Windows 11's September patch is killing USB audio — and there's still no fix
If your speakers or headset went silent after a Windows 11 update this month, the problem isn't your hardware. Microsoft's September 8 patch, KB5124008, breaks USB audio on Windows 11 versions 24H2, 25H2, and 26H1 — and as of writing, there is still no official fix.
The bug
The update disrupts USB Audio Class 1.0 devices, a standard used by a wide range of gear: USB headsets, audio DACs, gaming headsets like HyperX models, and professional audio interfaces. Affected users report Code 10 errors in Device Manager, complete loss of audio output, and volume controls that simply stop responding. Microphones are also hit — not just speakers. Multichannel, 3D, and 8-channel audio modes fail outright. Microsoft has confirmed the issue on its release health dashboard, though it has given no timeline for a resolution.
The only workaround reported so far is switching the audio output to 2-channel stereo in Sound Settings — an unofficial fix that some users say restores basic audio. Hardware Busters notes this is the only guidance Microsoft has offered, and it doesn't help everyone.
A recurring problem
This isn't an isolated slip. Bleeping Computer reports that January 2025's KB5050094 caused a similar audio regression, and Hardware Busters has tracked more than ten cumulative update regressions affecting audio since August 2025. The pattern points to a quality-assurance gap in Microsoft's monthly patch process — changes that affect specific hardware classes appear to be reaching stable channels without adequate pre-release testing.
What to do now
If you rely on USB audio for home office calls, music production, streaming, or gaming, the safest move is to hold off on installing KB5124008 if you haven't already. If you've already updated and lost audio, try switching to stereo mode under Settings → System → Sound → [your device] → Output format. Uninstalling the update via Settings → Windows Update → Update history → Uninstall updates is also an option, though it may reappear automatically.
Microsoft says it is working on a fix. Given the company's track record on this class of bug, it's worth checking the Windows 11 release health dashboard periodically for an update.