Bans due to launching games on ReFS


Recommended Posts

On 19/08/2025 at 09:13, Gotenks98 said:

If a game is looking at your file system, it is definitely not something you want to be playing. That is just way too intrusive.

I think is part of the anti-cheat software, validating *things* to make sure nothing is being modified.  If the software is unable to validate files, files signatures, etc, then it probably assumes something is *wrong*, and probably lead to in this case a ban.

Not validating if this practice is good or bad, however, as someone who plays online (and please dont judge me on this!) CS2, I appreciate anti-cheat software that makes competitive games *fair*, at least from a software standpoint.

There's an awful lot of name calling, emotion and self-justification here, but I feel for you - if you have spent time, effort and money on something to have it taken away without any discussion or means of dispute.

However, I will suggest this:  It doesn't matter what any company did - what you did was run games on a documented unsupported filesystem.  This seemingly triggered ant-cheat detections.  Lame, because they are just using "catch all" technologies, but it's sometimes necessary to "stay ahead of the cheats".

But here's the thing - you signed up and agreed to their terms.  They didn't agree to yours.  I think rather than getting bogged down in a futile crusade, you cut your losses and move on?

  • Like 2
On 19/08/2025 at 19:10, Nik Louch said:

There's an awful lot of name calling, emotion and self-justification here, but I feel for you - if you have spent time, effort and money on something to have it taken away without any discussion or means of dispute.

However, I will suggest this:  It doesn't matter what any company did - what you did was run games on a documented unsupported filesystem.  This seemingly triggered ant-cheat detections.  Lame, because they are just using "catch all" technologies, but it's sometimes necessary to "stay ahead of the cheats".

But here's the thing - you signed up and agreed to their terms.  They didn't agree to yours.  I think rather than getting bogged down in a futile crusade, you cut your losses and move on?

And what should all this lead to? I signed up to the agreement/terms and conditions/policy, which does not contain a ban on file systems, but I was banned. Moreover, in other games in the same series, there is no permanent ban, but only in one game does it happen; the previous one simply does not start, and everything is fine. What conclusion can be drawn from this?
I was mostly loyal to CoD, I even have licensed discs for the first games. Considering how much more was spent on games from this company and on upgrades to make everything run smoothly, getting banned in response is probably not very pleasant. And this was a purely accidental discovery, which clearly indicates a serious bug, and they are ignoring this bug report and even denying access to technical support... I'm not even talking about bans for running under Wine/Proton... and a bunch of other cases where players get banned for no reason, without any apparent cause, and they are not even told why, and they are not given a second chance, and appeals are simply ignored...
And what causes the most confusion is the use of vague terminology, blurred answers, and simply ignoring the issue.
And I understand that CoDBOCW is already an old game. But why, without any actual violations, do we have a cheater label on four accounts when we are not cheaters? And because of this ban, purchasing other games on these accounts will result in them also being automatically banned, even without launching them... This is a direct violation of rights. It's especially annoying when people refer to something that doesn't exist and isn't specified. The fact that the installation method is unofficial and hasn't been confirmed by anyone anywhere is just our opinion in theory. And why should anyone care about that anyway? And again, there is nothing in the agreement/license/policy about prohibiting this or that in my case, but for some reason it refers back to the top and simply throws it back to problem 1 on 1.

Spoiler

QkRyPgzSVeZbT_MgKfHtVI1Bm8pcoK2xF9P17vGPk11rV4X9Z1bI5gLJCMO7fMjVEaVRzTM2Q_qLuPpQwlOyAA_k.thumb.jpg.3f3c3a6116769b5e7339c24cd99ad5c8.jpg

 

Edited by funkerwolf
On 19/08/2025 at 21:42, funkerwolf said:

And what should all this lead to? I signed up to the agreement/terms and conditions/policy, which does not contain a ban on file systems, but I was banned. Moreover, in other games in the same series, there is no permanent ban, but only in one game does it happen; the previous one simply does not start, and everything is fine. What conclusion can be drawn from this?
I was mostly loyal to CoD, I even have licensed discs for the first games. Considering how much more was spent on games from this company and on upgrades to make everything run smoothly, getting banned in response is probably not very pleasant. And this was a purely accidental discovery, which clearly indicates a serious bug, and they are ignoring this bug report and even denying access to technical support... I'm not even talking about bans for running under Wine/Proton... and a bunch of other cases where players get banned for no reason, without any apparent cause, and they are not even told why, and they are not given a second chance, and appeals are simply ignored...
And what causes the most confusion is the use of vague terminology, blurred answers, and simply ignoring the issue.

  Hide contents

