Game won't launch with AntiCheat v2601.0 or v2601.1

When I enable the version v2601.0 or v2601.1 my game won’t launch, the splash screen just closes after loading and game will never open. How do I debug this?

The latest version that it works is v2512.0, I always updated the AntiCheat normally and it always worked.

My windows is 11 25H2 build 26200.7623 (but the problem is for all players, even windows 10 etc).

SDK version is latest (v1.18.1.2).

Nothing shows up on Windows event viewer so i have no idea how to debug this issue.

Someone help, please?

Hi, if you haven’t already, we would advise you to revert your client module to the older version that still works (v2512.0) while we investigate the problem with you.

Can you confirm if the client simply never launches, or if it launches and immediately closes?

Could you provide the service and bootstrapper log files? You’ll find directions for obtaining them here.

[Content removed] Herd​ I’m sorry it it seems like spamming comments but as a developer i believe the more context the better to find out the issue.

I noticed with Process Monitor that before the process exits it tries to access (or create) a file ending with 00001.log at C:\Windows\Logs\MeasuredBoot i mean, it tries 0000001256-0000000001.log but only 0000001256-0000000000.log exists

there is also one with same name but ends with .json with this content:

{“Version”:1,“HealthStatus”:“Attestable”,“Required”:[{“Field”:“TpmPresent”,“Value”:true,“DesiredValue”:true},{“Field”:“TpmMeetsMinimumVersion”,“Value”:true,“DesiredValue”:true},{“Field”:“TpmIsResponsive”,“Value”:true,“DesiredValue”:true},{“Field”:“EkCertIsAvailable”,“Value”:true,“DesiredValue”:true},{“Field”:“TcgLogFound”,“Value”:true,“DesiredValue”:true}],“Expected”:[{“Field”:“PcrsMatchTcgLog”,“Value”:true,“DesiredValue”:true}],“Informational”:[{“Field”:“SecureBootEnabled”,“ValueFromComputer”:false,“ValueFromTcgLog”:false,“DesiredValue”:true,“TcgValueIsVerifiable”:true},{“Field”:“VirtualSecureMemory”,“ValueFromComputer”:false,“ValueFromTcgLog”:false,“DesiredValue”:true,“TcgValueIsVerifiable”:true},{“Field”:“SecureCorePCCompliant”,“ValueFromComputer”:false,“ValueFromTcgLog”:false,“DesiredValue”:true,“TcgValueIsVerifiable”:true}{“Field”:“BootTcgLogFoundInFileSystem”,“Value”:true,“DesiredValue”:true},{“Field”:“CurrentTcgLogFoundInFileSystem”,“Value”:true,“DesiredValue”:true}]}

the .log i can’t put here in chat because it’s 77KB and is not “readable”, maybe needs a custom program to read, i’ll try to attach here but not sure it will work.

I’m guessing a change introduced in v2601.0 (also presents in v2601.1) related to this MeasuredBoot?

It says safe boot disabled in json (i believe is settings in bios) but i forced enable (also core isolation) and didnt help.

But version v2512 (and all previous) always worked fine (with core isolation enabled or not, always work), and like i said the problem is not just me, other players also can not run game with v2601+

i just tried the v2601.2 released today (feb 4) and also does not work :sob:… latest working version is still v2512.0

Is my game really the only one with this problem? It does not make sense…

Hi, thanks for all of this additional information. The exit code you’re seeing indicates a stack overflow, so there’s likely some unexpected interaction in those newer modules.

You mention that you’re not initializing EOS. Are you not using any of the other EOS services? The anti-cheat relies on other EOS services to function correctly. Was the anti-cheat actually working on the older modules before you encountered this error?

Hey [Content removed] Herd​ I still can’t update to never versions, i’m stuck in v2512.0.

I was wondering, is it because my game binary is 32-bit? EOS no longer supports 32 bits? And will eventually stop working for all older games..?

