Apex shows AntiCheat verification failed [4]
Hello EA technical team. I am asking you to investigate what this Apex authentication error means. I have no known ban, but Apex says that anti-cheat verification failed and that my profile does not have permission to play online.
One fact should be clear before the standard troubleshooting is suggested: BF6 also fails with every game accelerator, VPN/proxy, and Steam++ fully closed, including tests on campus wired Internet, a mobile hotspot, and mobile tethering through another carrier. Those tools have also been present during both successful and failed sessions, so they cannot be assumed to be the cause. I have already completed the usual checks for closing the tools, changing network paths or DNS, resetting Windows networking, clearing or verifying/reinstalling the game, reinstalling EA AntiCheat, and checking firewall and third-party components. None produced a stable fix. Please review the Apex EA AntiCheat verification, device-attestation, entitlement, and server-authentication records for the relevant timestamps.
On October 26, 2026, Apex ran for about 8 minutes 36 seconds but never reached a match. It first showed a server timeout (`code:house`), then displayed “the client is not running the anti-cheat system, or anti-cheat verification failed [4]” and “this profile does not have permission to play online.” The account can sign in, and I have no known ban or enforcement notice.
What I have checked:
1. **The exact failure sequence.**
This was not a mid-match kick. Apex failed during the login/connection stage: server timeout first, then the EA AntiCheat [4] message and the online-permission wording. I do not know whether the permission message is a real entitlement failure or a generic message shown after authentication fails.
2. **Account status.**
The account can log in and has no known ban record. A second EA account was also used during the Battlefield investigation, and the wider EA-game symptoms were reproduced there as well. This does not look like one account simply being unable to use EA services, although only EA can check the complete backend account state.
3. **EA AntiCheat versions and service state.**
During this Apex launch, the global EA AntiCheat installation changed to 1.0.16199215. BF6/BF1/BFV launch flows had used 1.0.16162060. The version changes may be normal when launching different games, but I do not know whether they matter. In the Battlefield tests, EAAC reported Running even when the game later failed, so a running service does not prove that attestation succeeded.
4. **Other EA games as a comparison.**
BF6 usually failed after 5-8 minutes with 0.85009S and sometimes failed while idle in the menu. BFV had one short-session disconnect at about 6:35, and BF1 had early 6-7 minute connection failures. BF4 ran for 16:35 on the same PC and mobile connection. This makes a shared newer EA authentication, device-attestation, or session path worth investigating, but it does not prove that all of these games have one confirmed bug.
5. **Different accounts and PCs.**
Two EA accounts and two PCs were used during the initial investigation, and the relevant EA-game symptoms were reproduced. Both accounts could log in and enter games, with no clear ban message.
6. **Different networks and accelerators.**
For the BF6 investigation, I first closed all game accelerators, VPN/proxy software, and Steam++ and tested campus wired Internet, a mobile hotspot, and USB tethering through another carrier. Short failures still occurred. I then tested with a game accelerator enabled and with a VPN/proxy enabled; failures still happened, although there were also some successful sessions with those tools on. “Close the accelerator/VPN and try again” has already been tested and is not a reliable fix. Campus wired also has a separate session-establishment problem, but switching to mobile data did not guarantee stable Battlefield sessions.
7. **Reinstalling the games, EAAC, and Windows.**
BF6 was fully reinstalled and verified through Steam. Battlefield and EA App caches were rebuilt. EA AntiCheat services, registry entries, and its program folder were removed and reinstalled. Windows 11 was installed cleanly. None of these steps produced a reliable, repeatable fix for the wider EA-game symptoms.
8. **Windows security and third-party components.**
I checked DNS, firewall/routing, TPM/Pluton, Secure Boot, HVCI/VBS, clock, USB devices, IPv6, Huorong, Tencent ACE, game-accelerator WFP filters, VMware networking, and hardware-monitor drivers. Steam++, VPN/proxy software, and hosts were tested with the relevant tools closed and enabled. No local error was found that clearly explains the Apex authentication failure.
9. **Packet captures and network resets.**
The Battlefield investigation collected more than one million UDP packets. Failed sessions generally still had bidirectional traffic before ending, and separate TCP/UDP probes ran for 15 minutes. I also used the Windows network reset, Winsock/IP/TCP resets, and `netcfg -d`; one reset happened to be followed by several successful sessions, but later resets did not reliably fix anything. I therefore do not consider the network reset a confirmed solution.
I am asking EA to review the timestamps against the EA AntiCheat verification, device-attestation, account-entitlement, and server-side authentication logs. Please explain what “verification failed [4]” and “this profile does not have permission to play online” mean in this case, including whether the permission wording is only a generic consequence of the authentication failure. I need the diagnostic result and targeted corrective steps rather than another generic reinstall checklist; the relevant game, anti-cheat, Windows, and network checks have already been completed without a stable fix.
