- Top Pick: Samsung 990 PRO 2TB NVMe SSD
- Runner-up: WD Black SN850X 2TB NVMe SSD
- Also consider: Crucial T500 2TB NVMe SSD
When a Linux player hits a wall with a big multiplayer game, the game itself usually is not the problem. Proton can translate its graphics calls, its audio and its networking well enough. The blocker is a second piece of software bundled with the game: an anti-cheat system that demands the deepest level of access a Windows PC can offer, inside the operating system kernel itself. That demand, rather than frame rates or graphics drivers, is why several of the largest games in the world still refuse to start on Linux.
This article explains the mechanism: what kernel-level access actually means, why a compatibility layer built entirely in user space cannot provide it, and what the companies involved have said in public. It is deliberately not a per-game status list. Our anti-cheat and Proton support check guide covers which games work today and how to verify your own library before switching; this piece covers the machinery underneath those answers.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
Kernel-level anti-cheat blocks Linux because these systems install a Windows kernel driver that inspects the operating system from the highest privilege level there is. Wine and Proton run entirely in user space and cannot load Windows kernel drivers, and Linux will not accept them either. Only the publisher can change the outcome, by choosing a user-space mode or enabling the documented Proton support paths.
The privilege model, in plain terms
A modern processor separates running code into privilege levels, often drawn as rings. Ordinary programs, including games and Proton itself, live in the outer ring, user space. Code there can only touch its own memory, and must ask the operating system for everything else. The innermost ring, ring 0, is where the kernel runs. Kernel code can read and write any memory on the machine, inspect every other program, and intercept any request those programs make.
That vantage point is exactly what competitive anti-cheat vendors are buying. A cheat hiding in user space can be seen from the kernel, which sits underneath it. A driver loaded at ring 0 can check which other drivers are present, watch memory being read by outside processes, and report tampering that a normal program could never detect. Riot’s Vanguard, Activision’s Ricochet and EA’s Javelin anti-cheat are all built on this model, each installing a kernel driver with the game.
The catch is that this power is specific to one kernel. A Windows kernel driver is written against the Windows kernel’s interfaces, is signed for Windows, and expects Windows structures in memory. It is not generic code that any operating system can host.
Why Proton cannot cross that line
Wine, and therefore Proton, is a translation layer that lives entirely in user space. It converts a game’s Windows API calls into Linux equivalents as the game runs. Crucially, it does not reproduce the Windows kernel: there is no Windows kernel inside a Proton prefix for a driver to load into, and Wine has no supported path for loading Windows kernel drivers.
Linux cannot fill the gap from its side either. The Linux kernel loads its own modules, written against Linux kernel interfaces; a signed Windows driver binary is meaningless to it. Loading one would require either a Windows kernel, which Linux is not, or a translation of kernel internals that nobody has built and that anti-cheat vendors would not trust anyway: a translated environment is exactly the kind of layer a cheat could hide inside.
This is why the failure mode is so abrupt. A game with kernel anti-cheat does not run slowly under Proton; it refuses to launch, because a component it requires has nowhere to exist. Tools that claim to bypass the check are attempts to defeat a security system: they violate the game’s terms of service and are a documented route to account bans, not a legitimate fix.
Two families of anti-cheat, two different fates
Not all anti-cheat needs the kernel, and the distinction decides which games work on Linux.
The first family is kernel-mode anti-cheat, described above. On Linux these systems are a hard stop unless the vendor redesigns them. Vanguard is the clearest example: Riot has explained publicly that its driver starts with the operating system itself, before the game, so it can establish trust in the machine’s state from boot. There is no Linux version of that driver, and Riot has announced none.
The second family works from user space, or leans on server-side detection. Easy Anti-Cheat and BattlEye both belong here, and both vendors offer a documented Linux path: their systems can run under Proton when the game’s developer enables that support, which both vendors describe as a switch the developer turns on for their title. When a developer flips that switch, the game usually works on Linux and the Steam Deck. When they do not, the same anti-cheat that runs fine in another studio’s game becomes the reason this one will not start.
Server-side detection is the third leg: analysis of behaviour and statistics on the publisher’s machines, needing nothing from the player’s operating system — which is why games with only server-side checks run on Linux with no special arrangement.
What the vendors have said in public
The public record matches the technical picture. Epic’s leadership has stated openly that Fortnite’s anti-cheat configuration is the reason it is not supported on Steam Deck or Linux, even though Easy Anti-Cheat itself offers a Proton path; the game’s specific setup, including kernel-level components, is what Epic declines to rework. EA moved in the other direction: in late 2024, EA and Respawn announced that Apex Legends would stop supporting Linux and Steam Deck access, citing the difficulty of detecting cheats in that environment. Bungie has stated that Destiny 2 is not supported on Steam Deck or Proton, and that attempting to run it there can put an account at risk under its policies. Riot has published detailed explanations of why Vanguard operates at kernel level and from boot.
Notice what none of these statements say. None claims the games could not render on Linux, and none blames Proton’s quality. Every position comes back to the same point: the anti-cheat architecture, and the publisher’s willingness to adapt it.
What would have to change
Three realistic paths exist, all in vendor and publisher hands. The first is wider use of the opt-in Proton support that Easy Anti-Cheat and BattlEye already document; each developer who enables it converts a blocked game into a working one. The second is architectural: anti-cheat designs that reach their goals from user space plus stronger server-side analysis, reducing the need for a kernel driver. The third is platform weight: the Steam Deck put a Linux gaming audience in front of publishers at a scale that was easy to ignore before, and Deck verification has already pushed some developers to enable support they had skipped.
Storage for the dual-boot fallback
Because the blocked games are a known, finite list for most players, the common practical answer is a second drive: Linux for daily use and the bulk of the library, Windows kept for the handful of kernel-anti-cheat titles.
Samsung 990 PRO 2TB NVMe SSD
A high-end Gen4 drive well suited to being the Windows drive in a dual-boot build, where the blocked titles live.
- Interface: PCIe 4.0 NVMe M.2 2280
- Capacity: 2TB
- Maker-rated sequential read: up to 7,450 MB/s
WD Black SN850X 2TB NVMe SSD
Western Digital’s gaming line, a natural pick for the Linux side of the same machine and its main Steam library.
- Interface: PCIe 4.0 NVMe M.2 2280
- Capacity: 2TB
- Maker-rated sequential read: up to 7,300 MB/s
Crucial T500 2TB NVMe SSD
A like-for-like Gen4 alternative for either operating system, useful when a board’s second M.2 slot is being filled.
- Interface: PCIe 4.0 NVMe M.2 2280
- Capacity: 2TB
- Maker-rated sequential read: up to 7,400 MB/s
Samsung T9 Portable SSD 2TB
The transfer and backup piece: moving game files between the two installs without re-downloading.
- Interface: USB 3.2 Gen 2×2
- Capacity: 2TB
- Maker-rated sequential read: up to 2,000 MB/s
Crucial MX500 1TB SATA SSD
The budget-tier option for older boards with no spare M.2 slot; a 2.5-inch SATA drive is still plenty for a Windows install and a few games.
- Interface: SATA 2.5-inch
- Capacity: 1TB
- Maker-rated sequential read: up to 560 MB/s
How to choose: your library by anti-cheat class
Sort your most-played games, not your whole library, into three buckets. Games with no anti-cheat or server-side detection only: safe on Linux today. Games using Easy Anti-Cheat or BattlEye where the developer has enabled Proton support: also safe, though worth rechecking after major updates. Games tied to kernel-mode anti-cheat, or to publishers who have publicly declined Linux support: these decide the question. If one of them is your main game, keep Windows, ideally on its own drive, and treat Linux as the system for everything else.
Who should skip this
Skip the mechanics if your library already runs and you have no interest in why; the per-game check takes minutes and answers the only question that affects you. Also skip it if you play exclusively single-player or co-op titles without client anti-cheat, because the kernel question will likely never touch your games. And if your main title is a kernel-anti-cheat game you play competitively, understanding changes nothing practical: that game needs Windows for the foreseeable future.
FAQ
Can Proton be updated to support kernel anti-cheat?
No, because the missing piece is not a Proton feature. A Windows kernel driver needs a Windows kernel to load into, Proton does not contain one, and the Linux kernel cannot host Windows drivers. Only the anti-cheat vendor or the publisher can change the design or enable a supported path.
Why do some Easy Anti-Cheat games work on Linux and others not?
Because Easy Anti-Cheat’s Proton support is an opt-in that each developer enables for their own game. The vendor supplies the capability; the publisher decides. Two games using the same anti-cheat can therefore have opposite Linux status.
Is kernel anti-cheat coming to Linux itself?
There is no announced Linux kernel anti-cheat from the major vendors, and the model travels badly: Linux kernels vary by distribution and can be rebuilt by their owners, the opposite of the fixed, attestable environment kernel anti-cheat is designed around. Vendors have instead put their Linux effort into the user-space Proton paths.
Can I get banned for trying to run a blocked game?
You can. Publishers that do not support Linux have in some cases stated that running their game through unsupported means risks account action, and bypass tools aimed at anti-cheat are treated as circumvention under game terms. If a title is blocked, the safe options are Windows or a different game.
Final verdict
Kernel-level anti-cheat is a structural boundary, not a compatibility bug. A driver that lives in the Windows kernel cannot be translated by a user-space layer, cannot be hosted by the Linux kernel, and cannot be wished into existence by a future Proton release. The games that work on Linux are the ones whose publishers chose user-space anti-cheat, server-side detection, or the documented Proton opt-ins. Sort your library by that distinction, keep Windows on a second drive for the exceptions, and the boundary becomes a planning fact instead of a recurring surprise.











