Battlefield 1 PC stuck on Easy Anti Cheat loading screen

I have also just tried deleting all game files from Steamapps Common and Documents, and reinstalling from there. Still no luck.

This is the only error message I have received, and I only get it after trying to run from a fresh install. Every subsequent attempt I get no error message.

Hey there, 

I'm sorry to hear you're having problems launching BF1. Since the error seems to be with the EA anticheat, you can try downloading its installer directly from our website and run the installer as admin. 

1. Download the EA Javelin Anticheat installer.
   • The link will automatically download the installer onto your browser.
2. Select the game you want to add EA Javelin Anticheat to.
3. Select Install.

Please give that a go and let us know if that helps. 

Hi, I've already tried that. I tried uninstalling and reinstalling just now, as well as repairing - all to no avail.

Look in Windows Event Viewer for any error codes for Battlefield 1 or EA anticheat.

Perhaps there's an app or program running in the background that could be causing a conflict with the anticheat. To rule that out, you can try a Clean Boot:

How to clean or safe boot your computer

So I looked through the Event Viewer logs and found a system error showing "The EAAntiCheatService service terminated with the following error: 0x4294901870" (translates to "The system cannot find the file specified")

Troubleshooting Steps Taken:

1. Identified Service Status Issue:
   • Checked Windows Services and found EAAntiCheatService stuck in "Starting" state
   • Changed startup type to Automatic but service never fully started
2. Attempted Service Management:
   • Tried net stop EAAntiCheatService and net start EAAntiCheatService commands
   • Received "System error 87: The parameter is incorrect"
   • Attempted to delete service via sc delete command - same Error 87
3. Registry Investigation:
   • Examined registry entries at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
   • Found two entries: EAAntiCheat (driver) and EAAntiCheatService (service)
   • Registry values appeared correct with proper ImagePath settings
4. Root Cause Discovery:
   • Registry showed EAAntiCheat driver pointing to system32\drivers\eaanticheat.sys
   • Critical Finding: The file eaanticheat.sys is completely missing from C:\Windows\System32\drivers\ folder
   • This explains why the service cannot start - the required driver file doesn't exist
5. Reinstalling / Repairing EAAntiCheat
   • Attempted to reinstall / repair EAAntiCheat for BF1 and restart computer
   • BF1 still won't open, stuck on EAAntiCheat starting.

I believe the core issue is that eaanticheat.sys is completely missing from C:\Windows\System32\drivers\ folder, but I have no idea how to fix this... I try to uninstall and reinstall, but no luck.

Could the issue still be that there is a background app or program? Or does the above chain of events prove that this is not the issue?

What can I do?

Does your Windows account have administrator privileges? To determine if your Windows account has administrative privileges, navigate to Settings > Accounts > Your info. If the account is an administrator, it will be indicated under your name,

I have played BF1 (also own BF V and 4) since it came out on an old i7 (4790). It was my favorite game of all time, actually. In Dec '24 I upgraded to a Ryzen (9700x) and my PC freezes 30 secs after launch due to a poorly tested anticheat upgrade.

I have tried everything and NOTHING works. Fast-forward to 8 months later: still no fix on your end, despite multiple reports and forum threads regarding Ryzen rigs with this sort of issue.

I wish I could go back in time and not give EA a dime of my money.

Congratulations on ruining your games for loads of people just cause your devs are incompetent/unable to test their stuff before launching!!

krasnyj_dome​  So this issue is being caused by some programs that interfere with the anti cheat. The usual suspects are Asus armory crate, Asus game first, Norton, Malwarebytes, RGB software and Daemon tools.

Closing those should help and if that doesn't do it then uninstalling them will.