Windows 11 AC-3 Audio Bug: Why Apps Are Closing After KB5124010

Microsoft has confirmed a new Windows 11 bug: after installing the September 22, 2026 update KB5124010 (OS Build 26200.9550) or any later cumulative update, some apps that rely on Windows' built-in AC-3 (Dolby Digital) audio decoding can close unexpectedly, fail to launch, or crash the moment they try to play that type of audio. Microsoft opened the issue on its official Windows 11 release-health page on October 2, 2026, marked it "Confirmed," and says it is working on a fix for a future update — there is no patch yet.

Here is what the bug actually does, which Windows 11 versions and builds are affected, the exact symptoms to watch for, what Microsoft has said, and what you can do about it right now.

What is the Windows 11 AC-3 audio bug?

According to Microsoft's Windows 11, version 25H2 release-health page, "following installation of Windows updates released September 22, 2026 (KB5124010), and later, some applications which require the decoding of AC-3 (Dolby Digital) audio might close unexpectedly."

AC-3, commonly known by its commercial name Dolby Digital, is a long-established audio compression format used in DVDs, some streaming content, and a lot of older PC games and media software. For decades, Windows has shipped a built-in decoder that lets apps play AC-3 audio without having to include their own decoding software. That built-in decoder is the component Microsoft says is now misbehaving.

Microsoft's own description of the behavior is deliberately broad, because the bug doesn't hit every app the same way. In its words: "Incidence of this issue depends on the activity that these applications perform. In some cases the application can fail to launch, or close without warning. In other cases the application will work normally until certain features are used, such as playing music."

Which Windows 11 updates and builds are affected?

The bug was introduced by KB5124010, an optional, non-security "preview" update that Microsoft released on September 22, 2026. Because it's cumulative, every Windows update released after that date carries the same underlying code and is also affected until Microsoft ships a fix.

KB5124010 shipped as three separate build numbers depending on which Windows 11 feature update you're running, which is why the bug reaches three different version numbers at once:

Microsoft's affected-platforms note for this issue lists "Client: Windows 11, version 26H2; Windows 11, version 25H2; Windows 11, version 24H2" and "Server: None" — so Windows Server builds are not affected, and older Windows 11 versions outside active support (such as 23H2) aren't listed either. If you're running the newer Windows 11 2026 Update (26H2) or still on version 25H2, you're in the affected population once you've installed KB5124010 or anything released after it.

Symptoms to watch for

Because the bug lives in an audio-decoding component rather than in any one app, the symptoms show up differently depending on what you're running and how it uses sound. Based on Microsoft's description, watch for:

• An app that fails to open at all, sometimes with no error message.
• An app that opens normally but crashes or closes without warning once you try to play music or other audio inside it.
• Older or "legacy" games, media players, or productivity software behaving fine until a specific audio feature is triggered.
• No sound, or a sudden app close, specifically tied to content encoded in AC-3 / Dolby Digital — not every audio format.

Microsoft is careful to note that this isn't a universal "Windows 11 has no sound" problem. It affects a specific decoding path, not the whole audio stack: "Please note that many modern applications do not use Windows for this type of encoding and therefore will not encounter this issue." Mainstream apps like your web browser, Spotify, or most current-generation games almost certainly ship their own audio decoders and are not expected to be affected.

Why is this happening?

Microsoft's explanation points squarely at older software rather than at any specific app title: "The code component involved in this issue is most commonly used in legacy applications that still rely on Windows built-in audio decoding. Many modern applications using this legacy codec frequently include their own audio decoding components."

In plain terms: Windows includes a built-in AC-3 decoder so that older apps don't have to build their own. KB5124010 appears to have changed something in that shared component. Apps that lean on Windows to do the AC-3 decoding for them — typically older games, legacy media players, and some productivity tools with built-in media playback — are exposed to the bug. Apps that handle their own AC-3 (or Dolby Digital) decoding internally are not.

What Microsoft has said

Microsoft's release-health entry lists the issue status as Confirmed, meaning the company has reproduced and verified the problem rather than just received unconfirmed reports. As of publication, Microsoft has not shipped a fix and has not published a workaround for affected users. The company's "next steps" note reads: "We are working on releasing a resolution for this issue in a future Windows update. We will provide an update when more information is available."

That is a notably thin response compared with some of Microsoft's other recent known issues — there's no Known Issue Rollback (KIR) group policy, no registry workaround, and no out-of-band patch offered for this one yet. The entry was opened October 2, 2026 at 15:06 PT and last updated the same day at 15:41 PT, so this is a very fresh disclosure; expect Microsoft to revise the entry as more details, or a fix, become available.

