BF6 fails to launch since July 1, 2026 update

Battlefield 6 worked correctly through June 30, 2026. After the update released July 1, 2026, the game no longer launches. The EA Javelin AntiCheat splash screen appears, disappears, and the game window never opens. No bf6.exe process appears in Task Manager under normal viewing; under closer inspection (Process Explorer, admin mode) bf6.exe does briefly appear but remains permanently in a Suspended state with a single thread, and is eventually killed after ~40 seconds along with EAAntiCheat.GameService.exe.

System specs:

• CPU: Intel i9-14900K
• GPU: RTX 5080 (tested on both current and several-releases-old Nvidia driver — identical result)
• Motherboard: MSI Tomahawk Z790
• OS: Windows 10
• Secure Boot: Enabled, Custom mode (maximum security configuration) — confirmed via BIOS
• Game installed on Steam library, drive G:

Event Viewer sequence on every launch attempt (Application log):

1. EAAntiCheatService — Failed retrieving service path
2. Service Control Manager — Event ID 7023 (EAAntiCheatService did not respond in a timely fashion / entered STOPPED after START_PENDING)
3. EAAntiCheatService — ExitType: 95 (267) ×2

This sequence repeats identically on every single launch attempt.

Process behavior observed (Process Explorer, run as Administrator):

• EAAntiCheat.Installer.exe, EAAntiCheat.GameService.exe, and EAAntiCheat.GameServiceLauncher.exe all launch, then intermittently flip between Running/Suspended.
• bf6.exe is created but remains permanently Suspended (1 thread) until killed.
• Resource Monitor confirms partial network activity during this window: EAAntiCheat.Installer.exe received 5003 bytes, EAAntiCheat.GameServiceLauncher.exe received 1162 bytes — so network requests are being sent and partially answered, not simply blocked/timing out at the connection level.
• Right-click "Analyze Wait Chain" is greyed out/unavailable on all EA AntiCheat processes and on bf6.exe even when run as Administrator, presumably due to Protected Process Light (PPL) protection, preventing further diagnosis via standard OS tools.

Troubleshooting already performed (all unsuccessful):

• Full uninstall/reinstall of EA AntiCheat via EAAntiCheat.Installer.exe (Uninstall All → Repair), both from the game folder and from C:\Program Files\EA\AC
• Manual deletion of EAAntiCheatService and EAAntiCheat registry service entries (sc delete), followed by manual recreation (sc create EAAntiCheatService binPath=... start=auto) — service creates successfully but identical failure persists on next launch
• Steam "Verify integrity of game files" — 907/907 files pass
• Full uninstall and clean reinstall of Battlefield 6 itself — no change
• Nvidia driver: tested both latest and a several-releases-old driver (from before July 1, when the game worked) — identical result on both
• Secure Boot confirmed Enabled in Custom mode (not just default Enabled)
• Antivirus (third-party, B2C) fully disabled during testing
• Clean boot via msconfig (all non-Microsoft services disabled)
• PC fully rebooted between every test
• No background overlay software running during tests (Discord overlay, MSI Afterburner, Logitech G HUB — all closed)
• Tested on two completely independent internet connections: home Rostelecom WiFi and a mobile USB modem via a different carrier (Beeline) — identical result on both, network connection type is not the variable
• No third-party software changes to the system in the last 6 months except KOMPAS-3D CAD software (installed ~2 months ago, game worked fine for 2 months with it present, since uninstalled to rule out — issue persists identically)
• Windows Event Viewer checked for Windows Defender / ASR rule interference — none found relevant to the failure window
• Memory Integrity / Core Isolation (HVCI) already disabled

Request:
Given the consistent, reproducible signature (Failed retrieving service path → Event ID 7023 → ExitType 95 (267) ×2, service stuck in START_PENDING, bf6.exe created but never resumed) and that every plausible local/user-side cause has been methodically ruled out, this appears to be a backend/installer-side regression in the Javelin AntiCheat service introduced by the July 1, 2026 update, rather than a local configuration issue. Requesting escalation to engineering rather than standard first-line troubleshooting steps, as those have already been exhausted.

Happy to provide: full Event Viewer export, Process Monitor trace, DxDiag, or any additional logs on request.