Epic Games has shipped a native ARM version of its Easy Anti-Cheat (EAC) client, removing the single biggest technical barrier that has kept competitive multiplayer titles—starting with Fortnite—off Snapdragon-powered Windows laptops and Linux ARM devices. The updated Epic Online Services SDK (version 1.17.1.3-CL44532354) now bundles an ARM-native anti-cheat driver and an ARM-aware bootstrapper, giving developers a straightforward integration path. Epic will validate the implementation with Fortnite before third-party studios adopt it, and Microsoft’s improved Prism emulator and Auto SR upscaler strengthen the case that Windows on ARM can finally be a gaming platform.

For years, ARM-powered Windows machines—most notably the Copilot+ laptops running Qualcomm’s Snapdragon X Elite and X Plus processors—have been hamstrung not by raw GPU performance, but by the inability to launch many online games. The culprit: kernel-level anti-cheat software that relied on x86‑64 drivers. Without an ARM-native driver, the anti-cheat would fail to load, and the game would refuse to start. EAC, used by hundreds of titles including Fortnite, Apex Legends, and Elden Ring, was the most prominent holdout. With this release, Epic bridges that chasm.

What Epic Shipped

The EOS SDK update distributes an ARM-native EAC client and an updated bootstrapper—the component that installs and updates the anti-cheat on a user’s machine. Game developers who already integrate EAC via the SDK will need to:

  • Update their EOS/EAC dependency to the new release.
  • Repackage their anti-cheat bootstrapper so that ARM devices receive the ARM client.
  • Test the full install, repair, and anti-tamper flows on actual Snapdragon X hardware, paying special attention to interactions with Windows security features like Memory Integrity and Secure Boot.

Epic’s decision to battle-test the integration with Fortnite is strategic: Fortnite’s massive player base and rapid update cadence will stress the ARM client under real-world loads, uncovering corner cases before the broader developer ecosystem follows suit. The company has indicated that wider adoption will occur “later this year,” though individual titles will appear on a staggered schedule as publishers ship updated builds.

Why Kernel‑Level Anti‑Cheat Was the Block

Anti-cheat solutions often deploy kernel-mode drivers to inspect memory, monitor process interactions, and resist tampering. These drivers are written against the Windows x64 kernel API. Microsoft’s Prism translation layer handles user-mode x86‑64 code, but it does not and cannot translate kernel-mode drivers. The Arm64EC toolchain, which allows mixing native ARM and emulated x86 code within a single process, also cannot solve the kernel driver problem—those components must be compiled natively for ARM64. Thus, even games that run acceptably under Prism emulation would silently fail because their anti-cheat driver never initialized.

The Broader ARM Gaming Ecosystem: Prism, Auto SR, and More

Microsoft has been laying the groundwork for ARM gaming since Windows 11 24H2. Prism, its rebuilt x86‑to‑ARM emulator, offers significantly better compatibility and performance than previous translation layers. Auto SR (Automatic Super Resolution) leverages the Snapdragon X NPU to upscale games from a lower render resolution, boosting frame rates on Copilot+ machines without requiring explicit developer integration. These platform enhancements mean that even x64 games running under emulation can become playable on thin‑and‑light laptops, provided the anti-cheat barrier is cleared.

What This Unlocks — And What It Doesn’t

Immediate wins:

  • Fortnite becomes natively playable on Snapdragon X Copilot+ PCs and Linux ARM devices once Epic flips the switch.
  • Hundreds of other EAC-protected titles—including Apex Legends, Rust, Fall Guys, Hunt: Showdown, and Elden Ring—are now technically eligible to run if their publishers opt into the ARM EAC client and ship updated builds.
  • The ARM platform narrative shifts from “can’t play popular multiplayer games” to “games are coming,” which could accelerate hardware adoption.

Remaining hurdles:

  • Performance parity is not automatic. Games that remain x64 and run under Prism will still incur translation overhead, hitting CPU-bound titles hardest. Native ARM64 game builds or carefully crafted Arm64EC hybrids are needed for full performance.
  • Other anti-cheat vendors still need to ship ARM drivers. While BattlEye, Denuvo Anti‑Cheat, and Wellbia XIGNCODE3/UNCHEATER have already released ARM support per Microsoft’s developer communications, many high-profile games rely on solutions like Riot Vanguard (Valorant, League of Legends), EA’s Javelin, and Faceit. These have not publicly confirmed ARM builds, so their games remain blocked.
  • Operational stability and security: Kernel drivers on a new architecture bring fresh risks of blue‑screen crashes, incompatibility with Windows hardening features, and privacy concerns over the data collection that kernel‑level software enables. Rigorous QA and transparent communication will be critical.

Other Anti‑Cheat Vendors and the Fragmentation Puzzle

