KB5127648 Fixes Windows 11 AC-3 Dolby Audio Crashes in Games and Apps

BleepingComputer reported that Microsoft has fixed a known issue that caused games and Windows 11 apps using AC-3 (Dolby Digital) audio decoding to crash after installing the September 2026 preview update (KB5124010). Microsoft's own documentation backs this up: the release notes for KB5127648 list the item as an audio known issue marked "Fixed."

What broke, and who was affected​

The trouble started with KB5124010, the optional non-security preview update Microsoft released on September 22, 2026, for Windows 11 versions 24H2, 25H2 and 26H2. Microsoft's release health entry says that after installing KB5124010 or a later update, some applications that need AC-3 (Dolby Digital) audio decoding could close unexpectedly.

Microsoft says the symptoms depended on what the app was doing:

• Some apps failed to launch or closed without warning.
• Other apps ran normally until they used a feature such as music playback, then crashed.
• The affected software included games, media players and certain productivity applications.

Not every app was at risk. Microsoft said the KB5124010 known issue primarily affects legacy applications that rely on Windows built-in audio decoding. In Microsoft's words, most modern applications are not affected. BleepingComputer added that Microsoft noted many modern apps that don't use Windows' built-in audio decoding for this type of encoding aren't affected, and that modern apps that use the legacy AC-3 codec often include their own audio decoding components.

That explains the pattern. A modern streaming app or a game that ships its own audio decoder never calls the Windows AC-3 decoder, so it never hits the bug. An older title or a classic media player that leans on the codec built into Windows could fall over as soon as it tried to decode a Dolby Digital stream.

Microsoft lists the affected platforms as Windows 11 24H2, 25H2 and 26H2 on the client side. No server versions are listed. Microsoft has not named specific games or apps, and it hasn't published a root cause beyond the AC-3 decoding path. Any list of "affected titles" you see elsewhere is not from Microsoft.

Section summary: The bug hit apps that rely on the AC-3 decoder built into Windows, mostly legacy software, on Windows 11 24H2 through 26H2 after the September 22 preview update.

Why fewer people were hit than the headline suggests​

KB5124010 was a preview update. According to BleepingComputer's reporting, KB5124010 is optional and normally requires users to select "Download and install." It installs automatically on devices where the "Get the latest updates as soon as they're available" setting is enabled. Microsoft's pages don't confirm that point about the settings toggle, so treat it as BleepingComputer's reporting.

So this wasn't a mass breakage in the same league as a bad Patch Tuesday. It mostly reached people who opt into early non-security updates. Many enthusiasts turn that toggle on and forget about it, though, and those are the same people likely to keep a shelf of older games around.

The timeline​

The issue was open for less than a week on the dashboard. It was live on preview-channel PCs for about three weeks before that.

How to get the fix​

Microsoft's resolution is simple. The problem is resolved by updates released on October 13, 2026 (KB5127648) and later. The company's advice: "We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one."

KB5127648 takes Windows 11 to OS build 26100.9711 (24H2), 26200.9711 (25H2) or 26300.9711 (26H2). It's cumulative: Microsoft's notes say it includes the improvements from KB5124008, the out-of-band KB5129195 and KB5124010. There's no separate AC-3 hotfix to look for.

For home users​

1. Open Settings and go to Windows Update.
2. If updates are paused, resume them.
3. Select Check for updates and install KB5127648 or anything newer, then restart.
4. To confirm, go to Settings > Windows Update > Update history and look for KB5127648. You can also check that your build ends in .9711 or higher.
5. Open the app that was crashing and repeat whatever used to crash it, such as starting playback.

You don't need to remove the preview update first. WindowsDigitals points out that you don't need to uninstall KB5124010 first, since KB5127648 is a cumulative update that already includes it. If Windows Update still offers KB5124010 as an optional download, it isn't installed, so skip it and take the October update.

For IT administrators​

Microsoft lists KB5127648 on Windows Update, Windows Update for Business (installed according to your configured policies), the Microsoft Update Catalog and WSUS. WSUS syncs it under Product "Windows 11" and Classification "Security Updates."

If you install from the Catalog, note that the packages include a required checkpoint cumulative update (KB5043080) that has to be installed before the target update. You can double-click the MSU files in order, or point DISM at a folder containing all of them and let it handle the checkpoint automatically.

