You should still install the update. Here's what broke, who was affected, what the fix covers, and the separate USB audio problem that is still only partly solved.
What broke: AC-3 decoding after the September preview
Back in September, Microsoft released optional preview update KB5124010, which caused issues with Windows 11's built-in decoding of Dolby Digital AC-3 audio. According to PCWorld, the bug caused some games and apps to crash when changing volume or using certain audio functions. In some cases, apps and games even failed to launch.
Windows Report described the same pattern. Some applications crashed immediately after launching, while others closed unexpectedly when users performed certain actions, such as playing music. Games, media players, and some productivity applications were among the affected software.
Microsoft's own wording is narrower. The KB5127648 notes say only that the update "fixes an issue that affects AC-3 audio playback in some applications." Microsoft doesn't name any apps, give a count, or explain the root cause. The details about specific crash triggers come from press reports, not from Microsoft's release notes.
Who was most at risk:
- Apps that use Windows' own AC-3 decoder instead of shipping their own
- PCs that installed the September 22 preview (KB5124010) or any later update
- Windows 11 versions 24H2, 25H2 and 26H2
Most programs weren't affected as long as they relied on their own audio decoding components. But for any that relied on the built-in offerings in Windows 11, a fix was desperately needed from Microsoft.
Summary: An optional September preview broke Windows' built-in AC-3 decoding. Apps that depended on it could crash or refuse to start. Apps with their own decoders were mostly fine.
A strange detail: Windows doesn't ship an AC-3 codec anymore
Here's an odd twist for anyone who has wondered why AC-3 audio in a video file sometimes plays silently. PCGlance cites Microsoft's media player troubleshooting page: "Beginning with Windows 11, version 24H2, the AC-3 codec is no longer included with Windows."
So there are two separate problems that are easy to mix up:
| Symptom | Likely cause | What to do |
|---|---|---|
| App crashes, closes or won't launch when using AC-3 audio | The September regression, starting with KB5124010 | Install KB5127648 or later |
| AC-3 video plays with no sound in a media player | Windows 11 24H2+ no longer includes an AC-3 codec | Use a player with its own decoder |
For the silent-playback case, PCGlance reports that a Microsoft support moderator suggested a player "that already included their support codecs, such as VLC media player". That was an informal forum answer, not an official workaround. KB5127648 won't add the codec back. It only fixes the crash.
The fix: KB5127648 and the builds to look for
Microsoft has officially marked the problem as resolved with KB5127648, released on October 13 as part of the company's monthly Patch Tuesday rollout. Once installed, your build number should be:
- Windows 11 24H2: OS Build 26100.9711
- Windows 11 25H2: OS Build 26200.9711
- Windows 11 26H2: OS Build 26300.9711
KB5127648 is a cumulative update. Microsoft's release notes say it includes the September 8 (KB5124008), September 14 out-of-band (KB5129195) and September 22 (KB5124010) updates. If you already have those, Windows downloads only what's new.
How to install and check it (home users)
- Press Windows + I to open Settings.
- Select Windows Update, then Check for updates.
- Install KB5127648 (or a newer cumulative update) if it's offered, and restart when prompted.
- Press Windows + R, type
winver, and check that your build ends in .9711 or higher. - Open the app that was crashing and play some AC-3 audio to confirm it works.
Users can install the update through Windows Update, and no additional workaround is necessary once the installation succeeds. Tech2Geek gives sensible advice if a crash continues: check for additional Windows updates and verify that the application itself is up to date.
For IT admins
According to Microsoft's release notes:
- The update arrives automatically through Windows Update and Windows Update for Business, following your configured policies.
- In WSUS, it syncs under Product "Windows 11" and Classification "Security Updates."
- Microsoft Update Catalog packages include a required checkpoint cumulative update (KB5043080), which must be installed before the target package. You can also run
DISM /Online /Add-Packageagainst the KB5127648 MSU and let DISM install the checkpoint automatically. - 24H2 and 25H2 devices need the June 10, 2025 update (such as KB5060842) or later, plus the latest servicing stack. KB5127648 includes servicing stack update KB5127647.
Some install failures have been reported. Reports indicate that KB5127648 fails to install with errors 0x800f0845 and others.
Summary: Install KB5127648 and check for build .9711. Microsoft lists no separate AC-3 workaround, so ignore advice to tweak codecs or replace system files.
The other audio bug: USB Audio Class 1.0 is only partly fixed
The original report also mentions a second audio problem from September. This is a different bug from the AC-3 crash, and KB5127648 does not fully fix it.
Microsoft's October release notes say some USB Audio Class 1.0 devices might fail to start or produce no sound. Symptoms include:
- Device Manager showing "This device cannot start (Code 10)"
- No audio output
- Volume controls that don't respond or stay stuck at zero
- Sound settings that are unresponsive or missing
- Devices that work in stereo but fail in multichannel modes such as 8-channel or 3D audio
Microsoft says some customers got sound back by switching to 2-channel mode. The out-of-band update KB5129195 (September 14) fixed the 8-channel and 3D audio symptoms only. Microsoft says it is still working on the rest. Admins who need an immediate workaround are told to contact Microsoft Support for Business. Wccftech says the same: that issue has only been partially resolved, with Microsoft continuing to work on the remaining symptoms.
The update numbers don't match. Some coverage blames KB5124008 for the USB problem. Microsoft's known-issue entry instead names "the September 8, 2026, Windows security update (KB5124012)," while listing KB5124008 as that day's update elsewhere on the same page. We can't settle this from the evidence available. What both sources agree on is that the trouble started with the September 8 security update.
Other fixes in KB5127648, and a few new problems
Microsoft's release notes also list these fixes:
- Windows Explorer: In multi-user environments such as Azure Virtual Desktop and FSLogix, Explorer.exe could fail to start or keep crashing after sign-in, leaving a black screen.
- Gaming: Mouse input could stutter in some games.
- Storage Spaces Direct: Tiered virtual disks could fail to come online after certain security updates, taking clustered workloads down with them.
- Printing: Some apps couldn't print through RAW or Generic Text Only drivers after the August 2026 update.
- Windows Hello: Fingerprint sign-in could fail after a cold boot on some devices.
Early reports also credited KB5127648 with an Always On VPN fix. Microsoft's change log says that note was removed on October 20, and the fix is now promised "in a future release." Don't count on this update for VPN problems.
The update also brings new known issues:
- Smart App Control: On some devices, it can't be turned back on once it has been turned off. Microsoft provides a registry fix and Group Policy mitigations.
- Remote Desktop: Since KB5124010, non-admin users may fail to connect to hosts with Administrator protection enabled, getting error 0xC000000D.
- NTLMv1: When the BlockNtlmv1SSO value isn't set and Credential Guard is off, Windows now defaults to Enforce mode. That can affect Wi-Fi, Ethernet and VPN connections that use MS-CHAPv2.
If you run 24H2 Home or Pro, you need to upgrade
Microsoft's KB5127648 page says Windows 11 24H2 Home and Pro have reached end of updates. The October 2026 update is the last one those editions will get. These users still get the AC-3 fix, but it's their final patch. Upgrade to 25H2 or 26H2 to keep receiving security fixes, including whatever finally resolves the USB audio bug.
Analysis
This is a typical Windows servicing problem. An optional preview update broke a system component that most modern software doesn't use, so the people who got hit were mostly running older games and media tools that depend on Windows' own decoder. The fix took about three weeks and came in the next Patch Tuesday. That's not fast, but it's normal.
Why do people keep calling it a vulnerability? Probably because the fix shipped in a security update, so "security update fixes audio bug" turned into "audio vulnerability." The difference matters for prioritizing patches. You should install KB5127648 for its actual security fixes and because it stops the crashes, not because AC-3 audio was ever a way to attack your PC.
One last thing: if your USB headset or DAC went quiet in September, this update won't fix it. Check whether it's a USB Audio Class 1.0 device, try 2-channel mode, and keep an eye on future cumulative updates.