Battlefield 6 Crashing ~20 Seconds After Launch — How to Fix It
If Battlefield 6 launches fine and then crashes to desktop about 15–30 seconds later — very often right around 20 seconds, usually with no error message — the cause is almost certainly Windows 11 optional preview update KB5124010 (rolled out ~22 Sep 2026). It conflicts with the game's kernel anti-cheat and force-closes it seconds after launch, and it's been reported to crash other anti-cheat games too. The confirmed fix is to uninstall KB5124010 and restart; it's an optional, non-security preview, so removing it is safe. If you don't have KB5124010 installed, it's a local crash — the fallback fixes are below.
Error codes
Crash to desktop ~15–30s after launch (no error message)
Battlefield 6 reaches the menu or the start of a match, then closes to desktop roughly 15 to 30 seconds later — very often at almost exactly 20 seconds — usually with no error dialog at all.
Cause: Windows 11 optional preview update KB5124010 (rolled out ~22 Sep 2026 to 24H2/25H2). It conflicts with the game's kernel-level anti-cheat, force-closing the process seconds after it starts. Microsoft has not acknowledged the gaming issue yet.
- Uninstall KB5124010: Settings > Windows Update > Update history > Uninstall updates > remove '2026-09 Preview Update (KB5124010)', then restart. This is the only confirmed self-service fix right now.
- This was an OPTIONAL preview update — you do not lose any security patch by removing it. After uninstalling, do NOT click 'Check for updates' (that can re-offer it); let it stay off until Microsoft ships a fix.
- If you can't find KB5124010 in the list, you likely never installed the preview — your crash is a different cause (see the EAC-repair and driver steps below).
- Pause Windows Updates for 1–2 weeks after uninstalling so the preview isn't silently reinstalled before a fixed build lands.
Anti-cheat / EasyAntiCheat error on launch
The game closes immediately or throws an anti-cheat error before you reach a match, distinct from the ~20-second post-launch crash.
Cause: Kernel anti-cheat failing to initialise — either the KB5124010 conflict above, or a separate driver/overlay conflict on your PC. KB5124010 has been reported to crash multiple EAC titles, not just Battlefield 6.
- Run the anti-cheat repair: game install folder > EasyAntiCheat > EasyAntiCheat_Setup.exe > Repair, then reboot.
- Close RGB/overclock/monitoring tools (older MSI Afterburner/RivaTuner, fan-control utilities) before launching — their kernel drivers commonly trip anti-cheat.
- Add Battlefield 6 and its anti-cheat to your antivirus exclusions so the driver can load.
- Update your GPU driver to the current release; a partially-updated driver can crash Vulkan/DX12 titles at load.
Crash after launch with KB5124010 NOT installed
You crash within a minute of launching but confirmed KB5124010 is not in your update history.
Cause: A local instability — GPU driver, corrupted shader/game files, or an overlay hooking the process.
- Verify/repair game files through your launcher (Steam: Properties > Installed Files > Verify; EA app: Repair).
- Disable in-game overlays (Discord, GeForce Experience, Steam) which can crash anti-cheat titles at launch.
- Delete the shader cache and let it rebuild; a corrupt cache crashes DX12/Vulkan renders seconds in.
- Do a clean GPU driver reinstall (DDU in safe mode, then the latest driver).
Fixes that work for most Battlefield 6 errors
- First check whether Windows 11 preview update KB5124010 is installed (Settings > Windows Update > Update history). If it is and you crash ~20s after launch, uninstalling it is the fix.
- KB5124010 was an optional, non-security preview — removing it costs you nothing and is reversible.
- After uninstalling, pause updates and avoid 'Check for updates' so the preview isn't re-offered before Microsoft patches it.
- If KB5124010 is not installed, treat it as a local crash: repair anti-cheat (EasyAntiCheat_Setup.exe > Repair), verify game files, update GPU driver, disable overlays.
- Watch the official Battlefield channels — once Microsoft or EA ships a fix, reinstalling the superseding Windows update will be safe.
FAQ
Why does Battlefield 6 crash exactly 20 seconds after launch?
It's almost always Windows 11 optional preview update KB5124010 (~22 Sep 2026), which conflicts with the game's kernel anti-cheat and force-closes it 15–30 seconds after launch. Uninstall KB5124010 and restart.
Is it safe to uninstall KB5124010?
Yes. KB5124010 was an optional, non-security preview update, so removing it doesn't drop any security fix. After uninstalling, pause updates so it isn't reinstalled automatically.
How do I uninstall KB5124010?
Settings > Windows Update > Update history > Uninstall updates, find '2026-09 Preview Update (KB5124010)', remove it and restart. Then avoid clicking 'Check for updates' until a fix ships.
Battlefield 6 still crashes and I don't have KB5124010 — what now?
Then it's a local issue: run EasyAntiCheat_Setup.exe > Repair, verify game files, disable overlays, and do a clean GPU driver reinstall.
Has Microsoft fixed the KB5124010 game crashes?
As of late September 2026 Microsoft has not acknowledged the gaming issue. Until a superseding update lands, keep KB5124010 uninstalled and updates paused.
Other games
- Civilization VII Errors — Crash at Startup, Not Launching, Vulkan/DX12 & Fixes
- Dune: Awakening Error Codes — P34, H74, 873, P64, Q62, FG3 & M52 Fixes (2026)
- Assassin's Creed Shadows Error Codes — DX12 0x887a0006, 0x80070057, ANIMUS & Fixes
- Kingdom Come: Deliverance II Errors — Crash at Startup, DX11/DX12, Nvidia 572.16 & Fixes
- Split Fiction Errors — 'UE-Split Game Has Crashed' Fatal Error, DX11/DX12 Crash & Fixes
- S.T.A.L.K.E.R. 2 Error Codes — 887A0006 (D3D12 Device Removed), LowLevelFatalError, Shader Crash & Fixes
- Black Myth: Wukong Error Codes — Denuvo 'Something Went Wrong', Error 577, D3D12 Device Crash & Fixes
- Cyberpunk 2077 Error Codes — Access Violation, 0xC000001D, Flatlined, CE-34878-0 & Fixes