Section summary: Install KB5127648 or later, restart, and check that the build number ends in .9711 or higher. That's the whole fix.

Troubleshooting: when the crash isn't this bug​

Don't blame AC-3 for every crash since September. Microsoft's description limits the known issue to apps that need AC-3 decoding. A useful test: the crash happens at launch or exactly when Dolby Digital audio starts playing. If your app dies at random on a device with no Dolby content involved, keep looking.

If KB5127648 is installed and an old player still crashes on Dolby tracks, Free-Codecs suggests the app is probably leaning on a Windows part it should not need. A player that ships its own decoder, such as VLC, is a practical workaround. That's a third-party suggestion, not Microsoft guidance.

Before the fix arrived, some guides recommended uninstalling KB5124010 or installing alternative decoders such as LAV Filters. Now that the official fix is out, WinTips.org advises users to install the latest Windows update available for your device, restart your computer, and test the affected application before trying the workarounds below. Rolling back a cumulative update now would also remove October's security fixes, which is a bad trade.

The fine print in KB5127648​

The October update fixes a lot besides AC-3. Microsoft's release notes also cover:

• Explorer.exe failing to start or crashing repeatedly, causing black screens, in multi-user environments such as Azure Virtual Desktop and FSLogix
• Always On VPN connections getting stuck on "Connecting" after KB5124008
• Tiered Storage Spaces Direct virtual disks failing to come online
• Printing failures with RAW or Generic Text Only drivers after the August update
• Mouse input stutter in some games
• Fingerprint sign-in failing after a cold boot

The update has its own problems too. Microsoft lists three known issues:

• Some devices can't turn Smart App Control back on.
• Non-admin users may be unable to make Remote Desktop connections, with error 0xC000000D, to hosts that have Administrator protection enabled. This affects KB5124010 and later updates.
• Some USB Audio Class 1.0 devices still fail to start or produce no sound. That bug began with the September 8 security update and is only partly fixed.

At least one outlet said Microsoft lists no new problems caused by KB5127648. Microsoft's own known-issues section says otherwise, so go by the official notes. If you run Remote Desktop hosts with Administrator protection, which Microsoft says is on by default in the Windows 11 24H2, 25H2 and 26H2 security baselines, test the update on one host first.

One more thing for 24H2 users: Microsoft says Windows 11 24H2 Home and Pro have reached end of updates, and KB5127648 is the last update for those editions. Install it to get the AC-3 fix and the final security patches, then plan an upgrade to a newer version of Windows 11. Otherwise the next bug like this won't get fixed on your PC.

Why audio bugs keep coming back​

Audio has been a recurring weak spot in Windows servicing. BleepingComputer recalls that two years ago Microsoft resolved a bug that caused games and apps using AC-3 (Dolby Digital) audio decoding to crash — no, that's this story. BleepingComputer's earlier examples were different bugs: game audio jumping to full volume on USB DACs, Intel Smart Sound Technology drivers causing blue screens that led Microsoft to block 24H2 upgrades, and a safeguard hold over Dirac audio software that broke Bluetooth headsets. Most recently there were the September USB audio failures.

The common thread, in my experience as a longtime Windows watcher, is legacy compatibility. Windows still ships decoders and audio paths that most new software skips. That leaves a large, quiet group of older apps that only notice a regression when something changes underneath them. The preview channel exists to catch exactly this kind of problem before Patch Tuesday, and here it worked roughly as intended: the bug was caught on opt-in machines and fixed in the next security release.

Is three weeks of crashing games a reasonable price for early access to fixes? If you'd rather not find out next time, turn off "Get the latest updates as soon as they're available" and wait for the monthly security update.

Bottom line​

• The problem: Apps that rely on the AC-3 (Dolby Digital) decoder built into Windows could crash after KB5124010.
• Affected versions: Windows 11 24H2, 25H2 and 26H2.
• The fix: KB5127648 (October 13, 2026) or later. It's cumulative, so you don't need to uninstall anything first.
• Check: Update history shows KB5127648, and your build ends in .9711 or higher.
• Watch for: KB5127648's own known issues (Smart App Control, Remote Desktop error 0xC000000D, USB Audio Class 1.0). If you're on 24H2 Home or Pro, this is your last update, so plan your upgrade.