Did Windows update KB5124010 crash Battlefield 6?

It is the most likely cause of the crash that started in late September. KB5124010, the optional September 22 preview update for Windows 11, made some games and apps crash or fail to launch, and Microsoft confirmed in early October that the cause was Windows' built-in Dolby Digital (AC-3) audio decoding. Microsoft did not name specific games, and EA has not confirmed the mechanism, but Battlefield 6 players reported the crash stopping when the update was removed.

Is the KB5124010 game crash fixed?

Yes. Microsoft says the October 13, 2026 cumulative update, KB5127648, fixes it. Run winver: build 26100.9711, 26200.9711 or 26300.9711, or anything higher, means you have the fix. WARDOGS also fixed its WD-L020 launch error on the game side in update 0.1.2 on September 30.

What was the WARDOGS WD-L020 error?

A launch failure that Team17 linked to KB5124010 in a pinned Steam notice on September 23. WARDOGS update 0.1.2, released September 30, lists a fix for the Windows 11 WD-L020 crash, so you no longer need to remove the Windows update to play.

Should I still uninstall KB5124010?

No. Install the October update, KB5127648, or anything newer, instead. It contains everything from KB5124010 plus the fix. Uninstalling an old preview today just puts you behind on security fixes. If a game still crashes on build .9711 or later, the cause is something else.

Was it a graphics driver, anti-cheat or Secure Boot problem?

No. Microsoft's confirmed cause is the audio decoding component in Windows. Rolling back your graphics driver, reinstalling the anti-cheat or changing Secure Boot settings would not have touched it, which is why the usual crash checklist did not help.

KB5124010 Game Crashes: Fixed in KB5127648

Some links in this guide are affiliate links - we may earn a commission at no extra cost to you.

Update, October 27: this one is fixed. Microsoft confirmed the bug in early October and fixed it in the October 13 cumulative update, KB5127648. The cause it named is audio, not anti-cheat: games and apps that use Windows' built-in Dolby Digital (AC-3) decoding could "fail to launch, or close without warning." Microsoft did not name Battlefield 6 or WARDOGS, so the link to those two games is consistent with everything reported, not confirmed by Microsoft. WARDOGS shipped its own fix for WD-L020 in update 0.1.2 on September 30. If you are on build .9711 or later, you have the fix, and you do not need to remove anything. Details below; the original September 28 write-up follows, corrected where Microsoft's explanation replaced our guess.

What Microsoft confirmed

In the first days of October Microsoft added a known issue to its release health dashboard, reported by Windows Latest on the 3rd and BleepingComputer on the 5th. After KB5124010, apps that use Windows' built-in AC-3 decoder, the Dolby Digital audio format, could crash. In Microsoft's words, "In some cases the application can fail to launch, or close without warning," and the affected software "can include games, media players, and certain productivity applications." It applies to Windows 11 24H2, 25H2 and 26H2.

On October 19 BleepingComputer reported that the dashboard now lists the issue as fixed by KB5127648, the October 13 Patch Tuesday update. That update also carries everything that was in KB5124010, so you lose nothing by moving forward.

Check that you have the fix

Press Win+R, type winver, and read the build number.

26100.9711, 26200.9711 or 26300.9711, or higher: you have KB5127648 or newer, and the fix.
26100.9550 or 26200.9550: you are on KB5124010 without the fix. Go to Settings, Windows Update, and install what is waiting.
Lower than .9550: you never had the bad update. If a game crashes, it is something else.

If you uninstalled KB5124010 in September and paused updates, unpause them now. The pause was only ever meant to bridge you to this fix.

One thing to know if you are on Windows 11 24H2 Home or Pro: the October update was the last one those editions get. Microsoft ended 24H2 Home and Pro servicing on October 13, 2026, and those PCs are being moved to 25H2. If your PC shows a 26100 build, expect that upgrade.

If a game still crashes on .9711

Then KB5124010 is no longer the explanation, and the normal checklist applies again: update the game, verify its files, update the graphics driver, and close overlays. A few readers on BleepingComputer report crashes continuing after KB5127648 and clearing when they removed it. That is a handful of unverified comments, not a pattern, and removing a security update is a bad trade on a hunch. Check your Reliability Monitor for the faulting module first. If it names an audio component, report it to Microsoft through the Feedback Hub.