I checked here https://dev.epicgames.com/docs/epic-online-services/release-notes and it says “Windows: EOS SDK releases higher than 1.18.1.2 will not support 32-bit binaries. If your product uses 32-bit binaries you must use SDK 1.18.1.2 or earlier.” but I don’t know if it’s only about SDK version or also anti cheat build version, but probably both. My sdk current version is 1.18.1.2 and latest build that works on my game is v2512.0.

I’m have the same issue.

Setup: 64-bit Windows (reproduces on both Windows 10 and Windows 11), start_protected_game.exe from the latest EOS SDK, 32-bit game client.

The problem reproduces with any x86 binary - even a blank Desktop Application (Classic Windows App) template from Visual Studio built as x86.

The same project rebuilt as x64 runs fine through the same bootstrapper; x86 always crashes.

anticheatlauncher.log: [Windows] [EAC Bootstrapper] [Info] Launcher finished with: 210, ‘Failed to start the game (2)’.

Process Monitor on the child process: process exit with status 0xC0000005

2026-04-28 status: they fixed it TODAY, thanks! The fix is in version v2604.1 (description of the version is “Fixed EAC crashing for 32-bit games.”).

Hi [Content removed] Herd​ !

Yes in production I reverted back to v2512.0 already.

I just tried the v2601.1 again and still have the same problem.

My game does get open (I don’t see it, it “immediately” closes but i dont even see the window), I know the executable gets opened because i added a OutputDebugString(“test”); in my game’s code and i was able to see it with DbgView program.

I found service.log at C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\EasyAntiCheat but I dont think this one is useful, because it’s always the following two lines, no matter if is the version that works or the version that does not work:

[EAC Setup] [31804] [17:09:03:582] [Info] Process started, running as admin: true.

[EAC Setup] [31804] [17:09:03:582] [Info] Started with ‘’.

But I found anticheatlauncher.log at C:\Users\MyUser\AppData\Roaming\EasyAntiCheat\myproductid\mydeploymentid\

which might be useful, I’m attaching the file here.

Oh, and in my game’s code i’m not even calling EOS_Initialize or anything of EOS, so I’m sure it’s not related to how i call functions.

Oh, when I said “i’m not even calling EOS_Initialize or anything of EOS” I meant i stopped calling just to test if it was a problem during the call or something, so it confirmed it’s not related to calling EOS functions.

I do use the service, currently i only use “EOS_Initialize” to check if anti-cheat was properly loaded (but like I said, i tried to stop calling the function to make sure it’s not related to that), heartbeat i haven’t implemented yet.

Yes anti-cheat was (and still is) working on the older modules, all other previous modules (I always update and it’s been two or three years I’ve been using the EOS anti-cheat, can’t remember exact dates).

So currently I am using v2512.0 because it’s the latest version that it works.

My program doesn’t seem to crash itself, there is no log in event viewer, i feel like this stack overflow might be the EOS closing the program for some reason, a fastfail or something.

If you guys have some ways for me to test new beta/custom builds I would try them, i could even send the game’s download link but you probably can’t test it so i won’t send unless asked.

It’s confusing because version 1.19.0.3 says it stopped working on 32-bit windows, not 32-bit games. My game is 32-bit but works on 64-bit windows

They fixed in version v2604.1, I just updated and it works

How do you use latest EOS SDK with 32-bit game client? They don’t send EOSSDK-Win32-Shipping.lib anymore, only the 64 one

The anticheatlauncher.log file i attached is saying “The file is no longer available”, I’m not sure what happened so here is the details of the version that does not work (v2601.1):