QkRyPgzSVeZbT_MgKfHtVI1Bm8pcoK2xF9P17vGPk11rV4X9Z1bI5gLJCMO7fMjVEaVRzTM2Q_qLuPpQwlOyAA_k.thumb.jpg.3f3c3a6116769b5e7339c24cd99ad5c8.jpg

 

Sigh… fair enough - if all this emotion and posting serves you, then fair play.

On 19/08/2025 at 23:45, Nik Louch said:

Sigh… fair enough - if all this emotion and posting serves you, then fair play.

I just want justice and to have the cheater label removed from my account and my friends' accounts, not to mention the huge number of false bans.
I still sometimes get the feeling that everyone is simply afraid to go against Activision.

  

On 19/08/2025 at 19:10, Nik Louch said:

what you did was run games on a documented unsupported filesystem.

 And this is precisely what is not specified in the terms and conditions, policy, and agreement.

On 19/08/2025 at 23:45, Nik Louch said:

Sigh… fair enough - if all this emotion and posting serves you, then fair play.

You talking about fair play, but you dont even know how many retards playing in cs2 and other games with cheats right now. And what developers do? Nothing, even faceit, they just do nothing with AUTOHOTKEY. You can play with triggerbot and other ###### and its legit lol, becouse its just a scripts.

If you using some software, for file system, you dont getting any advantage, but getting ban. It is fair?)) Its not even sound systems (some sound visualiser, also many ppls using in cs2), or other tricks, its just nothing, its not fair to get ban for nothing.

On 20/08/2025 at 07:33, Varrning Skopeftis said:

You talking about fair play, but you dont even know how many retards playing in cs2 and other games with cheats right now. And what developers do? Nothing, even faceit, they just do nothing with AUTOHOTKEY. You can play with triggerbot and other ###### and its legit lol, becouse its just a scripts.

If you using some software, for file system, you dont getting any advantage, but getting ban. It is fair?)) Its not even sound systems (some sound visualiser, also many ppls using in cs2), or other tricks, its just nothing, its not fair to get ban for nothing.

"You talking about fair play, but you dont even know how many retards playing"

Please don't use that word. Everything you say is ignored when you use that word.

A game requiring NTFS and a gaming company banning people for using a different file system to store their files is certainly...something. I wonder if it's something that's explicitly stated in the game's requirements or ToS, and it would certainly be interesting to see what exactly they need that requires strictly NTFS. Windows not being able to  officially *boot* from ReFS should not matter.

I'm going to look at this from afar, OP are you 100% sure it's due to ReFS and not some other running processes on your system?

 

If their Anti-Cheat requires direct access to the filesystem and that was known prior to the bans or even playing, then that's on you, not the developer/publisher; you're the one who chose to run an unsupported filesystem.

On 20/08/2025 at 14:05, Case_f said:

A game requiring NTFS and a gaming company banning people for using a different file system to store their files is certainly

This did not happen!

OP installed the game on a filesystem that blocked the game being able to access certain game data, or change any files in the game data (like a users game data folder) which probably also flagged the anti-cheat. And we don't even know what else was going on on the OPs system.

A game typically has installation requirements, like Windows 10, 11 etc where the officially supported file system is NTFS. A game developer is not specifically saying NTFS must be used, they are saying it is supported on 64-bit versions of Windows 11, of which currently only supports booting from NTFS. That is the environment the game targets.

The current version of  Windows 11 24H2 does not support booting from ReFS, so game developers do not care to develop for it yet.

What is complicated about these facts?

  • Like 1
  • Love 1
On 20/08/2025 at 15:56, Matthew S. said:

I'm going to look at this from afar, OP are you 100% sure it's due to ReFS and not some other running processes on your system?

 

If their Anti-Cheat requires direct access to the filesystem and that was known prior to the bans or even playing, then that's on you, not the developer/publisher; you're the one who chose to run an unsupported filesystem.

that refs is not officially supported, I didn't know at that moment, and even more I didn't know that for such installation a ban is possible, and 3 additional retests with different hardware and different regions revealed the problem.

On 20/08/2025 at 16:14, Steven P. said:

This did not happen!

OP installed the game on a filesystem that blocked the game being able to access certain game data, or change any files in the game data (like a users game data folder) which probably also flagged the anti-cheat. And we don't even know what else was going on on the OPs system.