How to check if you have KB5124010 installed

Because the bug depends on whether KB5124010 (or a later cumulative update) is on your PC, it's worth checking your exact build before you start troubleshooting an app. Here's how:

• Open Settings > Windows Update > Update history and look for "2026-09 Cumulative Update Preview for Windows 11" with KB5124010 in the name, or any update dated after September 22, 2026.
• Alternatively, open Settings > System > About and check the "OS Build" number. If it reads 26300.9550 (version 26H2), 26200.9550 (version 25H2), or 26100.9550 (version 24H2) — or any higher build number — you have the update that introduces this issue.
• You can also run winver from the Start menu search box for a quick build-number popup without digging through Settings.

If your build number is lower than the ones listed above, you haven't installed KB5124010 yet and the AC-3 decoding issue described here should not apply to your device — though you'll eventually need a cumulative update that includes a fix once Microsoft ships one.

What affected users can do right now

Because there's no official fix or workaround yet, options are limited. If an app on your PC is closing unexpectedly or losing sound after a recent update, here's what's worth trying:

• Check if it's actually an AC-3/Dolby Digital issue. The symptom to look for is a crash or failure tied specifically to audio playback, in an older app — not a general system-wide sound failure.
• Look for an app update. If the affected program has its own audio engine or decoder (common in modern software), updating it may route around Windows' built-in decoder entirely. Check the app's own update mechanism or the developer's site.
• Avoid the specific trigger where possible. If a productivity or media app only crashes when a particular audio feature is used, you may be able to keep using the rest of the app normally until a fix ships.
• Report it through Feedback Hub. Adding your own report helps Microsoft gauge how widespread the issue is.
• Hold off on installing further preview updates if you can. If you haven't installed KB5124010 yet and don't need what it offers, you can choose not to install an optional, non-security preview update until Microsoft resolves this. Mandatory security updates will still need to be installed when they arrive.
• Otherwise, wait. For most home users, the realistic answer is that there's nothing to actively "fix" on your end yet — Microsoft has confirmed the bug and says a resolution is coming in a future update.

What else is in KB5124010?

KB5124010 is an optional, non-security preview update — the kind Microsoft uses to test fixes and features ahead of the next month's mandatory Patch Tuesday release. According to the official KB5124010 support article, it applies to Windows 11 versions 26H2, 25H2, and 24H2, and it was also notable for being the final preview update for Windows 11, version 24H2. Beyond the AC-3 regression, the update bundled a mix of smaller changes, including File Explorer preview-pane and thumbnail reliability improvements, Emoji 17.0 support, a new "Tips" widget, accessibility tweaks such as an "Open apps maximized" setting, Bluetooth stability improvements, additional touchpad gestures, and a fix for an issue where a device's built-in camera could stop working.

Is this the same as other recent Windows 11 audio problems?

No — and it's worth keeping them separate if you're troubleshooting. Microsoft's release-health page also lists a different, earlier issue: some USB Audio Class 1.0 devices failing to start or producing no sound (Code 10 errors, or multichannel modes not working) after the September 8, 2026 update, KB5124008. That USB audio problem is listed as "Mitigated," with an out-of-band update already resolving part of it. The AC-3 decoding bug covered in this article is a separate, newer issue tied to KB5124010 and is still "Confirmed" with no fix shipped. If your device makes sound fine everywhere except inside one specific older app, you're more likely looking at the AC-3 issue; if a USB headset or audio interface itself won't start at all, that's the separate USB audio bug.

What happens next

Microsoft has not given a timeline beyond "a future Windows update," so there's no confirmed date for a fix as of this writing. Expect one of two paths: either a fix lands in the next monthly cumulative update, or — if the problem turns out to be severe or widespread enough — Microsoft issues an out-of-band patch the way it did for September's USB audio and Remote Desktop issues. Until then, the official release-health entry is the best place to check for updates, since Microsoft edits that same page in place rather than publishing a new one each time the status changes. If you rely on an older game, media player, or productivity app that uses Dolby Digital audio, keep an eye on that entry, and check whether the app in question has shipped its own audio-decoding update in the meantime.

Written byFelix Moreau

Felix Moreau writes Pandromeda's software coverage and how-to guides. He covers Windows, macOS and Linux updates, the apps people rely on, emulators and developer tools, and turns official documentation into clear, numbered steps that work on the current version.

More from Felix MoreauAll Software & Guides coverage