[17:09:00:097] [Windows] [EAC Bootstrapper] [Info] Log file open, 2026-01-30 17:09:00Z.
[17:09:00:097] [Windows] [EAC Bootstrapper] [Info] Loaded the following settings .json file: 'G:\AUBRlocal\EasyAntiCheat\Settings.json'
[17:09:00:097] [Windows] [EAC Bootstrapper] [Info] Provided settings:
[17:09:00:097] [Windows] [EAC Bootstrapper] [Info]  - ProcessTitle: Audition.
[17:09:00:097] [Windows] [EAC Bootstrapper] [Info]  - ExecutablePath: Audition.exe.
[17:09:00:097] [Windows] [EAC Bootstrapper] [Info]  - ProductId: e048083600574e48b87429db59933e50.
[17:09:00:097] [Windows] [EAC Bootstrapper] [Info]  - SandboxId: p-6lvbmqqkfph8jvl3t3vqtvfrfzemlf.
[17:09:00:097] [Windows] [EAC Bootstrapper] [Info]  - DeploymentId: e80f29567d96436e8bc77ee0f05709e0.
[17:09:00:097] [Windows] [EAC Bootstrapper] [Info]  - RequestedSplashScreen: EasyAntiCheat/SplashScreen.png.
[17:09:00:097] [Windows] [EAC Bootstrapper] [Info]  - WaitForGameProcessExit: false.
[17:09:00:097] [Windows] [EAC Bootstrapper] [Info]  - HideGUI: false.
[17:09:00:097] [Windows] [EAC Bootstrapper] [Info]  - HideBootstrapper: false.
[17:09:00:097] [Windows] [EAC Bootstrapper] [Info] System locale: 'pt_BR'.
[17:09:00:097] [Windows] [EAC Bootstrapper] [Info] Failed to load localization file: 'Config parsing error'.
[17:09:00:130] [Windows] [EAC Bootstrapper] [Info] Embedded resources successfully loaded.
[17:09:00:132] [Windows] [EAC Bootstrapper] [Info] Will use the icon extracted from the game executable.
[17:09:00:165] [Windows] [EAC Bootstrapper] [Info] System name: 'win64_wow64'.
[17:09:00:165] [Windows] [EAC Bootstrapper] [Info] Loader initializing with bootstrapper version 1.9.3, architecture: x86-64.
[17:09:00:223] [Windows] [EAC Bootstrapper] [Info] Loader component initialized.
[17:09:00:232] [Windows] [EAC Bootstrapper] [Info] [Connection] Connecting to URL: https://modules-cdn.eac-prod.on.epicgames.com/modules/e048083600574e48b87429db59933e50/e80f29567d96436e8bc77ee0f05709e0/win64_wow64
[17:09:00:321] [Windows] [EAC Bootstrapper] [Info] [Connection] Connect result: No error (0) Response Code: 304 Destination IP: 108.139.182.95
[17:09:00:321] [Windows] [EAC Bootstrapper] [Info] No update needed.
[17:09:06:599] [Windows] [EAC Bootstrapper] [Info] Launcher finished with: 301, 'O Easy Anti-Cheat foi carregado com sucesso no jogo'.
[17:09:06:599] [Windows] [EAC Bootstrapper] [Info] Successfully initialized the Easy Anti-Cheat module, waiting for game window to become visible.
[17:09:06:602] [Windows] [EAC Bootstrapper] [Info] Unlocking the launch lock, allowing next game to launch to take place.
[17:09:08:386] [Windows] [EAC Bootstrapper] [Err!] Fatal error, game process handle: 00000000000006B8, exit code: 3221226505.
[17:09:08:396] [Windows] [EAC Bootstrapper] [Info] Downloaded 1 bytes in 160 ms (0.01 KB/s).
[17:09:08:396] [Windows] [EAC Bootstrapper] [Info] Terminating with: 0.

here is the version that works (v2512.0):