A game typically has installation requirements, like Windows 10, 11 etc where the officially supported file system is NTFS. A game developer is not specifically saying NTFS must be used, they are saying it is supported on 64-bit versions of Windows 11, of which currently only supports booting from NTFS. That is the environment the game targets.

The current version of  Windows 11 24H2 does not support booting from ReFS, so game developers do not care to develop for it yet.

What is complicated about these facts?

I appreciate your position, but why are there such assumptions and no specific information? Shouldn't all this lead to a ban without warning anywhere? And if I hadn't started this topic on the internet, no one would have known about it at all. Except that Wine/Proton also gave out bans, and they didn't start right away. It's terrible.

On 20/08/2025 at 09:50, funkerwolf said:

that refs is not officially supported, I didn't know at that moment, and even more I didn't know that for such installation a ban is possible, and 3 additional retests with different hardware and different regions revealed the problem.

Except you technically did if you had to jump through hoops just to get windows 11 to install and boot on it...

  • Like 3

Right from the COD Security and Enforcement policy, now keep in mind drivers typically will fit both the device and applications definition.

image.thumb.png.c1b2b125e07f4d7ed800b665c5431dbf.png

On 20/08/2025 at 14:43, Matthew S. said:

Right from the COD Security and Enforcement policy, now keep in mind drivers typically will fit both the device and applications definition.

image.thumb.png.c1b2b125e07f4d7ed800b665c5431dbf.png

I'd say that implies cheating was involved, since all their definitions say AND use for cheating

 

On 20/08/2025 at 21:43, Matthew S. said:

Right from the COD Security and Enforcement policy, now keep in mind drivers typically will fit both the device and applications definition.

image.thumb.png.c1b2b125e07f4d7ed800b665c5431dbf.png

If you dig deeper, you'll find that MSI Afterburner is also banned, as well as Trial Windows. It's just nonsense. It's terrible, and for some reason, they are still not being criticized for banning the use of goodbyedpi and other things that have become a necessity in some countries.

Edited by funkerwolf
On 20/08/2025 at 16:02, funkerwolf said:

If you dig deeper, you'll find that MSI Afterburner is also banned, as well as Trial Windows. It's just nonsense. It's terrible, and for some reason, they are still not being criticized for banning the use of goodbyedpi and other things that have become a necessity in some countries.

but it also says they dont terminate  unless your account has extreme or repeat offense... the others are temporary suspended

On 20/08/2025 at 15:14, Steven P. said:

This did not happen!

OP installed the game on a filesystem that blocked the game being able to access certain game data, or change any files in the game data (like a users game data folder) which probably also flagged the anti-cheat. And we don't even know what else was going on on the OPs system.

A game typically has installation requirements, like Windows 10, 11 etc where the officially supported file system is NTFS. A game developer is not specifically saying NTFS must be used, they are saying it is supported on 64-bit versions of Windows 11, of which currently only supports booting from NTFS. That is the environment the game targets.

The current version of  Windows 11 24H2 does not support booting from ReFS, so game developers do not care to develop for it yet.

What is complicated about these facts?

What "certain game data" did that filesystem prevent the game from accessing or changing? That's exactly something I was interested about here.

And what has booting from ReFS has to do with anything, really? You could easily have a small NTFS partition to boot from and have everything else on ReFS. That would satisfy even the most literal interpretation of "officially supported" on current Win 11. Would that still trigger a ban is the question...I suspect it might, given what we know about OP's case. And yes, sure, you are certainly free to speculate about various other things that "were going on on the OPs system". I choose to work with the information I have and not assume anything unless given reason.

