Battlefield 6 and other anti-cheat games crash seconds after launch on Windows 11 KB5124010
Microsoft has still not acknowledged this crash pattern, and the anti-cheat link remains a hypothesis - re-checked on 12 November 2026 against the release-health pages and the notes for November's update. What changed on 13 October 2026 is the cost of the workaround: October's security update (KB5127648) is cumulative and lists KB5124010 among the updates it includes, and November's (KB5132061) builds on it, so removing KB5124010 on its own no longer keeps those changes off a machine that has taken either update. Test the game on your current build, and check whether the game has patched, before uninstalling anything.
Start here
Two things made this worth checking when the reports first appeared: the update involved was optional, so many people did not have it, and the timing was distinctive - seconds after launch, not minutes into a match. The first of those no longer holds. October's monthly security update shipped on 13 October 2026 and lists KB5124010 among the previously released updates it includes, so the same changes now arrive on machines that never chose the preview. The timing signature is still the useful part, and it is what tells this apart from the AC-3 audio decoder crash that Microsoft did acknowledge and has now fixed.
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.
Test on your current build before removing anything · Remove KB5124010
Fixes
Test on your current build before removing anything
about 10 minKB5127648 is cumulative and lists KB5124010 among the updates it includes, and November's KB5132061 builds on it, so the uninstall route changed on 13 October 2026. Find out what your current build actually does first.
Applies to: Windows 11 24H2, 25H2 and 26H2 on the October or November 2026 updates
- Check your build. Press Windows+R, run winver and read the number. A .9711 build (26100.9711 / 26200.9711 / 26300.9711) is October's security update; a .9974 build (26100.9974 / 26200.9974 / 26300.9974) is November's, KB5132061. Either way the KB5124010 changes are already included.
winver - If you are on a .9711 or .9974 build, launch the game and test it. Every report behind this page predates those builds, so nobody has yet established whether the crash survives October's or November's update. What you find is genuinely new information.
- If it still crashes, removing KB5124010 on its own is unlikely to help, because its changes are included in the October and November security updates. Do not expect the September workaround to apply unchanged.
- If it does not crash, stop here. Keep the machine on the current update rather than rolling anything back.
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.
Source: Microsoft, The FPS Review
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.
- Team17's stated position on 23 September 2026 was that there was no immediate remedy other than removing the update. A search of game and publisher announcements on 14 October 2026 turned up no patch for this on either Battlefield 6 or WARDOGS, so check the game's own channels for anything newer than that.
Source: The FPS Review
Remove KB5124010
Check before applyingabout 15 minPlayers across two separate games reported this restored normal play in late September. It now only applies to a machine that has not taken October's security update.
Applies to: Only machines still on build 26100.9550 / 26200.9550 that have not installed KB5127648
Before you do this
Microsoft's guidance is not to remove installed updates casually, and some updates cannot be removed at all. This matters more than it did in September: KB5124010's changes are now included in the October 2026 security update KB5127648, so on an up-to-date machine there may be no separate KB5124010 entry to remove, and the equivalent action would be removing a security update - which does strip October's security fixes. Check the date and the KB number in the list before you confirm anything. 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. The changes in KB5124010 arrived for everyone in October's cumulative update on 13 October 2026, so uninstalling the September preview is no longer a durable way to avoid them. If the conflict is still unresolved on the October build, the realistic options are a game-side or anti-cheat-side patch, not staying on an older Windows build.
Reported to work by 3 users; not confirmed by the vendor.
Source: Microsoft, Steam Community, The FPS Review
Known issues
Microsoft has still not acknowledged this crash pattern. Re-checked 12 November 2026: the 24H2, 25H2 and 26H2 release-health pages carry no entry about games or anti-cheat crashing, and the known-issues list for November's update, KB5132061, names only an install failure with error codes 0x80070306, 0x800f0989 and 0x800f0993. The only open entry across those pages is an unrelated SQL Server linked-server issue.
Affects KB5124010, Windows 11 24H2 26100.9550, Windows 11 25H2 26200.9550, Windows 11 26H2 26300.9550, KB5132061 (10 November 2026) - still no entry · Status: open
Team17 acknowledged the WARDOGS crashes and, as reported on 23 September 2026, said there was no immediate remedy beyond uninstalling the update, describing removal as optional and at your own risk. No equivalent statement from EA about Battlefield 6 has been reported, and no game-side patch for either title had surfaced by 14 October 2026.
Affects WARDOGS, Battlefield 6 · Status: workaround only
Do not read October’s mouse-stutter fix as a fix for this. KB5127648 lists, under Gaming, a fix for "an issue that could cause mouse input to stutter in some games", and some coverage has linked the two. Nothing in the update’s notes mentions crashing, game launches or anti-cheat, and input stutter is a different symptom from a process exiting after twenty seconds. Treat the connection as speculation.
Affects KB5127648 (13 October 2026) · Status: unknown
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. There is also a second, confirmed KB5124010 crash to rule out, which Microsoft fixed on 13 October 2026. Open Event Viewer (Win+R, eventvwr), go to Windows Logs > Application and read the faulting module. If it names msmpeg2ac3dec.dll, usually with code 0xc0000602, that is the AC-3 decoder fault rather than the pattern on this page, and installing the October 2026 update fixes it. It also hits right after a game's main menu or whenever audio starts, not 20 to 30 seconds in.
Common questions
- Will uninstalling KB5124010 leave my PC unpatched?
- The answer changed on 13 October 2026. KB5124010 was an optional non-security preview, so removing it in September cost nothing in security terms - September's fixes shipped separately in KB5124008 and the out-of-band KB5129195. But the October security update KB5127648 lists KB5124010 among the updates it includes. On a machine that has installed October's update there may be no separate KB5124010 entry left to remove, and removing the October update instead would strip that month's security fixes. Read the KB number and date in Update history before uninstalling anything.
- 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 the October 2026 update fix these crashes?
- Nobody has established that either way, and we will not guess. Microsoft never acknowledged this crash pattern, so there is no fix entry to point to, and KB5127648's notes do not mention games or anti-cheat. Because that update includes KB5124010's changes rather than reverting them, there is no particular reason to expect the conflict to have gone away - but the reports behind this page all predate it, so the honest position is unknown. If you are on a .9711 build, test the game: that is currently new information.
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
- Oblivion, Fallout: New Vegas and other apps crash after Windows 11 KB5124010 (msmpeg2ac3dec.dll)
- 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
- PowerToys Mouse Without Borders: "Pairing could not be loaded or updated" after the 0.102 update
- NVIDIA driver writes to the SSD constantly (NVDisplay.Container.exe, nvlog.nvlgstg)
Sources
Microsoft · Support page · checked Nov 12, 2026
- States "This update includes improvements from the following previously released updates:" and lists KB5124010 of 22 September 2026 among them
- Describes itself as providing security improvements, so the changes KB5124010 introduced now arrive via a security update
- Its known issues are a Remote Desktop 0xC000000D failure and USB Audio Class 1.0 devices; it lists no known issue about games crashing or anti-cheat
- Raises Windows 11 to builds 26300.9711 (26H2), 26200.9711 (25H2) and 26100.9711 (24H2)
Microsoft · Release notes · checked Nov 12, 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.
- The page now states the AC-3 issue is resolved in Windows updates released on and after October 13, 2026 such as KB5127648
Microsoft · Support page · checked Nov 12, 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.
- Re-checked 14 October 2026: no known-issue entry about games, anti-cheat or applications crashing on launch
- As of 13 October 2026 Windows 11 version 24H2 Home and Pro editions have reached end of updates; Enterprise and Education remain supported until 12 October 2027
Microsoft · Support page · checked Oct 14, 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.
Microsoft · Support page · checked Nov 12, 2026
- KB5132061, released 10 November 2026, is the current cumulative security update, carrying OS builds 26300.9974 (26H2), 26200.9974 (25H2) and 26100.9974 (24H2)
- KB5132061 applies to Windows 11 26H2 and 25H2 in all editions but to version 24H2 in Enterprise and Education editions only
- Re-read 12 November 2026: the update's Known issues section names only a November install failure with error codes 0x80070306, 0x800f0989 and 0x800f0993, for which Microsoft says an automatic repair reaches affected devices within 24 to 48 hours from 11 November 2026 - it says nothing about game crashes, anti-cheat, Battlefield 6 or WARDOGS
- KB5132061 lists no further mouse input stutter fix, so the fix noted in KB5127648 remains the one of record
The FPS Review · News · checked Nov 12, 2026
- Reported 25 September 2026: Battlefield 6 players describe the game dropping to desktop about 20 to 30 seconds after launch with no error message, and WARDOGS players get a WD-L020 launch error
- Names Windows 11 optional preview update KB5124010, released 22 September 2026 for 24H2 and 25H2, builds 26100.9550 and 26200.9550, and notes its known-issues list does not mention games
- Names Javelin as the anti-cheat involved and notes both games use kernel-level anti-cheat, calling it the obvious suspect while stating the mechanism is unconfirmed
- Reports that Team17 acknowledged the WARDOGS issue on its Steam forums, tied it to KB5124010, called removal optional and said it was still investigating a fix; reports no Microsoft acknowledgement and names no EA statement
- Notes that Insider-enrolled PCs may keep reinstalling the update until they unenroll
- Re-read 28 October 2026: no update note has been added and the article still does not mention KB5127648 or any fix
- (WD-L020) KB5124010 ERROR FIX :: WARDOGS DiscussionCommunity report
Steam Community · Forum · checked Nov 12, 2026
- A WARDOGS thread opened 22 September 2026 titled "(WD-L020) KB5124010 ERROR FIX" gives uninstalling KB5124010 through Windows Update history as the fix, naming the 22 September 2026 update by number
- Re-read in a browser on 28 October 2026 and recounted: the thread has seven comments and is closed to nothing further. Three distinct people report the removal working - the author, one who wrote that uninstalling KB5124010 restored gameplay with no reinstalls needed, and one who wrote "can confirm this worked". A fourth comment is a thank-you that does not state an outcome, so it is not counted
- One commenter rolled back their NVIDIA driver as well; the thread author replied that this was unnecessary and that the Windows update alone broke the game
- One commenter asks what to do once the ten-day uninstall window for the update has passed; the author answers only that it should still work