You plug in the same USB headset you used yesterday, and Windows 11 stays silent. The volume slider will not move, the sound settings page freezes, or Device Manager shows a yellow warning that says This device cannot start (Code 10). It feels like the headset died overnight. In most cases it did not. The usual trigger is a Windows security update from September 2026, and the problem is still open on Microsoft’s known-issues list.
This guide explains which devices are affected, why the Code 10 error appears, and every fix worth trying, from the quickest to the last resort. Last updated: October 20, 2026.
Quick Answer
Microsoft has confirmed that the September 8, 2026 security update broke some USB Audio Class 1.0 devices on Windows 11. The October 13 updates did not fully repair it, and Microsoft still lists the issue as Mitigated, which means a workaround exists but a permanent fix does not. First, install every pending update. If your device works in stereo but fails in 8-channel or 3D audio, switch it to 2 channel output. If it still shows Code 10, restart the PC, move the device to a different USB port, and use Bluetooth, HDMI or the built-in speakers until Microsoft ships a fix. Your hardware is almost certainly fine. If an update leaves your PC failing to install in the first place, our guide on Windows 11 updates that get stuck or fail covers that separate problem.
What Microsoft Has Confirmed
The timeline matters here, because many people think the October update caused the problem when it actually began a month earlier.
- September 8, 2026: Patch Tuesday brings KB5124008 for Windows 11 24H2 and 25H2, KB5122880 for 23H2 and KB5124012 for 26H1. After installing, some USB Audio Class 1.0 devices fail to start or produce sound.
- September 14: Microsoft releases an emergency update, KB5129195, for 24H2 and 25H2. It fixes the 8-channel and 3D audio failure, but Code 10 and silent devices remain on the known-issues list.
- October 13: The October updates arrive: KB5127648 for 24H2, 25H2 and 26H2, KB5126653 for 23H2 and KB5127646 for 26H1. They fix other bugs, but the USB audio issue is still marked Mitigated.
Microsoft’s own description lists these symptoms: Device Manager shows Code 10, there is no audio output, volume controls stay at zero or do not respond, and sound settings may be unresponsive. Some devices work in normal stereo but fail in multichannel modes, and some people restored audio by switching to 2-channel mode.
Which Devices Are Affected?
Only USB Audio Class 1.0 devices. That is an older standard, and it is still very common. A USB Audio Class 1.0 device is one that Windows recognizes straight away with its built-in driver, so you never had to install any software for it. That usually means:
- Budget USB headsets and gaming headsets with a plain USB plug
- Small external USB sound cards and DAC dongles
- Generic USB speakers and soundbars
- USB microphones and webcam microphones that need no driver
Microphones can fail too, which can break video calls even when your speakers are fine. Bluetooth headphones, HDMI audio and your 3.5 mm jack use different paths and are not part of this issue. A home PC with no USB audio gear is not affected.
Troubleshooting Table
| What You See | Most Likely Cause | Start With |
|---|---|---|
| Yellow warning and Code 10 in Device Manager | The September USB audio regression | Fix 1 |
| Works in stereo, fails in 8-channel or 3D | Multichannel mode problem | Fix 3 |
| No sound and volume stuck at zero | Device failed to start | Fix 2 |
| Works on another PC, not this one | Windows update, not the hardware | Fix 4 |
| Microphone silent in calls | USB mic is Audio Class 1.0 | Fix 5 |
| Work PC managed by IT | Needs Microsoft’s workaround | Fix 7 |
Why This Is Happening
1. A Windows update changed how USB Audio Class 1.0 starts
The September 8 security update changed something in Windows that older USB audio devices depend on. When the device tries to start, Windows refuses, and Device Manager reports Code 10. This is a Windows-side fault, not a damaged cable or a dead headset.
Clue: the device worked perfectly until the first restart after the September update, and it still works on a different, older PC.
2. The October update carries the same problem forward
Windows updates are cumulative, so the October update contains the September changes. Installing it did not remove the bug, and skipping it does not avoid the bug either.
Clue: Settings > System > About shows build 26100.9711, 26200.9711 or 26300.9711 and the device is still silent.
3. Multichannel modes fail even when stereo works
Some devices start in basic stereo but fail when asked to use 8-channel or 3D audio. The September 14 emergency update addressed this specific case on 24H2 and 25H2.
Clue: sound plays after you pick 2 channel, but disappears when a surround or spatial mode is on.
4. A stuck device state after the update
Sometimes Windows keeps a failed startup record for the device. This does not cause the bug, but it can keep the device in a failed state until it is removed and detected again.
Clue: the warning icon stays even after you unplug and reconnect the device without restarting.
Fix 1: Confirm It Is This Issue
- Right-click Start and open Device Manager.
- Expand Sound, video and game controllers and Audio inputs and outputs. Look for your USB device with a yellow warning icon.
- Double-click it. Under Device status, check for This device cannot start (Code 10).
- Open Settings > Windows Update > Update history and look for KB5124008, KB5122880, KB5124012 or a newer October update.
Test: you see Code 10 on a USB audio device and the September update is in your history. That means the remaining fixes apply to you.
Fix 2: Install All Pending Windows Updates
- Go to Settings > Windows Update and select Check for updates.
- Install everything offered, including optional updates if they are listed, and restart.
- Confirm you have the right October update: KB5127648 for 24H2, 25H2 and 26H2, KB5126653 for 23H2, or KB5127646 for 26H1.
This will not repair every device, but it removes the 8-channel and 3D audio failure and puts you on the newest build. When Microsoft ships the final fix, it will arrive through Windows Update, so keep checking.
Test: Settings > System > About shows a current build, and your device either works or fails the same way as before.
Fix 3: Switch the Device to 2-Channel Output
This is the workaround that some affected users reported working, and it costs nothing to try. The trade-off is that you lose surround and 3D modes.
- Open Settings > System > Sound and scroll to All sound devices.
- Select your USB headset or speaker.
- Find the Format option and choose a 2 channel entry, such as 2 channel, 24 bit, 48000 Hz.
- If the Format list is not available, press Win + R, type
mmsys.cpland press Enter. Select the device, click Properties, open the Advanced tab, choose a 2-channel format and click OK. - Turn off any spatial sound or surround option for that device.
Test: you hear the Windows test sound when you press the Test button.
Fix 4: Restart Fully and Try a Different USB Port
- Unplug the USB device.
- Select Start > Power > Shut down. A full shut down reloads the USB audio stack more completely than a quick restart on some PCs.
- Turn the PC back on and wait for the desktop to load.
- Plug the device straight into a USB port on the PC itself, not into a hub or dock. Try a rear port on a desktop.
Hold the Shift key while clicking Shut down if you use Fast Startup, because it forces a clean shutdown.
Test: the device no longer shows a warning icon in Device Manager.
Fix 5: Remove the Device and Let Windows Detect It Again
- Open Device Manager and right-click the failing USB audio device.
- Select Uninstall device. Do not tick any option to delete driver software unless the maker told you to.
- Unplug the device and restart the PC.
- Plug it back in and let Windows set it up again.
- For a microphone, also check Settings > Privacy & security > Microphone and make sure access is on.
This step clears a stuck state. It cannot repair the underlying Windows bug, so if Code 10 returns right away, go to the next fix. If a different device shows a warning icon after an update, see our guide on the yellow warning icon in Device Manager.
Test: Windows lists the device as working properly and the Sound settings page responds again.
Fix 6: Check for a Newer Driver or Firmware from the Maker
- Find the exact model of your headset, DAC or speaker.
- Visit the maker’s official support page and look for a firmware update or companion app.
- Install it only if the page says it supports Windows 11 and your device.
Some makers publish a notice or firmware once Microsoft confirms a bug like this. If your device has both a vendor driver and the standard Windows driver, follow the maker’s instructions rather than switching drivers blindly.
Test: the maker’s page lists a newer version, and after installing it Device Manager shows no warning.
Fix 7: Use Another Output Until Microsoft Ships a Fix
If nothing above works, the quickest way to get sound back is to avoid the failing path altogether.
- Click the speaker icon near the clock and open the output device list.
- Pick Bluetooth headphones, HDMI audio from a monitor, the 3.5 mm jack or the built-in speakers.
- For calls, choose a different microphone in the app’s own audio settings.
On a work PC, ask your IT team to contact Microsoft Support for Business. Microsoft says administrators can get a workaround that way.
Test: you can hear audio and join a call while the USB device is set aside.
Should You Uninstall the Windows Update?
For most people, no. The October update contains the September changes, so removing October alone returns you to a build that has the same bug. Removing security updates also leaves your PC exposed to the flaws they patched. Microsoft advises trying other steps first and uninstalling only when an update causes a problem you cannot work around. If you do roll back, do it through Settings > Windows Update > Update history > Uninstall updates, and pause updates only for a short time. In this case, the 2-channel workaround and a different audio output are safer.
Pro Tips
- Keep a cheap Bluetooth headset or a wired earphone as a backup for calls and meetings.
- After any Patch Tuesday, test your audio and microphone before an important meeting.
- Check Microsoft’s Windows release health page for your version when something breaks after an update.
- Write down your build number from Settings > System > About before and after you install updates.
- Do not buy a new headset until you have tested the old one on another computer.
Common Mistakes to Avoid
- Assuming the headset is broken. Test it on another PC or a phone first.
- Skipping updates to avoid the bug. The issue is already in September’s update, and you lose security fixes.
- Downloading driver tools from random sites. They can install the wrong driver or unwanted software.
- Deleting driver software at random. Only do it if the device maker tells you to.
- Forgetting the microphone. The same bug can silence USB microphones, not just output.
FAQs
Why is my USB headset showing Code 10 in Windows 11?
Code 10 means the device could not start. After the September 8, 2026 update, Microsoft confirmed that some USB Audio Class 1.0 devices fail to start on Windows 11. It is a Windows problem rather than a hardware fault.
Did the October 2026 update fix the USB audio problem?
Not fully. The October 13 updates fixed other issues, but Microsoft still lists the USB audio problem as Mitigated. A permanent fix is expected in a future Windows update.
Is my USB audio device affected?
If it is a driverless USB headset, DAC, speaker or microphone that worked as soon as you plugged it in, it is likely to use USB Audio Class 1.0. Not every such device fails, but those are the ones Microsoft ties to the issue.
Why does my device work in stereo but not surround?
Some devices start in basic stereo but fail in 8-channel or 3D modes. The September 14 emergency update fixed this on 24H2 and 25H2, and switching to 2-channel output is a known workaround.
Will uninstalling the update fix my USB audio?
It is unlikely to help. The October update includes the September changes, and removing security patches is risky. Use the 2-channel setting or another audio output instead.
Does this affect Windows 10?
Microsoft’s confirmed issue is for Windows 11 versions 24H2, 25H2, 26H2 and 26H1, and the 23H2 release health page also lists it. If you use Windows 10 and see Code 10, the cause may be something else, such as a driver or port problem.
When should I contact the device maker or Microsoft?
Contact the maker if the device also fails on another computer. Contact Microsoft Support, or your IT team on a work PC, if the device works elsewhere, Code 10 persists after every fix above, and you need the workaround for managed devices.