And, more importantly, we've kinda overlooked what was kinda more of my point - what specifically is the game doing with the filesystem that *requires* NTFS? The feature set of NTFS and ReFS is almost identical, we're not talking about critical differences in ie. security or access rights management that could in theory pose an issue. And it's not some quirky fringe filesystem either, it's a filesystem that MS has been using on servers for years and that now has almost complete support on workstations as well (and really, plenty of people have been using it on workstations for a long time now, even if it wasn't strictly speaking "official").

I would say that OP brought up some very good points/issues with their case that at the very least don't deserve handwaving in the style of "well who knows whatever else was going on on their system" or "well you can't yet boot from the filesystem, so it makes sense you can't use it at all". Yes, there might have been other things that lead to the ban, but I would still appreciate some actual answers to questions like "would using ReFS really cause a ban and if so, why exactly?", and I would think an issue like this would be of interest to inquiring tech journalists and their audience. Especially since cases where people will be using ReFS on their systems are only going to become more common.

On 21/08/2025 at 08:38, Case_f said:

And yes, sure, you are certainly free to speculate about various other things that "were going on on the OPs system". I choose to work with the information I have and not assume anything unless given reason.

What information do you have about the OPs system other than what was claimed?

Also you're still missing the point. The games in question were loaded on an unsupported environment

We're left to speculate why Activision and several others "immediately" permabanned, because we only have the word of who it happened to.

As a reminder: The games in question were loaded on an unsupported environment

  • Like 2
  • Love 1
On 21/08/2025 at 09:30, Steven P. said:

What information do you have about the OPs system other than what was claimed?

Also you're still missing the point. The games in question were loaded on an unsupported environment

We're left to speculate why Activision and several others "immediately" permabanned, because we only have the word of who it happened to.

As a reminder: The games in question were loaded on an unsupported environment

What information do *you* have that justifies going "who knows what else they've done"? Unlike you, I'm not assuming anything beyond what we have to work with, that is the game was installed on ReFS on several accounts and said accounts were presumably banned for it. Yes, we only have OP's word for it.

And no, I'm not missing your point. You don't have to repeat it five times in bold. We could technically argue whether ReFS actually equals "unsupported environment" on current Win 11, because, again, we actually don't know it does, it's not stated anywhere specifically. Which, BTW, is yet another reason for someone from Activision clarifying whether it is or isn't either to the user banned as the ban was issued, or subsequently to a journalist interested in clarifying the situation.

You, on the other hand, seem to be missing *my* point, which is that this seems to be (yes, seems to be, we only have OP's word for it) a case that would deserve certain answers, be it about the specific cases or subsequently on whether ReFS is supported and what specifically prevents the game from working. As I was saying, if the accounts were truly banned for running the game on ReFS, it will only get worse going forward. Handwaving it as essentially hearsay and "unsupported environment" helps nothing and nobody, IMO. Well, except maybe Activision to maintain their lack of communication and clarification I guess.

(But it's likely my last comment on this and my apologies to everyone else reading this for dragging it on.)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • BATorrent 3.0.2 by Razvan Serea BATorrent is a lightweight, open-source BitTorrent client built with modern C++ and Qt 6, offering a clean, fast, and privacy-focused alternative to traditional torrent apps. It supports magnet links, .torrent files, resume data, sequential downloading, per-file priorities, and even imports from qBittorrent. Power users benefit from integrated RSS auto-download with regex filtering, duplicate detection, and automatic tracker lists from Stremio. Streaming is seamless thanks to auto-detected players like VLC and IINA. BATorrent includes robust VPN tools—interface binding, auto-detection for WireGuard-based services like Mullvad and NordLynx, kill switch, proxy support, and IP filtering. A full WebUI enables remote control, while integrations with Plex, Jellyfin, and Emby automate library updates. With themes, speed scheduling, system-tray alerts, and cross-platform support for Windows, Linux, and macOS, BATorrent delivers a polished, high-performance torrenting experience. BATorrent features: Core .torrent file and magnet link support Resume data — picks up where you left off after restart Import torrents from qBittorrent Create .torrent files from any file or folder Sequential download mode Per-file priority control (skip, low, normal, high) Seed ratio limits with auto-pause DHT, PEX, UPnP, NAT-PMP RSS Auto-Download Subscribe to RSS feeds — automatically download new torrents as they appear Regex filters — match only what you want (e.g. 1080p|720p, S01E\d+) Per-feed settings — custom save path, check interval (5–1440 min), enable/disable Auto-download — matched items are downloaded automatically in the background Supports magnet links, .torrent URLs, and tags Tray notifications when items are auto-downloaded Duplicate detection — never downloads the same item twice Stremio Stremio Addon System pre-installed — works out of the box Auto tracker list from ngosang/trackerslist Streaming Play while downloading — stream video files before the download is complete Supports mp4, mkv, avi, mov, wmv, flv, webm, m4v, ts Auto-detects installed players (VLC, IINA, system default) VPN & Privacy Interface binding — lock torrent traffic to a specific network interface (e.g. tun0) Auto VPN detection — identifies VPN interfaces (tun, tap, WireGuard, Mullvad, NordLynx, ProtonVPN) Kill switch — automatically pauses all torrents if the VPN interface drops Auto-resume — resumes only the torrents paused by the kill switch when VPN reconnects Proxy support — SOCKS5 and HTTP proxy with optional authentication IP filtering — load P2P blocklists to block unwanted IP ranges Protocol encryption (enabled / forced / disabled) WebUI Remote management — control torrents from any browser at http://localhost:8080 REST API with JSON responses Add torrents via magnet link or .torrent upload Pause, resume, remove torrents remotely View peers and files per torrent Dark theme matching the desktop app HTTP Basic Auth with SHA-256 password hashing Configurable port and remote access (localhost vs 0.0.0.0) Interface 3 themes: Dark, Light, Midnight (bat/vampire aesthetic) Real-time speed graph Detailed panel with tabs: General, Peers, Files, Trackers Filter bar: search by name, filter by state (Active, Downloading, Seeding, Paused, Finished) Drag & drop .torrent files and magnet links Drag & drop reorder in torrent list System tray with notifications (download complete, kill switch events, RSS auto-downloads) Splash screen with bat animation Bilingual: English and Portuguese (BR), auto-detected from system locale Bandwidth Scheduler Alternative speed limits — set different download/upload limits on a schedule Time range — configure active hours (e.g. 01:00 to 07:00), supports overnight ranges Per-day control — choose which days of the week the schedule applies Automatically switches between normal and alternative speeds Media Server Integration Plex — automatically trigger library scan when a download completes Jellyfin / Emby — same automatic library refresh via API Configure server URL and authentication token/key in Settings System Cross-platform: Windows, Linux, macOS Auto-shutdown — automatically shut down PC when all downloads complete (60s cancellable countdown) Auto-update system (AppImage on Linux, installer on Windows, DMG on macOS) CLI arguments: pass .torrent files or magnet: URIs directly Keyboard shortcuts: Space to toggle pause, Ctrl+A to select all, Ctrl+O to open BATorrent 3.0.2 changelog: Phone pairing & WebUI The browser WebUI was reskinned to match the desktop app — same dark palette, Inter font, flat surfaces, the real BATorrent logo (it was a random bat before), and a proper magnet icon. It now looks like the same product, not a separate dashboard. Pairing is one tap and zero typing: the generated WebUI password is now copyable, and the QR code carries the credentials — scanning it from your phone logs straight in (no typing the IP or password), then drops the credentials from the address bar. Search Two new providers: RuTor (CIS sources, no login, via a public TorAPI relay) and Torrents-CSV. Results are sorted by seeders (healthiest first), and each search now times out after 15 s so one dead provider can't hang the UI. Files & trackers Per-file priority is back: right-click a file in the detail panel to set Skip / Low / Normal / High. Rename an individual file inside a torrent (double-click or the file menu), separate from renaming the torrent. Remove a tracker from a torrent (the ✕ on a tracker row); adding was already there. Smart Paste on Ctrl+V — paste a magnet, a 40-char info-hash, or a .torrent URL straight from the clipboard and it's added immediately (text fields still paste text normally). Covers & titles Anime fansub naming ([Group] Title - NN) now resolves to the right show. Audio channel layouts in titles (DDP5.1, 7.1, …) are stripped so they don't pollute cover matching. Under the hood The legacy QWidget interface is gone. QML had been the only UI since 3.0.0 (reachable old code lived behind a hidden --legacy flag); with parity confirmed, the entire QWidget layer — main window, every dialog, the theme manager — was removed (~13,400 lines). The four restored actions above were features that backend already supported but the QML port had never wired. macOS: the WebUI password hash moved out of the keychain into app settings, so launching the app no longer pops a login-keychain password prompt on unsigned builds. The actual password still lives in the keychain. Cleanup: ~400 orphaned translation strings and a batch of dead code removed; internal duplication collapsed; an ARCHITECTURE.md added for contributors. Unit / security / memory tests and the ASan/UBSan/TSan sanitizers stay green. Download: BATorrent 3.0.2 | 30.5 MB (Open Source) Download: BATorrent Portable | 42.3 MB Links: BATorrent Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • How about a global switch to turn the awful things off instead of a registry hack? Then everyone wins.
    • This doesn't strike me as so shocking when... " IT admins do have some control over this rollout. If they choose to opt out, devices in their tenant won't automatically get the dreaded Copilot app"
  • Recent Achievements

    • Mentor
      grik went up a rank
      Mentor
    • Dedicated
      JKR earned a badge
      Dedicated
    • One Year In
      CHUNWEI earned a badge
      One Year In
    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
    • Week One Done
      I2D earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      PsYcHoKiLLa
      257
    3. 3
      Skyfrog
      79
    4. 4
      ATLien_0
      60
    5. 5
      FloatingFatMan
      60
  • Tell a friend

    Love Neowin? Tell a friend!