Key Takeaways
- Check for Code 10: The September Windows 11 update KB5124008 caused some USB Audio Class 1.0 headsets and speakers to go silent, freeze the Sound page, or leave volume stuck at zero. Check Device Manager for Code 10 and run winver to check your build.
- Install the Fix: For Windows 11 USB audio showing “This device cannot start (Code 10),” install KB5132061 and restart. If needed, try a direct USB port and stereo, disable spatial audio and enhancements, reinstall the driver, then restart Windows Audio and Windows Audio Endpoint Builder.
- Test Your USB Audio: If Windows 11 USB audio still fails, test your headset or speakers on another PC and check for a manufacturer driver. Upgrade 24H2 Home or Pro to 25H2 or 26H2 to get the fix, and use Bluetooth headphones or built-in speakers in the meantime.
Your USB headset, speakers, DAC, or mic goes silent, and Device Manager says “This device cannot start (Code 10).” The September 8, 2026 Windows 11 security update, KB5124008, caused that error on some USB Audio Class 1.0 devices. Microsoft fixed the bug in the November 10 update, KB5132061.
You might also find your volume stuck at zero or the Sound page frozen. If your PC can install KB5132061, start there. Restart Windows, then unplug your USB audio device and plug it back in.
Still silent? Your Windows edition matters here, since 24H2 Home and Pro received their final update in October. Check your build first, then work through the fixes that fit what you’re seeing.
What Went Wrong With USB Audio in Windows 11
The September security update left some USB audio devices unable to start and others unable to play sound in certain modes. To see why one headset could go silent while another worked on the same PC, start with the driver Windows uses.
Which Devices Were Hit
USB Audio Class 1.0, or UAC1, lets compatible devices work through a driver Windows already has, called usbaudio.sys. That’s how many plug-and-play gaming headsets, USB speakers, desk mics, and USB-C to 3.5 mm adapters work. Some speakerphones, simple DACs, and audio interfaces use it too.
A USB Audio Class 2.0 device using usbaudio2.sys or a device using its maker’s own driver was outside the scope of this bug. If your UAC1 headset worked before the September update and suddenly shows Code 10, check the update and driver before spending money on a replacement.
How Long the Bug Lasted
The September 14 emergency update fixed failures in 8-channel and 3D audio modes, but Code 10, silent output, and the volume stuck at zero persisted. Both the October security update and the October 28 preview left those symptoms unresolved.
Microsoft listed affected Windows 11 releases from 23H2 through 26H2, including 26H1, as well as Windows 10 22H2 and other Windows 10 editions. Here’s how the fix rolled out.
| Date in 2026 | Update | What happened to USB audio |
|---|---|---|
| September 8 | KB5124008 for 24H2 and 25H2, KB5124012 for 26H1 | Some devices went silent, showed Code 10, or had their volume stuck at zero. |
| September 14 | KB5129195 emergency update | Fixed failures in 8-channel and 3D audio modes. |
| September 22 | KB5124010 preview | The remaining USB audio symptoms persisted. |
| September 29 | Windows 11 26H2 became widely available | The bug was present in 26H2 too. |
| October 13 | KB5127648 | The bug persisted through the final update for 24H2 Home and Pro. |
| October 28 | KB5127936 preview | The USB audio bug remained open. |
| November 10 | KB5132061 | Microsoft fixed the remaining symptoms on eligible editions. |
How to Tell If This Bug Is Your Problem
A silent headset alone gives you little to go on. Device Manager tells you whether Windows failed to start it, and your build number tells you whether your PC has the fix. Check the error first.
Check Device Manager for Code 10
Right-click Start and open Device Manager. Expand Sound, video and game controllers and look for your USB device. You can also check Audio inputs and outputs if the device appears there.
Double-click the device and read Device status on the General tab. “This device cannot start (Code 10)” means a driver failed to start the device. If you see it on a UAC1 headset that went silent after the September update, check your Windows build next.
Check Your Windows Build
Open Settings > System > About and look for your Windows version and OS build. You can also run winver to see both. The build prefixes for 24H2, 25H2, and 26H2 are 26100, 26200, and 26300, respectively.
Affected builds span .9445 through .9818 across those releases, with the exact range depending on your version. On eligible editions, 26100.9974, 26200.9974, and 26300.9974 contain the fix, as do later builds in those branches. You can check Settings > Windows Update > Update history for KB5132061.
How to Get Your USB Audio Working Again
If your Windows edition can receive the November update, install it before changing audio formats or reinstalling drivers. Once your PC has restarted, give the headset, speakers, or mic a quick test before moving on to the next fix.
Install the November 10 Update and Restart
Go to Settings > Windows Update > Check for updates. KB5132061 covers all editions of Windows 11 25H2 and 26H2, plus Enterprise and Education on 24H2. It includes the changes from the October 28 preview, and Microsoft listed no known issues for KB5132061 at release.
Install the update and choose Restart for a full reboot. Once you’re back at the desktop, unplug the USB device and reconnect it. Try playing audio through your headset or speakers, or check whether Windows picks up sound from your mic.
If the update itself refuses to install, follow our guide for when a Windows 11 update is stuck or failing.
Reconnect the Device Directly to the PC
If your USB audio runs through a dock, monitor, or unpowered hub, unplug it from there and connect it to the PC itself. Try a rear motherboard port on a desktop or a built-in USB port on a laptop.
Still quiet? Try another built-in port so Windows detects the device again. Microsoft gave similar advice after a USB audio bug in January 2025, when it suggested bypassing an intermediate DAC and connecting the audio device directly.
Switch the Device to 2-Channel Stereo
Some owners reported that their USB audio worked again when they switched from multichannel output to two-channel stereo, and Microsoft cited those reports. If your device starts but goes silent in multichannel or virtual 7.1 mode, stereo is worth a try.
Open Control Panel > Hardware and Sound > Sound > Playback. Select your USB playback device, then choose Configure > Stereo. If your headset maker’s app controls virtual 7.1, turn it off there.
From the Playback tab, open the device’s Properties > Advanced > Default Format. Try a common option such as 16-bit, 48000 Hz if it’s available, then play audio again.
Turn Off Spatial Sound and Audio Enhancements
Go to Settings > System > Sound and select your USB headset or speakers under Output. Find Audio enhancements and set it to Off.
On the same device page, set Spatial audio to Off. Since 3D audio modes were part of the original bug, try ordinary stereo playback with both options off to see whether sound returns.
Reinstall the Device in Device Manager
If your USB audio device still shows Code 10 after the update, right-click it in Device Manager and choose Uninstall device. If you see “Attempt to remove the driver for this device,” select it and confirm the uninstall.
Restart the PC so Windows can detect the device and reload usbaudio.sys for a UAC1 device that uses the built-in driver. If the device doesn’t reappear, open Device Manager and choose Action > Scan for hardware changes. Check Device status again before testing the sound.
Restart the Windows Audio Services
If the Sound page still freezes or the volume stays at zero, open services.msc. Find Windows Audio, right-click it, and choose Restart. Do the same for Windows Audio Endpoint Builder.
Once both services are running again, reopen Settings > System > Sound and try the volume slider. If it responds, play audio through the USB device to check whether playback is back too.
Upgrade If Your Windows Version Is Out of Support
Windows 11 24H2 Home and Pro received their last update on October 13, 2026. Home and Pro on 23H2 reached the end of support in November 2025. To get the fix on either version, open Settings > Windows Update and upgrade to 25H2 or 26H2. Windows 11 24H2 end of support
If you’re on Windows 10 22H2, you need active Extended Security Updates to receive November’s KB5131096. Whether that Windows 10 update contains the USB audio fix remains unconfirmed.
Here is what the Windows 11 24H2 end of support means and how to upgrade.
Roll Back the Latest Update as a Last Resort
Consider a rollback only if you can’t install the November fix yet. Open Settings > Windows Update > Update history > Uninstall updates, then select the latest affected update if Windows lets you remove it. From the Windows Recovery Environment, use Troubleshoot > Advanced options > Uninstall Updates > Uninstall latest quality update.
The affected cumulative updates carried the September changes forward, so removing the newest update can leave you on an earlier build that still has the bug. A rollback also removes security fixes, and some updates can’t be uninstalled. If you need a brief pause, go to Settings > Windows Update > Pause updates > Pick a date. Windows allows up to 35 days, but resume updates as soon as you can install the fix.
If You Still Have No Sound After the Update
If your build has the fix and your headset or DAC still won’t start, see whether the same device works on a second computer. That gives you somewhere to start before you change another driver or contact support.
Test the Device on Another Computer
Try the headset, mic, or interface on a second computer, ideally one that already has the fix. If it fails there too, check the cable, power, and the device itself.
One Lexicon Alpha Studio owner reported that the interface showed Code 10 after KB5124008 but worked on another PC and on an older Windows installation. If your device also works on another computer, keep troubleshooting the PC where it fails.
Using wireless earbuds instead? See our fixes for AirPods Pro 3 not working on Windows 11.
Look for a Vendor Driver or Firmware
Check the manufacturer’s support page for your exact DAC, headset, or audio interface. Look for a Windows driver or firmware for that model, especially if Windows still shows Code 10 after reinstalling the built-in driver.
Some DACs and interfaces may offer a USB Audio Class 2.0 mode or a separate driver from the maker. Either option can bypass usbaudio.sys if your device supports it. Whether changing modes restores sound on your specific model is unconfirmed.
Report It to Microsoft
Open the Get Help app and run the audio troubleshooter. If the device still fails, report it in Feedback Hub with the device model, your Windows build, and the exact message you see in Device Manager.
If the problem affects a work PC managed by your organization, your IT team can contact Microsoft Support for Business. Include whether the device worked on another computer so support can start with what you’ve already checked.
How to Avoid the Next Audio-Breaking Update
If you rely on USB audio for calls, streams, or recording, a few days can give you time to see whether a new update causes trouble. Start by timing the install around when you need your audio gear.
Wait a Few Days Before Installing Patch Tuesday
If you have a stream or recording session coming up, you can pause updates for about a week through Settings > Windows Update > Pause updates > Pick a date. Check the Windows release health page during that time for known issues affecting your version.
When the pause ends, Windows resumes updates automatically. You can resume them sooner if you have time to install the update and test your audio before your next call or session.
Keep a Backup Audio Output Ready
Keep a pair of Bluetooth headphones handy or check that you can switch to your PC’s built-in speakers. Open the taskbar Speakers control, select the arrow beside the volume slider, and choose your backup output.
Before a big Windows update, you can also create a restore point. That gives you a System Restore option if your usual audio stops working and the other fixes fail.
FAQs
Code 10 means a driver failed to start your USB headset. If it uses usbaudio.sys and the message appeared after the September 2026 update, it fits the USB Audio Class 1.0 bug Microsoft fixed in November. Check your Windows build to see whether the fix is already installed.
Install KB5132061, released November 10, 2026, or a later security update for your eligible Windows 11 edition. KB5132061 covers 25H2 and 26H2 across all editions and 24H2 Enterprise and Education. If you have 24H2 Home or Pro, upgrade to 25H2 or 26H2 to get the fix.
Uninstalling a security update removes its security fixes, so save that step for when you can’t install the November update. Later cumulative updates carried the same USB audio bug, so removing a single update may still leave you on an affected build. Windows also prevents some updates from being removed.
Look for usbaudio.sys in your USB device’s driver details in Device Manager. That’s the built-in Windows driver for USB Audio Class 1.0. If you see usbaudio2.sys, your device is using the USB Audio Class 2.0 driver.
A volume slider stuck at zero was one of the symptoms Microsoft listed for the September USB audio bug. Install KB5132061 or a later update that includes the fix and restart your PC. If the slider still won’t move, restart Windows Audio and Windows Audio Endpoint Builder in services.msc.
Yes, Microsoft listed Windows 10 22H2 and several other Windows 10 releases among the affected versions. If you use Windows 10 22H2, you need active Extended Security Updates to get November’s KB5131096. Whether that update includes the USB audio fix remains unconfirmed.