WARDOGS players: update 0.1.2 lists "Windows 11 'WD-L020' Crash Error Fix," and later patches have shipped since. If you still see WD-L020 on a current build, repair the game files through Steam before touching Windows.

The original September 28 write-up follows, with the build checks and timeline as they stood then.

On September 22 Microsoft shipped KB5124010, the optional non-security preview update for Windows 11 24H2 and 25H2. It takes the OS to build 26100.9550 or 26200.9550 depending on which version you are on, and the release notes list 46 changes: File Explorer previews, Emoji 17.0, a remappable Copilot key, Bluetooth fixes, a File History repair. Nothing about games.

Within a day the Battlefield 6 subreddit and the Steam forum had threads describing the same thing: the game launches, runs for 15 to 30 seconds, and closes to the desktop with no error box. WARDOGS players got a more useful symptom, a launch failure with the code WD-L020. On September 23 Team17 pinned a notice on the WARDOGS forum saying their team had identified a compatibility problem with KB5124010 and giving the uninstall steps as the workaround. An EA community manager in the Battlefield thread said it had been passed to the team. TechSpot, Neowin and The FPS Review all reached the same conclusion from the same reports.

As of September 28 Microsoft's known-issues list for the update mentioned a Credential Guard domain-trust problem and some USB audio devices failing to start, but no games. The game crash was added in early October, as above.

How you could have got it

KB5124010 was optional. On a normal PC it only landed if you went into Settings, Windows Update, Optional updates and clicked Download and install. There were two ways to get it without doing that. The toggle labelled "Get the latest updates as soon as they're available" installs preview updates automatically, and a lot of people turned it on once and forgot. And PCs enrolled in the Windows Insider program on the Release Preview channel got it earlier in September.

How to remove an update, if you ever need to

You should not need this for KB5124010 any more, but the steps are the same for any update that breaks something:

Settings, then Windows Update, then Update history.
Scroll to the bottom and open Uninstall updates.
Find the update and choose Uninstall.
Restart when asked. The rollback takes a few minutes.

From a command prompt run as administrator, the equivalent is wusa /uninstall /kb: followed by the number. Then pause updates for a week or two so it does not come straight back. Pause only buys up to 35 days, which is why the real answer is always the fixed update, not a permanent block.

Why the usual crash checklist did nothing

In September nobody had published the mechanism, and the first version of this post guessed at a conflict with the games' kernel-level anti-cheat, because Battlefield 6 (EA Javelin) and WARDOGS (Elytra) both failed after the same update. Microsoft's confirmation points at audio instead: the crash was in the Windows component that decodes Dolby Digital. That fits a crash that hit at launch or in the first seconds of play, when a game starts its audio, though Microsoft has not described the crash in that much detail.

Either way, the practical advice held. Verifying files, reinstalling the anti-cheat, clearing shader caches, disabling overlays and updating the GPU driver did not touch the thing that changed. And it was not your hardware: the reports came from Nvidia and AMD cards, Intel and AMD processors, prebuilts and home builds.

The Secure Boot red herring

Both games attract "turn on Secure Boot" replies to every crash thread, for a reason. Battlefield 6 does require Secure Boot and TPM 2.0 by design, and our WARDOGS requirements post covers why a number of WARDOGS players found the same setting cleared a launch crash even though Bulkhead does not officially require it.

Neither applied here. If Secure Boot were the problem the game would never have launched, and these were machines that played fine on Sunday and broke on Tuesday. Do not go into the BIOS chasing a Windows update.

The short version

KB5124010 was the optional September 22 preview update for Windows 11 24H2 and 25H2, builds 26100.9550 and 26200.9550.
Battlefield 6 closed 15 to 30 seconds after launch with no error. WARDOGS failed with WD-L020. Team17 confirmed the link on September 23.
Microsoft confirmed in early October that the update crashed games and apps using Windows' built-in Dolby Digital (AC-3) decoding. It did not name specific games.
Fixed: the October 13 update, KB5127648 (builds .9711), fixes it. WARDOGS 0.1.2 (September 30) fixed WD-L020 on the game side.
Check winver. On .9711 or later you are done; do not uninstall anything. 24H2 Home and Pro got their last update on October 13.

Battlefield 6 and WARDOGS Crashed After Windows Update KB5124010. Microsoft Fixed It on October 13.