If your USB headset, speaker, or DAC went silent after a Windows update, you have probably hit the Windows 11 USB audio Code 10 bug. Microsoft confirmed that the September 8, 2026 security update can stop older USB Audio Class 1.0 devices from starting, and switching the device to 2-channel stereo is the quickest way to get sound back.
Here’s the short version, then the full fix list below.
- Trigger: KB5124008 (Windows 11 24H2 and 25H2), or KB5124012 on 26H1.
- Who’s hit: Only USB Audio Class 1.0 devices, on Windows 11 24H2 or later.
- Symptom: Device Manager says “This device cannot start (Code 10)” and you get no sound.
- Workaround: Switch the device from multichannel or 3D audio to 2-channel stereo.
- Status: Still listed as unresolved in coverage of the October update, KB5127648.
If you only skim one section, make it the stereo fix further down.
What the Windows 11 USB audio Code 10 bug actually does
After the update, Windows sometimes refuses to start the audio device at all. You’ll see no output, volume sliders that stay at zero or won’t respond, and sound settings that stop working.
According to BleepingComputer, Microsoft acknowledged the problem on its release health dashboard. Some people report the failure only in multichannel modes such as 3D audio or 8-channel, while plain stereo keeps working.
Microsoft hasn’t published a technical root cause. What we know is the trigger (the September update) and the pattern (older USB audio devices in surround modes).
Which devices and Windows versions are affected
USB Audio Class 1.0 is the older driver standard that many plug-and-play headsets, budget DACs, and audio interfaces still use. Newer class 2.0 devices aren’t named in Microsoft’s description.
| Detail | What’s reported |
|---|---|
| Windows versions | 24H2 and 25H2 (KB5124008), plus 26H1 (KB5124012) |
| Device type | USB headsets, speakers, DACs, and audio interfaces using Audio Class 1.0 |
| Error shown | “This device cannot start (Code 10)” in Device Manager |
| Modes that fail | Often multichannel or 3D audio; some devices still work in stereo |
| Official fix | None yet, per IT-Connect’s October update review |
This matters because the fix depends on whether your device actually offers a stereo mode. Check that before you start pulling updates.
How to tell the update is the culprit, not your hardware
A silent headset has many causes, so confirm this one before you change anything. A dead cable and a Code 10 error look the same from the couch.
Start with Settings, Windows Update, Update history, and look for KB5124008 or KB5124012 with a date around September 8. Then open Device Manager, double-click your USB audio device, and read the status box on the General tab. If it says the device cannot start, and the same gear worked a few weeks ago, you’re in the right place.
Next, try the device on another computer or a phone. If it plays fine there, the hardware is healthy. That single test saves you from buying a replacement headset you don’t need, which is the most expensive mistake in this whole saga.
The 2-minute fix: switch to stereo first
Microsoft’s own workaround is to drop the device to 2-channel mode, and some users report that restores audio. It costs you surround or 3D effects, but nothing else.
Look for the setting in Windows sound settings, the manufacturer’s companion app, or a physical switch on the device. Not every device offers it.
If that doesn’t work, run through these in order, and stop when sound returns:
- Open Settings, then Windows Update, and install anything pending. Restart afterward.
- Go to Settings, System, Sound, and pick a different output device to confirm the rest of your audio works.
- Unplug the device, plug it into a different USB port, and check Device Manager again.
Reinstalling the audio driver isn’t a confirmed fix for this bug, so don’t spend an hour on it. As far as Wintips reports, the problem lies with the update, not your driver.
Should you uninstall the September update?
Only as a last resort. Rolling back KB5124008 removes the security fixes that came with it, and you’d have to reinstall later.
If you do it, go to Settings, Windows Update, Update history, then Uninstall updates, and pick KB5124008. Restart, and pause updates only briefly.
A simpler option for many people is a Bluetooth headset or a different adapter until Microsoft ships a fix. We covered the broader October Windows 11 update and another bug from the same September update if you want the full picture.
Frequently Asked Questions
Why does my USB headset show Code 10 on Windows 11?
Code 10 means Windows couldn’t start the device. In this case it follows the September 8, 2026 update and affects USB Audio Class 1.0 devices.
Does the October update fix the USB audio problem?
Not according to IT-Connect’s review of KB5127648, which lists the USB Audio Class 1.0 issue as still unresolved. Check Microsoft’s release health page for the latest status.
Is my newer USB-C headset affected?
Probably not unless it uses Audio Class 1.0. Microsoft’s description names only that older class.
How do I know if my device uses USB Audio Class 1.0?
Check the spec sheet or manufacturer’s support page, which often mentions “UAC1” or “USB Audio Class 1.0.” Many simple plug-and-play headsets that need no driver install fall into this group, but confirm with the maker rather than guessing.
Will Bluetooth audio work while this is broken?
The reports concern USB devices only, so Bluetooth and the built-in speakers are a reasonable stopgap.
My take: try stereo mode first, keep the update installed, and use another output for a few days. Pulling a security patch over an audio quirk is a poor trade for most people. The exception is a work setup that depends on a USB audio interface, where a short, deliberate rollback may be worth it.
Leave a Reply