Microsoft has been coordinating with anti‑cheat vendors to bring native ARM support to Windows on ARM. In its official communications, BattlEye (used in Destiny 2, Rainbow Six Siege, and ARK), Denuvo Anti‑Cheat (Doom Eternal, Deathloop), and Wellbia UNCHEATER (popular in Korean MMOs) are listed as supported. However, the landscape remains fragmented. Riot Vanguard, deeply tied to x64 and Secure Boot configurations, has not announced an ARM version. Similarly, Faceit’s custom anti‑cheat and EA’s newer Javelin system have complex requirements that will need explicit vendor support. Until those vendors release ARM drivers, the games that depend on them—including some of the most popular esports titles—will stay off ARM devices. Fragmentation is not just about if a solution exists, but whether a publisher chooses to implement and ship it.

The Linux and Steam Deck Connection

EAC has long supported Linux through Valve’s Proton compatibility layer, provided developers opt in. This existing Proton support is the reason many EAC‑protected titles work on the Steam Deck. The new ARM EAC client extends that capability to Linux on ARM—a boon for future handhelds, ARM‑based desktops, and Valve’s own Proton ARM tooling improvements. But it’s important to note that enabling EAC for a game via Proton still requires an explicit developer action to include the Linux EAC library in their Steam depot; it’s not automatic. Valve and Epic have streamlined the process over the years, but the developer opt‑in model remains the gating factor.

Security, Stability, and the Kernel Conundrum

Porting kernel‑mode code to ARM64 is an engineering feat with significant operational risks. The ARM and x64 kernels differ in ABIs, memory model details, and driver signing models. A bug in the ARM EAC driver could cause system crashes, data loss, or incompatibility with Windows security features like Memory Integrity and hardware‑enforced stack protection. Historical precedent shows that EAC driver updates have sometimes clashed with Windows patches, so incremental rollouts and robust telemetry are essential.

Additionally, kernel‑level anti‑cheat raises privacy questions. By design, it can observe a wide range of system activity. Epic, Microsoft, and other vendors must disclose what data is collected, how long it is retained, and provide clear repair or opt‑out paths. Enterprise IT departments evaluating Snapdragon laptops will need assurance that these drivers do not compromise fleet security or interfere with compliance tools.

Developer Checklist

For studios that want to bring their EAC‑protected game to ARM players, the practical steps are:

  1. Grab the latest EOS SDK (1.17.1.3-CL44532354 or newer) from Epic’s developer portal.
  2. Replace your EAC bootstrapper with the ARM‑aware version and ensure your installer/launcher correctly deploys the ARM client on ARM64 systems.
  3. Validate the full anti‑cheat initialization on Snapdragon X Elite, X Plus, and X variants, paying attention to driver signing, Secure Boot, and Memory Integrity policy interactions.
  4. Test performance under Prism emulation if your main game binary is still x64, and consider investing in Arm64EC or native ARM64 game builds for competitive performance.
  5. Coordinate with Epic’s EAC support team to monitor false‑positive bans and crash telemetry during the rollout phase.

Advice for Gamers, IT Admins, and OEMs

  • Gamers: If you’re considering a Copilot+ laptop primarily for a specific multiplayer game, explicitly confirm that the publisher has shipped ARM‑compliant anti‑cheat components. Many titles will need time to update.
  • IT admins: Treat early ARM anti‑cheat deployments as a pilot. Test the full install, update, and repair workflow on your chosen hardware. Do not disable Windows security features as a workaround; instead, work with the vendor to address compatibility issues.
  • OEMs: Use EAC ARM support as a marketing point for Copilot+ gaming capabilities, but be realistic: emulated x64 games may still run slower than on a similarly priced x86 laptop. Focus on the growing native game library and the benefits of Auto SR.

A Tactical Victory, Not Yet Total War

Epic’s ARM Easy Anti‑Cheat port is the most significant breakthrough in the Windows‑on‑ARM gaming story to date. By packaging the ARM client directly into the EOS SDK, Epic has given developers a standardized, low‑friction path to support Snapdragon PCs and Linux ARM devices. Combined with Microsoft’s Prism and Auto SR, the technical foundation is finally in place. Yet the victory is incomplete. Performance parity, publisher buy‑in, and the alignment of other anti‑cheat vendors will dictate how quickly—and how thoroughly—the Windows ARM gaming catalog fills out. For now, the gate is open. The next six months will tell us how many publishers walk through it.

Note: The EOS SDK release notes also mention support for Nintendo Switch 2, allowing developers to extend existing Switch integrations. However, neither Epic nor Nintendo has issued a detailed public confirmation of EAC-specific artifacts for Switch 2, so this aspect remains promising but unverified.