[17:18:24:401] [Windows] [EAC Bootstrapper] [Info] Log file open, 2026-01-30 17:18:24Z.
[17:18:24:401] [Windows] [EAC Bootstrapper] [Info] Loaded the following settings .json file: 'C:\DADOS\aubrplayer\EasyAntiCheat\Settings.json'
[17:18:24:401] [Windows] [EAC Bootstrapper] [Info] Provided settings:
[17:18:24:401] [Windows] [EAC Bootstrapper] [Info]  - ProcessTitle: Audition.
[17:18:24:401] [Windows] [EAC Bootstrapper] [Info]  - ExecutablePath: Audition.exe.
[17:18:24:401] [Windows] [EAC Bootstrapper] [Info]  - ProductId: e048083600574e48b87429db59933e50.
[17:18:24:401] [Windows] [EAC Bootstrapper] [Info]  - SandboxId: 114c5d9ee1a7422ab095563ca8dbf3ec.
[17:18:24:401] [Windows] [EAC Bootstrapper] [Info]  - DeploymentId: b9b8d751a4b24ad79b511a15ba1b0c00.
[17:18:24:401] [Windows] [EAC Bootstrapper] [Info]  - RequestedSplashScreen: EasyAntiCheat/SplashScreen.png.
[17:18:24:401] [Windows] [EAC Bootstrapper] [Info]  - WaitForGameProcessExit: false.
[17:18:24:401] [Windows] [EAC Bootstrapper] [Info]  - HideGUI: false.
[17:18:24:401] [Windows] [EAC Bootstrapper] [Info]  - HideBootstrapper: false.
[17:18:24:401] [Windows] [EAC Bootstrapper] [Info] System locale: 'pt_BR'.
[17:18:24:401] [Windows] [EAC Bootstrapper] [Info] Failed to load localization file: 'Config parsing error'.
[17:18:24:435] [Windows] [EAC Bootstrapper] [Info] Embedded resources successfully loaded.
[17:18:24:436] [Windows] [EAC Bootstrapper] [Info] Will use the icon extracted from the game executable.
[17:18:24:467] [Windows] [EAC Bootstrapper] [Info] System name: 'win64_wow64'.
[17:18:24:467] [Windows] [EAC Bootstrapper] [Info] Loader initializing with bootstrapper version 1.9.3, architecture: x86-64.
[17:18:24:529] [Windows] [EAC Bootstrapper] [Info] Loader component initialized.
[17:18:24:532] [Windows] [EAC Bootstrapper] [Info] [Connection] Connecting to URL: https://modules-cdn.eac-prod.on.epicgames.com/modules/e048083600574e48b87429db59933e50/b9b8d751a4b24ad79b511a15ba1b0c00/win64_wow64
[17:18:24:622] [Windows] [EAC Bootstrapper] [Info] [Connection] Connect result: No error (0) Response Code: 304 Destination IP: 108.139.182.19
[17:18:24:622] [Windows] [EAC Bootstrapper] [Info] No update needed.
[17:18:30:342] [Windows] [EAC Bootstrapper] [Info] Launcher finished with: 301, 'O Easy Anti-Cheat foi carregado com sucesso no jogo'.
[17:18:30:342] [Windows] [EAC Bootstrapper] [Info] Successfully initialized the Easy Anti-Cheat module, waiting for game window to become visible.
[17:18:30:343] [Windows] [EAC Bootstrapper] [Info] Unlocking the launch lock, allowing next game to launch to take place.
[17:18:33:382] [Windows] [EAC Bootstrapper] [Info] The game window has become visible, the bootstrapper will leave the visible state.
[17:18:33:390] [Windows] [EAC Bootstrapper] [Info] Downloaded 1 bytes in 159 ms (0.01 KB/s).
[17:18:33:390] [Windows] [EAC Bootstrapper] [Info] Time spent waiting for the game window to become visible: 3039 ms.
[17:18:33:390] [Windows] [EAC Bootstrapper] [Info] Terminating with: 0.

I did not hide anything since all those informations are public and has no sensitive data, all the three ids are in Settings.json anyway that gets distributed to the players.

I think the problem must be here:

[Err!] Fatal error, game process handle: 00000000000006B8, exit code: 3221226505.