On October 2, 2026, Microsoft confirmed on its Windows release health dashboard that Windows updates released September 22, 2026 (KB5124010) and later can make some apps and games close unexpectedly on Windows 11, version 26H2, and on versions 24H2 and 25H2. The crash hits applications that require AC-3 (Dolby Digital) audio decoding and still rely on Windows’ built-in decoder. Windows Latest reported the confirmation on October 3.
The short answer to “Is 26H2 safe to install?”: for most people, yes. This is a narrow codec bug, not a broad Windows failure. Skipping 26H2 also won’t protect you, because 24H2 and 25H2 have the same problem.
What Happened
Here’s the timeline, using only official and reported sources:
- August 27, 2026: Microsoft released Windows 11, version 26H2 to the Release Preview Channel (Windows Insider Blog).
- September 22, 2026: Microsoft released KB5124010, an optional non-security preview update for Windows 11 26H2, 25H2, and 24H2 (OS Builds 26300.9550, 26200.9550, and 26100.9550) (Microsoft Support, KB5124010).
- September 29, 2026: Version 26H2 reached general availability, with a phased rollout starting with devices set to get the latest updates as soon as they’re available (Microsoft release health).
- October 2, 2026: Microsoft opened the known issue “Applications which require AC-3 audio decoding might close unexpectedly” with the status Confirmed. It says it is working on a resolution for a future Windows update.
- October 3, 2026: Windows Latest reported Microsoft’s confirmation (Windows Latest).
What AC-3 is, in plain English
AC-3 is the technical name for Dolby Digital. It’s the surround-sound audio format used on DVDs, many Blu-ray discs, TV broadcasts, and some game cutscenes and video files. When an app plays an AC-3 track, something has to decode it into sound your speakers can play. Some apps include their own decoder. Others ask Windows to decode it. The bug affects only the second group.
There’s a wrinkle here. Microsoft’s own documentation says Windows 11 24H2 and later no longer include the AC-3 codec by default. Some PCs still have it because the manufacturer preinstalled it or because the PC got it through an in-place upgrade (Microsoft Support, Troubleshoot Windows Media Player errors). That means two PCs on the same build can behave differently with the same game.
Symptoms Microsoft describes
Microsoft says the symptoms depend on what the affected app is doing:
- In some cases, the app or game fails to launch or closes without warning.
- In other cases, the app works normally until you use certain features, such as playing music, and then closes.
Microsoft says affected applications vary and can include games, media players, and certain productivity applications. It hasn’t published a fuller list of trigger actions.
What is NOT confirmed yet
Be skeptical of anyone who claims to know more than this. As of October 4, 2026, Microsoft’s entry does not provide:
- A list of affected games or apps. Microsoft has not published one.
- A specific error code or error message. None appears in the sources.
- A fix date or fixed build number. Microsoft says only “a future Windows update.”
- A workaround. Microsoft’s AC-3 entry lists none, only its plan to fix the issue in a future update.
- A Known Issue Rollback (KIR) for this bug. Microsoft’s AC-3 entry doesn’t list one. The same release health pages do list a KB5124010 KIR, but it belongs to a separate issue (black screens or desktop loading problems after sign-in, mostly on Azure Virtual Desktop), not to the AC-3 crash.
Who This Affects
You’re potentially affected only if all three of these are true:
- Your PC runs Windows 11, version 24H2, 25H2, or 26H2. Check under Settings > System > About.
- You’ve installed KB5124010 or any Windows update released after September 22, 2026. Check under Settings > Windows Update > Update history.
- You use a game or app that asks Windows to decode AC-3 audio.
KB5124010 is an optional preview, so not every PC has it yet. Microsoft’s entry covers updates released September 22 “and later,” though, so skipping the optional preview won’t keep you clear once later cumulative updates install.
Microsoft lists only Windows 11, versions 24H2, 25H2, and 26H2 as affected. Windows 10 and Windows Server aren’t on the list.
Microsoft says many modern applications don’t use Windows for this kind of decoding and won’t encounter the issue. The component involved is most commonly used by legacy applications. If your PC is mostly a work machine running Office and a browser, this probably isn’t your problem.
The people most likely to run into it:
- PC gamers, especially those playing older titles or games with Dolby Digital cutscene or video audio.
- Home theater PC owners who route movie audio to an AV receiver or a Dolby Digital soundbar.
- Anyone using older media players that rely on the Windows codec instead of a bundled one.
How It Stacks Up
Two comparisons matter most for your decision. The first is whether staying on an older version helps. The second is whether this is the same as other audio bugs you may have read about.
| Scenario | Affected by the AC-3 crash? | Source |
|---|---|---|
| Windows 11 26H2 with KB5124010 (Build 26300.9550) or later | Yes, confirmed | Microsoft release health, 26H2 |
| Windows 11 24H2 / 25H2 with KB5124010 (Builds 26100.9550 / 26200.9550) or later | Yes, confirmed | Microsoft release health, 24H2; KB5124010 |
| Delaying 26H2 but staying current on 24H2/25H2 | Not a workaround, since 24H2 and 25H2 are affected too | Microsoft release health, 26H2 |
| USB Audio Class 1.0 failures (Code 10, no output, unresponsive volume) | Separate known issue, not this bug | Microsoft release health, 26H2 |
Two takeaways stand out.
First, this is not a 26H2 problem. The 26H2 label is in the headlines because it’s the newest release. The trigger is the Windows updates released September 22, 2026 (KB5124010) and later, which 24H2, 25H2, and 26H2 all receive. Pausing the 26H2 feature update while taking regular 24H2/25H2 updates gives you no protection.
Second, don’t lump this in with other audio bugs. If your USB headset shows a Code 10 error in Device Manager, or you simply have no sound, that’s a different problem with a different cause. The AC-3 bug crashes apps. It doesn’t silence your whole PC. Mixing the two up leads to the wrong troubleshooting path.
The Reaction
We couldn’t find a Reddit, Hacker News, or social media thread we could verify and link, so we aren’t characterizing community sentiment here.
What we can verify is that several other problems people may blame on recent updates are separate entries on Microsoft’s release health dashboard, not part of this bug: black screens or desktop loading problems after sign-in (mostly on Azure Virtual Desktop), domain-joined devices losing their trust relationship with the domain, and USB Audio Class 1.0 devices showing Code 10 or producing no sound. If your symptom matches one of those, it’s a different issue with its own guidance.
Treat claims about specific files or named games as unconfirmed until Microsoft adds them to its entry.
What to Do Next
If nothing is crashing, do nothing. Microsoft hasn’t recommended any preventive action, and you don’t need to uninstall updates you already have. KB5124010 itself is an optional preview, so there’s no need to go looking for it either.
If a game or app is crashing right now, your one practical next step is to confirm whether you match the known issue before you change anything:
- Open Settings > System > About and note your Windows 11 version (24H2, 25H2, or 26H2).
- Open Settings > Windows Update > Update history and look for KB5124010 or any update installed after September 22, 2026, under Quality Updates.
- Note when the app crashes. Does it fail to launch, or does it close only when it starts playing audio, such as music?
If all three line up, you’re very likely hitting this bug. It’s not a problem unique to your PC. Until the fix ships, you could avoid the in-app audio action that makes the app close. That’s our suggestion, not a Microsoft workaround, and because Microsoft hasn’t published a full list of triggers, it isn’t guaranteed to help.
General audio troubleshooting (not a confirmed fix)
Microsoft publishes standard audio guidance. You can work through it to rule out other problems, but none of these steps is confirmed to fix the AC-3 crash:
- Check output devices under Settings > System > Sound.
- Turn off audio enhancements for your output device in the same Sound settings area.
- Update your audio driver through Device Manager or your PC maker’s support site.
- Run the audio troubleshooter in the Get Help app.
Microsoft’s full walkthroughs are on its Fix sound or audio problems in Windows page and its Fix audio stops working after a Windows update page.
About rolling back
Windows 11 lets you remove some updates from Settings > Windows Update > Update history > Uninstall updates. However, Microsoft hasn’t published rollback guidance for this specific bug. Some cumulative updates can’t be removed this way either.
Removing a cumulative update also strips out that month’s security fixes. If you decide to try it on a machine that depends on one critical game or app, take a backup to an external SSD first. Pause updates afterward so the update doesn’t quietly reinstall.
Our Take
Verdict: Install as normal. Work around the problem only if you’re actually affected. Worry level: low for most people, moderate for gamers and home theater PC users.
The evidence points to a narrow bug. It affects one codec path, mostly in legacy apps that rely on an AC-3 decoder Windows 11 24H2 and later no longer include by default (though many PCs still have one). Holding back 26H2 does nothing, because 24H2 and 25H2 are affected the same way. Blanket update avoidance would leave you without security patches and still exposed to the bug.
The real annoyance is the lack of detail. Microsoft hasn’t given an app list, an error code, a fix date, or a workaround. That leaves the family fix-it person guessing.
If you manage PCs for others, the practical rule is simple. A game or media app that crashes on audio actions after September 22, 2026 is probably this bug, so don’t spend hours reinstalling drivers. If crashes happen across many unrelated apps, or Windows itself freezes or blue-screens, suspect something else. That pattern points to a failing driver, bad hardware, or malware. Run a malware scan and check Reliability Monitor before you blame KB5124010.
Wrapping Up
If your PC is fine, keep updating. If something did break, check your version and update history to confirm the match, then wait for Microsoft’s fix rather than ripping out security updates. We’ll update this story when Microsoft publishes a fixed build or a Known Issue Rollback.
| Step | Action | Applies To |
|---|---|---|
| 1 | Check Settings > System > About for 24H2/25H2/26H2 | Anyone with a crashing app |
| 2 | Check Update history for KB5124010 or any update installed after Sept 22, 2026 | Anyone with a crashing app |
| 3 | Note whether crashes happen on launch or when audio plays | Gamers, media/HTPC users |
| 4 | Keep installing updates and watch for Microsoft’s fix | Everyone |