Apex Legends stuck at Easy Anti-Cheat (EOS) init since Aug 21 2026 update
Since the August 21, 2026 update, Apex Legends fails to launch. The game freezes at the "Initializing" screen with the message "Easy Anti-Cheat Bootstrapper (EOS) is not responding." If left long enough, it eventually fails with "The Easy Anti-Cheat launcher encountered an internal error." The game worked perfectly before this update.
Key diagnostic finding: If I completely disable Wi-Fi/network before launching, the game passes this freeze screen without issue (it then stops at a later screen due to no internet connection, which is expected). However, whenever any network connection is active — tested on my home Wi-Fi, phone Wi-Fi hotspot, and USB tethering — the freeze reproduces identically every time. This strongly suggests the issue lies in EAC's initialization/network handshake process itself, not in my local network path.
System specs:
- OS: Windows 10 Pro (version 10.0.19045, 22H2)
- CPU: Intel Core i7-7700K @ 4.20GHz
- Motherboard: ASUS (custom-built PC), UEFI mode, Secure Boot enabled, CSM disabled
- Network adapter: Intel Wi-Fi 6 AX200
- Purchased via: Steam
Troubleshooting already attempted (no change from any of these):
- Verified integrity of game files via Steam
- Reinstalled/repaired EAC via EasyAntiCheat_EOS_Setup.exe (install/repair/qa-factory-reset, including with correct productid)
- Fully removed and re-registered the EAC Windows service
- Completely uninstalled antivirus software (Trend Micro)
- Fully disabled Windows Firewall
- Disabled IPv6, reset Winsock/TCP-IP stack (netsh winsock reset)
- Ran sfc /scannow (repaired some corrupted files, no change in symptom)
- Reinstalled Visual C++ Redistributables
- Enabled Secure Boot and disabled CSM in BIOS
- Fully closed/uninstalled background software (Razer Synapse, EPOS Gaming Suite)
- Deleted EAC cache folders (%APPDATA%\EasyAntiCheat)
- Tested with a brand-new Windows user account — same result
- Reviewed Application/System/CAPI2 event logs — no relevant errors found
I've ruled out essentially all local causes I can control. This appears to be a regression introduced by the August 21 update, likely on the client or EAC server-side handshake. Any guidance or a fix timeline would be greatly appreciated.
