x86 Win32 Deprecation?

The docs state “If your game runs on any of these operating systems, you can continue to use EOS SDK 1.18.1.2 (or lower) but to update to EOS SDK 1.19.0.3 or higher, you must change your game to run on 64-bit Windows or 64-bit Android higher than OS 7.”

Is 1.18 guaranteed to work ‘forever’? We used EOS to refresh a legacy project and don’t plan on moving it to x64.

And what are the implications of this on Easy Anticheat? Will x86 titles still be able to utilize EAC and receive updates?

There is no explicit guarantee of indefinite support. Per the EOS Developer Agreement, Section 5.1, Epic commits to backward compatibility for up to 3 years from the date of an SDK release. After that period, Epic will use “commercially reasonable efforts,” but is not obligated to maintain support for prior versions. SDK 1.18.1.2 will not receive bug fixes or security patches.

EAC requires a 64-bit Windows OS, but it does support protecting 32-bit (x86) game executables running on 64-bit Windows via WoW64.

The EAC client module is fetched dynamically at each game launch and is not tied to your EOS SDK version. This means your x86 title on SDK 1.18.x should continue to receive anti-cheat module updates (bug fixes, detection improvements) independently, though this is not a guarantee.

Did you update the bootstrapper from a later SDK version? There is this note on client module 9840 that can easily be missed (I’ll see if we have this information at least in the docs and release notes).

Note: This and newer releases require start_protected_game.exe from a recent EOS SDK (v1.16 or newer). It's not required to update the entire EOS SDK; just replacing start_protected_game.exe with a newer version is enough.

Can you share bootstrapper and EOS SDK logs from both runs (1 with the older module, and 1 with the newer module)? EOS SDK logs should be written to your game logs (look at EOS_Logging_SetCallback to see where they are going). Bootstrapper logs are in a subfolder of %AppData%\Roaming\EasyAntiCheat.

Can you also confirm you are testing on a 64-bit operating system?

Thanks for the logs. I can reproduce this on my end using our sample. I’m talking with our anti-cheat engineering team.

It is unexpected for client modules to not work on 32-bit applications on 64-bit OS. We’re working on a fix. Any chance you could share a Steam (or other storefront) key with us? We’re looking for a game to test the fix with.

We released a new client module with a fix.

Thanks for the reply & information.

However, for EAC, after upgrading to module 11058/v2601.0 (and all above modules), 32bit applications will no longer work:

Launcher finished with: 210, ‘Failed to start the game (2)’.

I reproduced this without our game / with a simple console app - x86 and x64 builds - the x64 build works, x86 failed with the above error.

Yes. We are using the final x86 EOS SDK and matching start_protected_game (EOS-SDK-47370208-Release-v1.18.1.2) and EAC tools/dist EOS_AntiCheatTools-win32-x64-2.2.0 from inside that SDK zip

start_protected_game.exe from EOS-SDK-49960398-Release-v1.19.0.3 exhibits the same issue.

If we revert the AC module back to 10986 - v2512.0 Dec 18, 2025, 09:36 AM EST, everything works as expected. Anything after that breaks with x86 (works with x64)

Multiple machines have encountered this, and they are all running 64-bit Windows 11.

I’ve linked two EAC logs below, good and bad:

Good - [01:00:45:513] [Windows] [EAC Bootstrapper] [Info] Log file open, 2026-04-21 01: - Pastebin.com

Bad - [00:58:38:451] [Windows] [EAC Bootstrapper] [Info] Log file open, 2026-04-21 00: - Pastebin.com

Bad is running - 11790 v2604.0 Apr 16, 2026, 08:20 AM EDT

Good is running - 10986 v2512.0 Dec 18, 2025, 09:36 AM EST

I do not have a game log file or anything from EOS_Logging_SetCallback because the process doesn’t get that far. I added a Win32 msgbox as the first line in WinMain and it didn’t even hit that.

We have enabled this module and tested it and it works!

Thank you for all of the help