Battlefield 6 and other anti-cheat games crash seconds after launch on Windows 11 KB5124010
If games with anti-cheat started crashing to desktop within seconds of launch in the last few days, check whether KB5124010 is installed. It is an optional, non-security preview update Microsoft released on 22 September 2026, and removing it is what players report stops the crashes. Because it is a preview update rather than a security one, taking it off does not cost you September's security fixes - those shipped separately in KB5124008 and the 14 September out-of-band update. Microsoft has not acknowledged the crashes, and the anti-cheat link is still a hypothesis rather than a confirmed cause.
Start here
Two things make this worth checking before you reinstall a game or reset a PC. The first is that the update involved is optional, so a lot of people do not have it and never will. The second is that the reports are consistent about timing - seconds after launch, not minutes into a match - which is a distinctive enough pattern to tell this apart from ordinary game instability.
Symptoms
- A game closes to desktop within roughly 20-30 seconds of launching, often with no error message
- It happens on every launch rather than intermittently
- Battlefield 6 is the most widely reported title; WARDOGS fails with error code WD-L020
- Other titles with anti-cheat are reported less often, including Battlefield 2042
- Games without anti-cheat on the same machine keep working
- Nothing changed on the machine except a recent Windows update
Why this happens
The KB5124010 preview update, in combination with anti-cheat software
Every affected title reported so far carries some form of anti-cheat, and EA's Javelin - which covers Battlefield - is the suspected point of conflict, and both widely reported games use kernel-level anti-cheat. Treat that as the leading hypothesis and not as settled: the reporting is explicit that there is no full confirmation anti-cheat is the cause, only that the affected games have it in common. What is solid is the correlation with one specific update, and that removing that update is reported to restore normal play.
Confirm you actually have KB5124010, and that the crash pattern matches · Remove KB5124010
Microsoft has not acknowledged it, which changes what you should expect
KB5124010's own known-issues section lists only the domain trust relationship problem and the USB Audio Class 1.0 Code 10 problem. Microsoft's Windows 11 24H2 release-health page carried no entry about game crashes as of 26 September 2026. There is therefore no Known Issue Rollback, no out-of-band fix and no published workaround to wait for. That is the practical reason the community answer is removal rather than a setting change.
If you have not installed it yet, simply do not · Remove KB5124010
Fixes
Confirm you actually have KB5124010, and that the crash pattern matches
about 5 minThis update is optional, so plenty of crashing PCs do not have it and need a different answer entirely.
Applies to: Windows 11 24H2, Windows 11 25H2
- Open Start, then Settings, then Windows Update, then Update history. Look for KB5124010 with an install date of 22 September 2026 or later.
- Check your build: press Windows + R, type winver and press Enter. The reported builds are 26100.9550 on Windows 11 24H2 and 26200.9550 on 25H2.
winver - Check the pattern. Reports describe a crash to desktop within roughly 20-30 seconds of launch, on every attempt, in a game that uses anti-cheat. A crash that happens minutes in, or only in one map, is unlikely to be this.
- Confirm the scope: if games without anti-cheat run fine on the same machine, that fits. If everything crashes, look at drivers or hardware instead.
- If KB5124010 is not in your update history, stop here - this page is not your problem.
If you have not installed it yet, simply do not
about 2 minKB5124010 is optional, so skipping it costs nothing in security terms.
Applies to: Windows 11 24H2, Windows 11 25H2
- In Settings, then Windows Update, leave the optional preview update alone - it installs only if you choose "Download and install" under optional updates, or fetch it from the Microsoft Update Catalog.
- Keep taking normal monthly security updates. September's security fixes were KB5124008 on 8 September and the out-of-band KB5129195 on 14 September, both separate from this preview.
- Wait for October's monthly update, which will include the same changes once they have had another month of testing.
Check whether the game has shipped its own fix first
about 10 minA game-side or anti-cheat-side patch solves this without touching Windows, and costs nothing to check.
Applies to: Games using anti-cheat on Windows 11
- Let the game update fully in its launcher, then relaunch. Anti-cheat components often update separately from the game build.
- Check the game's own news or announcements for a post about the Windows update. Team17 acknowledged the WARDOGS crashes publicly, and other publishers may do the same.
- Note that as of 23 September 2026 Team17's stated position was that there was no immediate remedy other than removing the update - so if nothing has changed since, expect to move on to the next step.
Source: TechSpot
Remove KB5124010
Check before applyingabout 15 minThis is the step players across two separate games report as restoring normal play.
Applies to: Windows 11 24H2 build 26100.9550, Windows 11 25H2 build 26200.9550
Before you do this
Microsoft's own guidance is not to remove installed updates casually, and notes that some updates cannot be uninstalled at all. This one is a non-security preview, so removing it does not strip September's security fixes - but the same steps on a security update would, so read the date in the list before you confirm. If the machine will not boot far enough to reach Settings, Microsoft documents removing the latest quality update from the Windows Recovery Environment under Troubleshoot, then Advanced options, then Uninstall Updates.
- Open Start, then Settings, then Windows Update. Under More options select Update history, then under Related settings select Uninstall updates. This is Microsoft's documented route.
- Find the entry for KB5124010 and check the date reads 22 September 2026 before you touch it - you are removing that specific preview update, not September's security update.
- Select it, choose Uninstall, and restart when prompted.
- Relaunch the game and confirm it survives past the first minute.
- Watch for it coming back. Microsoft delivers this one through optional updates and the Update Catalog, so on a normal PC it should not reinstall unless you pick it again. On a PC enrolled in the Windows Insider program it can keep reinstalling itself until you unenroll - if the crashes return after a clean removal, check your Insider status first.
- Treat this as temporary either way. The changes in KB5124010 reach everyone in October's cumulative update, so if the conflict is still unresolved by then, expect it to come back with that update rather than staying away for good.
Reported to work by 4 users; not confirmed by the vendor.
Source: Microsoft, Steam Community, TechSpot, TweakTown, The FPS Review
Known issues
Microsoft has not acknowledged this. KB5124010's known-issues section lists only the domain trust relationship problem and the USB Audio Class 1.0 Code 10 problem, and the Windows 11 24H2 release-health page carried no game-crash entry as of 26 September 2026. Two tech publications reported on 23 September that there was no Microsoft acknowledgement and no fix. Expect that to change: this is not the first Windows update this year to be linked to game crashes.
Affects KB5124010, Windows 11 24H2 26100.9550, Windows 11 25H2 26200.9550 · Status: open
Team17 acknowledged the WARDOGS crashes and, as reported on 23 September 2026, said there was no immediate remedy beyond uninstalling the update. No equivalent statement from EA about Battlefield 6 had been reported at that point.
Affects WARDOGS, Battlefield 6 · Status: workaround only
If none of this worked
The anti-cheat connection is a hypothesis built on what the affected games have in common, not a confirmed mechanism, so treat a non-matching case as a different problem rather than forcing the fit. If your crash arrives minutes into play rather than seconds after launch, if it takes the whole PC down rather than just the game, or if games without anti-cheat crash too, this is not it - look at GPU drivers, memory, or thermals instead. Last month's game crashes on KB5121003 looked superficially identical but traced to inpoutx64 drivers shipped with RGB peripherals, which is a reminder that "crashes after a Windows update" has had more than one cause this year. If you removed KB5124010 and the crashes continue, put the update back and keep looking.
Common questions
- Will uninstalling KB5124010 leave my PC unpatched?
- No. KB5124010 is a non-security preview update. September's security content shipped in KB5124008 on 8 September and the out-of-band KB5129195 on 14 September, and those stay in place. This is the key difference from the September security update, which you should not remove to chase a game crash.
- Is this confirmed to be an anti-cheat problem?
- No. Every game reported so far uses anti-cheat, and EA's Javelin is the suspected point of conflict, but the reporting is explicit that the cause has not been confirmed. What is well established is the correlation with this one update and that removing it is reported to work.
- Will the update come back on its own?
- On a normal PC it should not: Microsoft documents KB5124010 as delivered through optional updates or the Microsoft Update Catalog, so it installs only when you choose it. There is one exception - PCs enrolled in the Windows Insider program are reported to keep reinstalling it until they unenroll. Either way its contents reach everyone in October's cumulative update, so this is a reprieve rather than a permanent escape.
- Should I just skip Windows updates from now on?
- No - skip this optional preview, not your monthly security updates. Preview updates exist so that changes get a month of wider testing before they reach everyone, and declining them is the supported way to stay on well-tested builds without falling behind on security.
Did this fix work?
If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.
Report a problem with this pageRelated problems
- Games crash with EXCEPTION_ACCESS_VIOLATION after Windows 11 KB5121003
- Game Crashes When You Alt-Tab on Windows 11
- Windows Update Stuck Downloading or Failing to Install
- The Witcher 3 Remastered: Low FPS and Stuttering on PC
- Does FSR 4 work on Radeon RX 7000 cards?
- Steam shows one Xbox controller as two, and every input registers twice
Sources
Microsoft · Release notes · checked Sep 26, 2026
- KB5124010 was released on 22 September 2026 as OS Builds 26100.9550 (Windows 11 24H2) and 26200.9550 (Windows 11 25H2).
- Microsoft describes KB5124010 as a non-security preview update, obtained through optional updates in Windows Update or from the Microsoft Update Catalog.
- The known-issues section of KB5124010 lists only the domain trust relationship issue and the USB Audio Class 1.0 Code 10 issue; no game crash or anti-cheat issue is listed.
Microsoft · Support page · checked Sep 26, 2026
- As of 26 September 2026 Microsoft's Windows 11 24H2 known-issues list does not contain any entry about games crashing after KB5124010.
- September's security update was KB5124008, released 8 September 2026, and the out-of-band update KB5129195 followed on 14 September 2026 - both separate packages from the KB5124010 preview update.
Microsoft · Support page · checked Sep 26, 2026
- Microsoft documents removing an update via Start > Settings > Windows Update > Update history > Uninstall updates, then selecting the update and choosing Uninstall.
- Microsoft states that some updates cannot be uninstalled, and that you should understand the risks before removing security updates.
- Microsoft documents a Windows Recovery Environment route - Troubleshoot > Advanced options > Uninstall Updates - for machines that will not boot normally.
- Latest Windows 11 update is crashing Battlefield 6, Wardogs, and other Javelin-protected gamesReputable
TechSpot · News · checked Sep 26, 2026
- Reported on 23 September 2026 that Battlefield 6 crashes to desktop within seconds of launch after KB5124010, with Wardogs and some Battlefield 2042 reports alongside it.
- The suspected common factor is a clash with EA's Javelin anti-cheat, which covers Battlefield and other EA titles.
- A Team17 representative acknowledged the Wardogs crashes and said there is no immediate remedy beyond uninstalling the update.
- Wardogs players reported a WD-L020 error code accompanying the failure.
TweakTown · News · checked Sep 26, 2026
- Multiple Reddit and Steam user reports describe Battlefield 6, WARDOGS and other anti-cheat titles crashing after KB5124010, with some reports naming Battlefield 2042 and Fallout New Vegas.
- There is still no full confirmation that anti-cheat is the cause; the common factor is only that the affected games carry some form of anti-cheat.
- There is no reported Microsoft acknowledgement of the KB5124010 game crashes and no released fix.
- Uninstalling KB5124010 reportedly stopped the crashes for several affected players.
The FPS Review · News · checked Sep 26, 2026
- Reported on 25 September 2026 that Battlefield 6 and Wardogs crash to desktop about 20 to 30 seconds after launch with no error message.
- PCs enrolled in the Windows Insider program may keep reinstalling KB5124010 until they unenroll, so the update can return after removal.
- Both affected games use kernel-level anti-cheat, which is suspected as the point of conflict, but nobody has confirmed the mechanism.
- The changes contained in KB5124010 will arrive in October's cumulative update regardless.
- (WD-L020) KB5124010 ERROR FIX :: WARDOGS DiscussionCommunity report
Steam Community · Forum · checked Sep 26, 2026
- WARDOGS players report a WD-L020 launch error and attribute it to the Windows update KB5124010 dated 09/22/2026.
- The procedure players report as working is Windows Update > Update history > Uninstall updates, removing the 09/22/2026 KB5124010 entry, then restarting.