Epic Games’ Easy Anti‑Cheat (EAC) is finally landing on ARM platforms — a technical and ecosystem milestone that removes one of the largest obstacles keeping multiplayer PC games off Snapdragon‑powered Copilot+ laptops and Linux ARM devices. The company shipped updated Epic Online Services (EOS) tooling that includes a Windows‑on‑ARM EAC client and an ARM‑aware bootstrapper distributed via the EOS SDK, and Epic will battle‑test the rollout with Fortnite before wider studio adoption. This move pairs with Microsoft’s Prism improvements and Auto SR upscaler to make ARM Windows gaming more feasible, but it does not magically solve performance, fragmentation, or kernel‑level risk concerns; publishers, anti‑cheat vendors, and platform teams still have concrete work to do.
The last two years have seen dramatic improvements to Windows on ARM: Microsoft’s Prism x86→ARM translation and Arm64EC tooling let developers ship hybrid builds, while Qualcomm’s Snapdragon X‑series silicon improved raw capability for thin-and‑light gaming. Still, a critical blocker remained: kernel‑level anti‑cheat drivers. These low‑level components historically targeted x64 kernel interfaces and simply do not run through user‑mode translation layers, which meant many popular multiplayer titles refused to start on ARM devices because their anti‑cheat never initialized. Epic’s work directly addresses that kernel‑mode gap by shipping an ARM‑native EAC client and distributing it through the EOS SDK to studios.
Epic’s announcement frames Fortnite as both a consumer milestone and a pragmatic validation platform: Fortnite will be among the first titles to adopt the ARM EAC client so Epic can “battle‑test” the implementation in real‑world multiplayer conditions before third‑party studios follow. The EOS SDK update — reported in the wild as EOS 1.17.1.3‑CL44532354 (Aug 12, 2025) in press coverage — is the delivery vehicle for the ARM anti‑cheat binaries and integration guidance. Developers must still opt in and update their installers/bootstrappers to ship the ARM‑aware components.
Key practical point: enabling EAC for a game via Proton often requires explicit developer action and, in some cases, a rework if the title uses a legacy (non‑EOS) EAC integration. Valve and Epic have provided tooling and simplified flows over time, but developer choice remains the gating factor for many games.
Notably, some high‑profile anti‑cheat systems have not publicly announced full ARM support. Riot Vanguard (used by Riot titles) historically remains tightly coupled to Windows x64 and Secure Boot constraints, and Faceit’s and EA’s newer Javelin/secure‑boot strategies have complex requirements; these vendors/publishers must confirm ARM builds before their games are reliably playable on ARM Windows or Linux. Where public statements are absent, treat vendor support as unverified until the vendor issues a formal ARM compatibility announcement.
That said, the victory is tactical, not total. Performance parity, publisher engagement, and vendor diversity of anti‑cheat support will determine how broadly ARM devices become mainstream gaming platforms. Kernel‑mode code must be shipped with meticulous QA, transparent telemetry policies, and careful coordination with Windows security features. For players and admins, the sensible approach is cautious optimism: the anti‑cheat gate is open, but the broader work of porting, optimizing, and validating multiplatform builds continues.
For developers and publishers, the message is clear: the toolchain is available — update your EOS/EAC integration, validate on representative ARM hardware, and prepare clear messaging to players. For OEMs and Microsoft, execution now matters: ensure update flows, support pages, and compatibility signals are unambiguous so buyers can reliably know which titles will work locally on ARM devices.
This change removes one of the most visible technical barriers to ARM gaming. The next 6–12 months will reveal whether momentum, publisher economics, and vendor coordination are enough to turn that technical possibility into a widely usable reality.
Source: Tom's Hardware Epic Games adds Easy Anti-Cheat for ARM devices — Feature unlocks support for Windows, Linux, and Switch 2
The last two years have seen dramatic improvements to Windows on ARM: Microsoft’s Prism x86→ARM translation and Arm64EC tooling let developers ship hybrid builds, while Qualcomm’s Snapdragon X‑series silicon improved raw capability for thin-and‑light gaming. Still, a critical blocker remained: kernel‑level anti‑cheat drivers. These low‑level components historically targeted x64 kernel interfaces and simply do not run through user‑mode translation layers, which meant many popular multiplayer titles refused to start on ARM devices because their anti‑cheat never initialized. Epic’s work directly addresses that kernel‑mode gap by shipping an ARM‑native EAC client and distributing it through the EOS SDK to studios. Epic’s announcement frames Fortnite as both a consumer milestone and a pragmatic validation platform: Fortnite will be among the first titles to adopt the ARM EAC client so Epic can “battle‑test” the implementation in real‑world multiplayer conditions before third‑party studios follow. The EOS SDK update — reported in the wild as EOS 1.17.1.3‑CL44532354 (Aug 12, 2025) in press coverage — is the delivery vehicle for the ARM anti‑cheat binaries and integration guidance. Developers must still opt in and update their installers/bootstrappers to ship the ARM‑aware components.
Why this matters: the technical hurdles and the fix
Kernel drivers, Prism, and Arm64EC — why anti‑cheat is different
Anti‑cheat packages frequently include kernel‑mode drivers that inspect memory, monitor process interactions, and defend against tampering. Those drivers are written for the x64 kernel API and cannot be trivially emulated in user space. Microsoft’s Prism addresses user‑mode translation; it does not translate kernel drivers. Arm64EC lets developers create hybrid binaries (native ARM parts and emulated x86 parts), but kernel drivers still need an ARM native port to function reliably. That mismatch is why many multiplayer titles were effectively blocked on ARM devices even when game logic could run via Prism.What Epic shipped — SDK, bootstrapper, and client
Epic’s EOS SDK update packages an ARM‑native anti‑cheat client and an updated bootstrapper (the installer/launcher component that installs and updates EAC on the user’s machine). Studios will need to:- Update their EOS/EAC dependency to the new SDK release.
- Replace or repackage the anti‑cheat bootstrapper so ARM devices receive the ARM client at install time.
- Test driver initialization, repair flows, and telemetry on representative Snapdragon X hardware.
Linux, Proton, and the Steam Deck angle
EAC has supported Linux and the Proton/Wine compatibility layers for several years, and Valve and Epic have worked together to make EAC function in Proton where developers opt in. Epic’s historic Linux/Proton support is the reason many Steam Deck titles became possible in the first place, and expanding ARM support to Linux is a meaningful win for Linux‑on‑ARM players because Valve has also improved Proton’s ARM tooling. That combination reduces friction for Steam Deck‑style handhelds and other Linux ARM devices. However, Proton integration depends on developers enabling the Linux EAC client or including the needed Linux library in their Steam depots — it’s not automatic for all titles.Key practical point: enabling EAC for a game via Proton often requires explicit developer action and, in some cases, a rework if the title uses a legacy (non‑EOS) EAC integration. Valve and Epic have provided tooling and simplified flows over time, but developer choice remains the gating factor for many games.
What Epic’s move unlocks — and what it doesn’t
Immediate wins
- Hundreds of EAC‑protected titles become eligible to run locally on Snapdragon X‑series Copilot+ PCs if publishers adopt the updated EOS SDK and ship the ARM anti‑cheat client.
- Developer burden is reduced: Epic’s SDK provides a single, maintained integration path instead of forcing each studio to build its own ARM anti‑cheat port.
- OEM and Microsoft narratives improve: The removal of the anti‑cheat blocker strengthens the real‑world argument for ARM Windows devices as capable gaming machines.
What remains a blocker
- Performance parity is not guaranteed. If a game remains x64 and runs under Prism emulation, translation overhead will still affect CPU‑bound performance and occasionally GPU workloads. Native ARM64 builds or well‑crafted Arm64EC mixes are required for parity in many titles.
- Other anti‑cheat vendors matter. Epic’s EAC is pervasive but not universal. Games that rely on other anti‑cheat systems remain blocked until those vendors ship ARM builds.
- Operational risks from kernel code. Porting kernel drivers to a new ISA means new testing vectors: stability, compatibility with Windows hardening (Memory Integrity / Core Isolation), and driver signing requirements must be validated.
Where other anti‑cheat vendors stand
Microsoft and industry partners have been coordinating to bring anti‑cheat vendors onto ARM. Microsoft explicitly called out several vendors as having ARM support in its platform push: BattlEye, Denuvo Anti‑Cheat, and Wellbia XIGNCODE3 / UNCHEATER are now supported on Windows on ARM per Microsoft’s developer communications. That progress reduces the chance a single anti‑cheat system becomes a permanent blocker, but it doesn’t eliminate catalog fragmentation — publishers must still choose to ship the ARM builds.Notably, some high‑profile anti‑cheat systems have not publicly announced full ARM support. Riot Vanguard (used by Riot titles) historically remains tightly coupled to Windows x64 and Secure Boot constraints, and Faceit’s and EA’s newer Javelin/secure‑boot strategies have complex requirements; these vendors/publishers must confirm ARM builds before their games are reliably playable on ARM Windows or Linux. Where public statements are absent, treat vendor support as unverified until the vendor issues a formal ARM compatibility announcement.
Nintendo Switch 2: claim vs. confirmation
Some coverage of the EOS SDK update repeated a developer‑facing line that the release “adds support for Nintendo Switch 2” and suggested EOS/Switch integration can be extended to Nintendo’s next console with minimal changes. That phrasing appeared in secondary reports and in certain SDK notes, but there is no single, unambiguous public confirmation from both Epic and Nintendo enumerating a Switch 2 EAC integration at the same level of detail as the Windows on ARM announcement. Treat Switch 2 support as plausible and developer‑oriented (the EOS ecosystem already supports Nintendo platforms), but flag it as not fully verified until Epic or Nintendo publish explicit, platform‑level release notes describing EAC artifacts for Switch 2.Security, privacy, and operational risks — a balanced analysis
Porting kernel‑mode anti‑cheat components to a new architecture is an engineering victory with non‑trivial tradeoffs. The three risk categories to watch are:- Stability and driver fragility. Kernel bugs cause blue screens and data loss. ARM and x64 kernels differ in ABI and subtle behavior; rigorous QA and staged rollouts are essential to avoid shipping destabilizing drivers. Historical EAC driver interactions with Windows updates show how quickly the surface area can produce breakage.
- Windows hardening interactions. Features like Memory Integrity (Core Isolation) and hardware‑enforced stack protection can block drivers not built with proper compatibility. Anti‑cheat vendors must align with Microsoft’s kernel security guidance and signing models to avoid forcing users to disable important protections.
- Telemetry, privacy, and trust. Kernel‑level anti‑cheat necessarily increases what vendors can observe. Players, enterprise IT admins, and privacy advocates will expect clear disclosures on what data is collected, retention windows, and opt‑out/repair flows. Poor communications will create backlash and support headaches.
Developer checklist — practical steps to ship ARM‑aware builds
- Download the latest EOS SDK that advertises Windows‑on‑ARM EAC support and review the release notes in detail on Epic’s developer portal.
- Replace or update the EAC anti‑cheat bootstrapper used by your installer/launcher so the ARM client is deployed on ARM devices.
- Include/test the ARM‑native anti‑cheat client module in your build or ensure your launcher can fetch and repair it at install time.
- Validate interactions with Windows security features (Memory Integrity, Secure Boot, hardware stack protection) and confirm driver signing and certificates across your QA matrix.
- Run representative tests on Snapdragon X variants (X, X Plus, X Elite) with Auto SR and Prism-enabled profiles, and collect telemetry for false positives and crash metrics.
Practical guidance for consumers, IT admins, and OEMs
- Gamers: If a single multiplayer title is the reason you’re buying an ARM device, verify the publisher has shipped ARM‑aware anti‑cheat components for that specific game before purchasing. Many titles will still require updates from publishers.
- IT / fleet admins: Treat early ARM anti‑cheat rollouts as pilot projects. Test install and repair flows across representative hardware and document support playbooks before wide distribution. Avoid disabling Windows security features as a workaround.
- OEMs: Use EAC ARM support as a marketing point for Copilot+ gaming capabilities, but keep performance and compatibility messaging realistic; emulated x64 builds may still underperform compared with x86 laptops for some AAA titles.
Microsoft’s other platform items — Prism and Auto SR
Epic’s EAC port sits inside a larger Microsoft push to make ARM gaming viable. Microsoft’s improved Prism emulator expands the range of x64 code that can run on ARM devices, and the operating system now exposes Automatic Super Resolution (Auto SR) — a built‑in AI upscaler that lowers rendering resolution and uses the device’s NPU to upscale frames, improving frame rates on qualifying Copilot+ machines. Auto SR works out of the box for a curated list of titles and can be enabled per‑game; it requires Windows 11 24H2 and Snapdragon X hardware. Those platform improvements substantially improve the playability of emulated titles even where pure performance parity is not achieved.Timeline and expectations
Epic’s March 2025 announcement indicated Fortnite will be a first mover and that broader adoption would follow “later this year.” The EOS SDK packaging with the ARM EAC client is now available to developers; however, real availability for players depends on:- Publishers pushing updated builds with the new bootstrapper and client.
- Other anti‑cheat vendors shipping their own ARM drivers for titles that do not use EAC.
- Continued platform hardening and driver signing alignment between Microsoft and vendors.
Conclusion — a pivotal step, not the finish line
Epic Games’ ARM port of Easy Anti‑Cheat is a substantive, infrastructure‑level win for the ARM gaming story. Packaging ARM support into the EOS SDK removes a historically painful compatibility blocker and gives developers a standardized path to bring multiplayer experiences to Snapdragon‑powered Windows and Linux ARM devices. Combined with Microsoft’s Prism emulation improvements and Auto SR upscaling, the practical viability of ARM as a gaming platform has never been stronger.That said, the victory is tactical, not total. Performance parity, publisher engagement, and vendor diversity of anti‑cheat support will determine how broadly ARM devices become mainstream gaming platforms. Kernel‑mode code must be shipped with meticulous QA, transparent telemetry policies, and careful coordination with Windows security features. For players and admins, the sensible approach is cautious optimism: the anti‑cheat gate is open, but the broader work of porting, optimizing, and validating multiplatform builds continues.
For developers and publishers, the message is clear: the toolchain is available — update your EOS/EAC integration, validate on representative ARM hardware, and prepare clear messaging to players. For OEMs and Microsoft, execution now matters: ensure update flows, support pages, and compatibility signals are unambiguous so buyers can reliably know which titles will work locally on ARM devices.
This change removes one of the most visible technical barriers to ARM gaming. The next 6–12 months will reveal whether momentum, publisher economics, and vendor coordination are enough to turn that technical possibility into a widely usable reality.
Source: Tom's Hardware Epic Games adds Easy Anti-Cheat for ARM devices — Feature unlocks support for Windows, Linux, and Switch 2
Last edited: