Please see other gists for updated information. https://gist.github.com/XenoPanther/15d8fad49fbd51c6bd946f2974084ef8
Last active
September 4, 2025 14:02
-
-
Save 0xbadfca11/da0598e47dd643d933dc to your computer and use it in GitHub Desktop.
Windows ReFS versions
Version number is reported by fsutil fsinfo refsinfo, available on Windows 10 and Windows Server 2016.
- Version of formatted by Windows Server 2012.
- Version 1.1 is used already in Windows Server 8 Beta. I have never seen version 1.0.
- Can use and store alternate data streams, when mount on 8.1/2012 R2 or later.
- Version of formatted by Windows 8.1, Windows 10 v1507 to v1607, Windows Server 2012 R2, and when specified ReFSv1 on Windows Server 2016 or later.
- Cannot use alternate data streams, when mount on 2012.
- Version that can be formatted with Windows 10 Technical Preview build 9841 to 9860 and Windows Server 2016 TP1 (It's not default). Could not mount in 10 9879 or 2016 TP2 and later.
- Version that can be formatted with Windows 10 Technical Preview build 9879 (It's not default). Could not mount in 9926 and later.
- Version that can be formatted with Windows 10 Technical Preview build 9926 (It's not default). Could not mount in 10041 and later.
- Version that can be formatted with Windows 10 Technical Preview build 10041 to 10049 (It's not default). Could not mount in 10061 and later.
- Version of formatted by Windows Server 2016 TP2/TP3.
- Version that can be formatted with between Windows 10 Technical Preview build 10061 or later and earlier than 10130 (It's not default). Could not mount in Windows 10 Insider Preview build 10130 and later, or Windows Server 2016 TP4 and later.
ReFS v2 Overview
http://www.snia.org/sites/default/files/SDC15_presentations/file_sys/JRTipton_ReFS_v2.pdf
http://www.snia.org/events/storage-developer/presentations15#file_sys
- Version of formatted by Windows Server 2016 TP4/TP5.
- Upgrade to 3.1 when writable mount from Windows Server 2016 RTM.
- Version of formatted by Windows Server 2016.
- Version of formatted by Windows 10 v1703.
- Version that can be formatted with Windows 10 Insider Preview 15002 or later (It's not default at 15002) and Windows Server Insider Preview build 16237.
- It became the default between after than 15002 and 15019 or earlier.
- Version of formatted by Windows 10 Enterprise v1709 and Windows Server version 1709.
- Version of formatted by Windows 10 Enterprise Insider Preview build 16257 and Windows Server Insider Preview build 16257.
- Version of formatted by Windows 10 Enterprise v1803, Windows Server 2019 and Windows Server version 1803.
- Version of formatted by Windows 10 Enterprise Insider Preview build 17083 and Windows Server Insider Preview build 17079.
- Version of formatted by Windows 10 Enterprise Insider Preview build 19536 and Windows Server Insider Preview build 19551.
- Added hardlink support if fresh formatted volume.
- Can't use hardlink if upgraded from previous version.
- Upgrade to 3.6 when writable mount from Windows 10 Insider Preview build 21292.
- Version of formatted by Windows 10 Enterprise Insider Preview build 21292 and Windows Server Insider Preview build 20282.
- Upgrade to 3.7 when writable mount from Windows 10 Insider Preview build 21313.
- Version of formatted by Windows 11 Enterprise v21H2 and Windows Server 2022.
- Version of formatted by Windows 10 Enterprise Insider Preview build 21313 and Windows Server Insider Preview build 20303.
- Version of formatted by Windows 11 Enterprise v22H2.
- Version of formatted by Windows 11 Enterprise Insider Preview build 22598 and Windows Server Insider Preview build 25099.
- Added post process compression with LZ4 & ZSTD, transparent decompression.
| ReFS\Windows | 2012 | 8.1/2012 R2 | 10 v1507 | 2016 | 10 v1703 | 10 v1709 | 10 v1803/2019 | 11 v21H2/2022 | 11 v21H2 |
|---|---|---|---|---|---|---|---|---|---|
| 1.1 | Yes | Yes1 | Yes1 | Yes1 | Yes1 | Yes1 | Yes1 | Yes1 | Yes1 |
| 1.2 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 3.1 | No | No | No | Yes | Yes2 | Yes3 | Yes4 | Yes56 | Yes76 |
| 3.2 | No | No | Yes | Yes3 | Yes4 | Yes56 | Yes76 | ||
| 3.3 | No | No | Yes | Yes4 | Yes56 | Yes76 | |||
| 3.4 | No | Yes | Yes56 | Yes76 | |||||
| 3.7 | No | Yes | Yes8 | ||||||
| 3.9 | No | Yes |
Notes
Empty filed is "I don't know. I haven't tested.".
License: CC BY
Footnotes
-
"Volume "?:" was mounted in an older version of Windows. Some features may be lost." was recorded to event log when writable mount. I don't know what's been lost. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8
-
Upgrade to 3.2 when writable mount. ↩
-
Upgrade to 3.9 when writable mount. Can't mount read-only. ↩ ↩2 ↩3 ↩4
-
Upgrade to 3.9 when writable mount. ↩
バージョン番号はWindows 10とWindows Server 2016で使用可能なfsutil fsinfo refsinfoで報告されるもの。
- Windows Server 2012でフォーマットしたバージョン。
- Windows Server 8 Betaの時点で1.1であり1.0の存在は不明。
- 8.1/2012 R2以降でマウントした場合はAlternate Data Stream使用可能。
- Windows 8.1、Windows 10 v1507からv1607、Windows Server 2012 R2でフォーマットしたとき、およびWindows Server 2016以降でReFSv1を指定してフォーマットしたときのバージョン。
- 2012でマウントした場合はAlternate Data Stream使用不可。
- Windows 10 TP ビルド9841から9860とWindows Server 2016 TP1でフォーマット可能なバージョン（デフォルトではない）。10 9879/ 2016 TP2以降ではマウント不可。
- Windows 10 TP ビルド9879でフォーマット可能なバージョン（デフォルトではない）。9926以降ではマウント不可。
- Windows 10 TP ビルド9926でフォーマット可能なバージョン（デフォルトではない）。10041以降ではマウント不可。
- Windows 10 TP ビルド10041から10049でフォーマット可能なバージョン（デフォルトではない）。10061以降ではマウント不可。
- Windows Server 2016 TP2/TP3でフォーマットしたバージョン。
- Windows 10 TP ビルド10061から10130より前でフォーマット可能なバージョン（デフォルトではない）。10 10130以降、2016 TP4以降ではマウント不可。
ReFS v2の概要
http://www.snia.org/sites/default/files/SDC15_presentations/file_sys/JRTipton_ReFS_v2.pdf
http://www.snia.org/events/storage-developer/presentations15#file_sys
- Windows Server 2016 TP4/TP5でフォーマットしたバージョン。
- Windows Server 2016から書き込み可能でマウントすると3.1にアップグレードされる。
- Windows Server 2016でフォーマットしたバージョン。
- Windows 10 v1703でフォーマットしたバージョン。
- Windows 10 Insider Preview ビルド15002およびWindows Server Insider Preview ビルド16237でフォーマット可能なバージョン（15002ではデフォルトではない）。
- 15002より後、15019までの間にデフォルトになった。
- Windows 10 Enterprise v1709およびWindows Server version ビルド1709でフォーマットしたバージョン。
- Windows 10 Enterprise Insider Preview ビルド16257およびWindows Server Insider Previewビルド16257でフォーマットしたバージョン。
- Windows 10 Enterprise v1803、Windows Server 2019およびWindows Server version 1803でフォーマットしたバージョン。
- Windows 10 Enterprise Insider Preview ビルド17083およびWindows Server Insider Preview ビルド17079でフォーマットしたバージョン。
- Windows 10 Enterprise Insider Preview ビルド19536およびWindows Server Insider Previewビルド19551でフォーマットしたバージョン。
- 新規フォーマットした場合に限りハードリンク使用可能。
- 3.5未満からアップグレードした場合は使用不可。
- Windows 10 Insider Preview ビルド21292から書き込み可能でマウントすると3.6にアップグレードされる。
- Windows 10 Enterprise Insider Preview 21292およびWindows Server Insider Previewビルド20282でフォーマットしたバージョン。
- Windows 10 Insider Preview ビルド21313から書き込み可能でマウントすると3.7にアップグレードされる。
- Windows 11 Enterprise v21H2およびWindows Server 2022でフォーマットしたバージョン。
- Windows 10 Enterprise Insider Preview 21313およびWindows Server Insider Previewビルド20303でフォーマットしたバージョン。
- Windows 11 Enterprise v22H2でフォーマットしたバージョン。
- Windows 11 Enterprise Insider Preview 22598およびWindows Server Insider Previewビルド25099でフォーマットしたバージョン。
- LZ4 & ZSTDによる事後圧縮と透過伸長が追加。
| ReFS\Windows | 2012 | 8.1/2012 R2 | 10 v1507 | 2016 | 10 v1703 | 10 v1709 | 10 v1803/2019 | 11 v21H2/2022 | 11 v21H2 |
|---|---|---|---|---|---|---|---|---|---|
| 1.1 | Yes | Yes1 | Yes1 | Yes1 | Yes1 | Yes1 | Yes1 | Yes1 | Yes1 |
| 1.2 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 3.1 | No | No | No | Yes | Yes2 | Yes3 | Yes4 | Yes56 | Yes76 |
| 3.2 | No | No | Yes | Yes3 | Yes4 | Yes56 | Yes76 | ||
| 3.3 | No | No | Yes | Yes4 | Yes56 | Yes76 | |||
| 3.4 | No | Yes | Yes56 | Yes76 | |||||
| 3.7 | No | Yes | Yes8 | ||||||
| 3.9 | No | Yes |
空欄は「テストしてないので分かりません」を意味します。
License: CC BY
Footnotes
Good evening, I no longer know where to turn with my problem. Here’s what happened: since I upgraded my computer in the winter of this year, I’ve been having issues finding games in Black Ops 6, and it turns out I am constantly in a shadow ban without reason, and then I received a permanent ban in Cold War. For a long time, I thought I got banned first due to purchasing used hardware - specifically a motherboard and a processor, but that turned out not to be the case - they were new according to the receipts from the store. Then I thought the ban came from the nvidia dlss override feature, but upon rechecking, that version turned out to be invalid. After more time, my friends and I came to the conclusion that for some reason in the Call of Duty series, a ban occurs if you launch the game from a ReFS partition where Windows 11 24h2 is installed. What should I do about this? Activision support doesn't help at all and forces me to read their policy like a dogma (but there is absolutely nothing there regarding the use of file systems even), and their supposed solution after appealing is final and cannot be reconsidered... Yes, I fully understand that Windows does not officially support booting from a ReFS partition; however, the Windows installer allows one to do so, both on ReFS and to install the system with Server 2025. But that's not a reason to ban me in just one game, because in other games like Counter-Strike 2 everything is fine, including those protected by EAC. Statements and proofs: reddit.com/r/Warzone/comments/1kl8wys habr.com/ru/articles/923190/
So what do you expect us to do here? Microsoft will certainly not make ReFS behave and act like NTFS because it's not implementing the same features. Hacking anti cheat and anti tempering software is also forbidden. And there's no way anyone here will be able to tell Activision to change their software to run on ReFS.
I've got a disk with ReFS for gaming but also a disk for games that run only on NTFS. I suggest you do the same. You can easily have these two disks on a physical disk when you use Storage Spaces.
Guys how do i enable it
Guys how do i enable it
HELP
Guys how do i enable it
Enable what?
Good evening, I no longer know where to turn with my problem. Here’s what happened: since I upgraded my computer in the winter of this year, I’ve been having issues finding games in Black Ops 6, and it turns out I am constantly in a shadow ban without reason, and then I received a permanent ban in Cold War. For a long time, I thought I got banned first due to purchasing used hardware - specifically a motherboard and a processor, but that turned out not to be the case - they were new according to the receipts from the store. Then I thought the ban came from the nvidia dlss override feature, but upon rechecking, that version turned out to be invalid. After more time, my friends and I came to the conclusion that for some reason in the Call of Duty series, a ban occurs if you launch the game from a ReFS partition where Windows 11 24h2 is installed. What should I do about this? Activision support doesn't help at all and forces me to read their policy like a dogma (but there is absolutely nothing there regarding the use of file systems even), and their supposed solution after appealing is final and cannot be reconsidered... Yes, I fully understand that Windows does not officially support booting from a ReFS partition; however, the Windows installer allows one to do so, both on ReFS and to install the system with Server 2025. But that's not a reason to ban me in just one game, because in other games like Counter-Strike 2 everything is fine, including those protected by EAC. Statements and proofs: reddit.com/r/Warzone/comments/1kl8wys habr.com/ru/articles/923190/
So what do you expect us to do here? Microsoft will certainly not make ReFS behave and act like NTFS because it's not implementing the same features. Hacking anti cheat and anti tempering software is also forbidden. And there's no way anyone here will be able to tell Activision to change their software to run on ReFS.
I've got a disk with ReFS for gaming but also a disk for games that run only on NTFS. I suggest you do the same. You can easily have these two disks on a physical disk when you use Storage Spaces.
In the end, Activision banned me from their technical support, and they don't accept direct bug reports.
@funkerwolf I'm afraid if you want to use Activision's servers, and they don't want you booting from ReFS, you have to play by their rules.
@funkerwolf I'm afraid if you want to use Activision's servers, and they don't want you booting from ReFS, you have to play by their rules.
Unfortunately, their rules, license agreement, and policy do not mention file systems, refs, or ntfs. https://habr.com/en/articles/929782/
@funkerwolf There's nothing we can do about that for you, and to be fair, ReFS isn't supported for booting by Microsoft, so it's doesn't seem fair to blame Activision for not supporting it in their anti-cheat software.
This thread has to be marked as the official complaint page for MSFT ReFS
This thread has to be marked as the official complaint page for MSFT ReFS
Considering the fact that Activision is owned by Microsoft and, for some reason, the former has not been punished for this yet, they are in a convenient position to shift the blame for their mistakes onto users. And it's not a very funny situation when games set in the future don't work on the file system of the future, on the operating system of the future, and on the company of the future, Microsoft...
@funkerwolf There's nothing we can do about that for you, and to be fair, ReFS isn't supported for booting by Microsoft, so it's doesn't seem fair to blame Activision for not supporting it in their anti-cheat software.
You can raise a fuss in the media. Why is this even possible? I didn't violate anything, but I got banned. What's more, I got banned by their technical support, and they don't accept direct bug reports, even early ones, until Windows defaults to using ReFS instead of NTFS. They should be grateful to me, not treating me this way and banning four accounts belonging to my friends.
@funkerwolf Sorry but at present the fact is that Microsoft do not support booting via ReFS (NB 'it works' does not mean 'it is supported'). That means Microsoft and Activision cannot really be considered fully accountable for any issues you may encounter while doing so.
https://learn.microsoft.com/en-us/windows-server/storage/refs/refs-overview#features-unavailable-on-refs
Until it's supported, I don't think your complaint has a leg to stand on here. But regardless, I wish you every success in regaining access to your account.
@funkerwolf Sorry but at present the fact is that Microsoft do not support booting via ReFS (NB 'it works' does not mean 'it is supported'). That means Microsoft and Activision cannot really be considered fully accountable for any issues you may encounter while doing so. https://learn.microsoft.com/en-us/windows-server/storage/refs/refs-overview#features-unavailable-on-refs Until it's supported, I don't think your complaint has a leg to stand on here.
If that were really the case, then the Windows installer wouldn't allow it, but it does allow it, and it's entirely possible in the release version 24h2 with Server 2025. But even so, it shouldn't be a reason for a ban, especially since no other game has this, but for some reason Call of Duty is fine, and I repeat, there is nothing in their policy/terms/agreement about file systems, which again means that the ban is not legitimate, but unfortunately, I cannot go to court.
@funkerwolf Again, 'the installer allows it' is another way of saying 'it works', but again, this is not the same as 'it's supported'.
@funkerwolf Again, 'the installer allows it' is another way of saying 'it works', but again, this is not the same as 'it's supported'.
Why should this be a reason for a ban, which does not contradict the terms and conditions/policy/agreement?
I have no complaints about ReFS itself, only about the attitude of programmers who, in 13 years, have not learned how to work with it. But for some reason, ordinary users and gamers have to pay for their mistakes. I wouldn't be surprised if ReFS itself is a target for their anti-cheat system, which means I can't use two hard drives in a mirror to speed up game startup.
Don't you have a better place to whine?
Don't you have a better place to whine?
I shouldn't have been banned from a Microsoft game on a Microsoft file system with a Microsoft operating system, considering that this platform has also belonged to Microsoft for a long time. I want to draw attention to the problem so that it can finally be solved, rather than being banned for programmers' mistakes, a ban that is unjustified on the part of the player/user.
Your banning has absolutely nothing to do with ReFS and this gist.
Your banning has absolutely nothing to do with ReFS and this gist.
Your banning has absolutely nothing to do with ReFS and this gist.
OK, what on earth do you think you're doing here?
- This is a group of tech interested people, we're not connected to either Microsoft nor Activision.
- Just because Activision is owned by Microsoft, there's no need for them to support all Microsoft file systems that can run on Windows like FAT, VFAT, exFAT, TFAT, TexFAT, REFS, HPFS, FatX, WinFS, CSVFS, CLFS, ProjFS or other, closed and open sourced third party file systems.
- Ordinary users and gamers aren't the target audience of ReFS on client versions of Windows. The main target audience are Windows developers for the dev drive and then people who want to store their DATA similar to a server.
- Mirroring on Windows also works with NTFS, there's no need for ReFS. Installing Windows still isn't supported on ReFS despite its not blocked anymore.
- There's no advantage of installing online games on mirrored disks since they can be downloaded again for free and often use online auto-repair.
- Windows Store games mostly refuse to even install on ReFS which should be a warning to any gamer that Microsoft has yet to support ReFS for gaming.
- Your ban in the video seems to only be partially active so I suggest you uninstall and reinstall on NTFS and then wait until you get unbanned again (if it's actually the cause and not something else you did).
- Online game services are usually offered as is with no guarantee for uptimes, access or server availability beyond the day of the release. If you can't use them as expected, you can try to get a refund.
- Please stop pointless arguing and bothering us here. We're only discussing the changes and improvements of released versiona of ReFS here, nothing more. Despite you mentioning file system and anti cheat development, I doubt you have any idea about how to do that.
- If you continue to talk off topic, you risk getting suspended here, too.
To add to the excellent points made above, I suspect the reason why your anti-cheat software is blocking you when you boot with ReFS is because of bypasses like this, which use EfiGuard to bypass various signed driver requirements in Windows, but also seems to involve booting from a FAT / FAT32 USB stick.
So it could be a blunt mitigation against that e.g. ‘if you’re not booting from an NTFS drive, you may be cheating?’ But again, Microsoft are very clear that ReFS is not yet supported for booting (which means they haven’t completed testing that scenario, so even if it does work, it is not under their ‘support’ which is like their ‘manufacturer’s guarantee’, and you must accept that there may be unwanted side effects). One of these is apparently, it may trip anti-cheat software. The answer is to run it on a supported file system, not to moan on a GitHub gist where sadly nobody you’re talking with has any ability to change anything for you.
I don't know where you got the information that Microsoft supports or does not support this, but banning users and referring to terms, agreements, or policies that do not specify this, i.e., according to you, is normal, and even threatening to suspend accounts here is brilliant logic. And the fact that this thread is for developers further emphasizes that this is important and necessary information, which was revealed by chance and could prevent such cases in the future if they take note of it.
Your banning has absolutely nothing to do with ReFS and this gist.
OK, what on earth do you think you're doing here?
He telling if you using refs, you will get ban.
Developers must write something to activision, cos peopeles getting bans for nothing.
He telling if you using refs, you will get ban. Developers must write something to activision, cos peopeles getting bans for nothing.
So go write something already. And not here, for fuck's sake. This is a gist, not a platform for activism.
Don't you have a better place to whine?
I shouldn't have been banned from a Microsoft game on a Microsoft file system with a Microsoft operating system, considering that this platform has also belonged to Microsoft for a long time. I want to draw attention to the problem so that it can finally be solved, rather than being banned for programmers' mistakes, a ban that is unjustified on the part of the player/user.
This is a gist for developers and enthusiasts that is NOT CONNECTED WITH MS nor Activision.
You should contact game developer or MS.
No one here cares about your fking ban.
Others respond you just because your comments are disrupting the discussion, not because everyone cares so much about the problems you're facing.
Just for anyone actually interested in the underlying tech here, I've compiled some information.
Creating a working WindowsApps folder for Windows Store and Xbox games installs on any drive currently involves these steps:
- When you run Add‑AppxVolume, PowerShell calls into the PackageManager COM API (Windows.Management.Deployment.PackageManager), which in turn calls the internal AppxVolume::Add routine in the AppX Deployment Service (AppXSVC).
- That routine queries the target path’s file system type via Win32 APIs (e.g., GetVolumeInformationW) and compares it against NTFS.
- If it’s not NTFS, the API returns an error (ERRORNOTSUPPORTED), which surfaces in PowerShell as a failure to add the volume.
So it's impossible to setup a Windows games install folder on ReFS.
The only way I can think of doing this is by either forcing the Windows 11 installation on ReFS during Windows Setup (formatting with ReFS during the setup is still not enabled) or manually cloning an NTFS file system to ReFS. Both ways are clearly manipulations of the OS and it's behavior and certainly unsupported.
Don't you have a better place to whine?
I shouldn't have been banned from a Microsoft game on a Microsoft file system with a Microsoft operating system, considering that this platform has also belonged to Microsoft for a long time. I want to draw attention to the problem so that it can finally be solved, rather than being banned for programmers' mistakes, a ban that is unjustified on the part of the player/user.
This is a gist for developers and enthusiasts that is NOT CONNECTED WITH MS nor Activision. You should contact game developer or MS.
No one here cares about your fking ban. Others respond you just because your comments are disrupting the discussion, not because everyone cares so much about the problems you're facing.
https://www.youtube.com/watch?v=1f4RKuZLq_0
Just for anyone actually interested in the underlying tech here, I've compiled some information.
Creating a working WindowsApps folder for Windows Store and Xbox games installs on any drive currently involves these steps:
* When you run Add‑AppxVolume, PowerShell calls into the PackageManager COM API (Windows.Management.Deployment.PackageManager), which in turn calls the internal AppxVolume::Add routine in the AppX Deployment Service (AppXSVC). * That routine queries the target path’s file system type via Win32 APIs (e.g., GetVolumeInformationW) and compares it against NTFS. * If it’s not NTFS, the API returns an error (ERRORNOTSUPPORTED), which surfaces in PowerShell as a failure to add the volume.So it's impossible to setup a Windows games install folder on ReFS.
The only way I can think of doing this is by either forcing the Windows 11 installation on ReFS during Windows Setup (formatting with ReFS during the setup is still not enabled) or manually cloning an NTFS file system to ReFS. Both ways are clearly manipulations of the OS and it's behavior and certainly unsupported.
24h2 installs through the installer with nothing if the disk is formatted through diskpart and these are all regular versions through steam and blizzard, they don't even ask any questions and work
I'll bite.
I setup a REFS volume, had Steam install Call of Duty on it. I played one match of Warzone (won too lol). I didn't get banned. 🤷
Next is to setup a bootable refs volume and do the same?!
I'll bite.
I setup a REFS volume, had Steam install Call of Duty on it. I played one match of Warzone (won too lol). I didn't get banned. 🤷
Next is to setup a bootable refs volume and do the same?!
Yes. Don't launch CoDBOCW unless you don't mind losing it and don't want to get your account banned. The free WZ will suffice; you'll get a shadow for a week, and it will be removed automatically.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Good evening, I no longer know where to turn with my problem. Here’s what happened: since I upgraded my computer in the winter of this year, I’ve been having issues finding games in Black Ops 6, and it turns out I am constantly in a shadow ban without reason, and then I received a permanent ban in Cold War. For a long time, I thought I got banned first due to purchasing used hardware - specifically a motherboard and a processor, but that turned out not to be the case - they were new according to the receipts from the store. Then I thought the ban came from the nvidia dlss override feature, but upon rechecking, that version turned out to be invalid. After more time, my friends and I came to the conclusion that for some reason in the Call of Duty series, a ban occurs if you launch the game from a ReFS partition where Windows 11 24h2 is installed. What should I do about this? Activision support doesn't help at all and forces me to read their policy like a dogma (but there is absolutely nothing there regarding the use of file systems even), and their supposed solution after appealing is final and cannot be reconsidered... Yes, I fully understand that Windows does not officially support booting from a ReFS partition; however, the Windows installer allows one to do so, both on ReFS and to install the system with Server 2025. But that's not a reason to ban me in just one game, because in other games like Counter-Strike 2 everything is fine, including those protected by EAC. Statements and proofs: reddit.com/r/Warzone/comments/1kl8wys habr.com/ru/articles/923190/