If your USB headset, mic, or speaker went silent or showed “This device cannot start (Code 10)” after September’s Windows security updates, Microsoft’s November 10, 2026 Patch Tuesday updates resolve the remaining documented symptoms. The September 14 emergency patch only fixed part of the problem.
What Happened: USB Audio Not Working After a Windows Update
According to BleepingComputer’s original report, Microsoft’s September 2026 security updates broke some USB audio devices. BleepingComputer named those updates as KB5124008 and KB5124012.
Microsoft’s Windows release health entry traces the issue on most branches to the September 8 security update and lists a broad set of affected platforms. On Windows 11 version 26H2, Microsoft instead says the problem appeared after installing version 26H2 itself. That list covers Windows 11 versions 23H2 through 26H2, Windows 10 versions 21H2 and 22H2, Windows 10 Enterprise LTSC 2016 and 2019, and Windows Server 2012 through Windows Server 2025.
Affected PCs showed three symptoms:
- A “This device cannot start (Code 10)” error in Device Manager
- No sound output at all
- Volume controls and sound settings that stopped responding
The failing layer is narrow. Microsoft says the issue is limited to devices using the older USB Audio Class 1.0 standard. Budget USB headsets, mics, DACs, and older USB speakers commonly use this standard, though not every device in these categories is necessarily affected.
Microsoft’s documented scope is USB Audio Class 1.0 devices only, and it doesn’t list USB Audio Class 2.0 devices as affected. That isn’t a guarantee for every other audio setup, and it doesn’t rule out unrelated audio problems.
To check your own PC, open Device Manager from the Start menu search. Then expand Sound, video and game controllers. A yellow warning icon on a USB audio entry, with Code 10 in its properties, matches this bug.
How the Two-Stage Fix Stacks Up
On the branches affected by the September 8 update, Microsoft fixed this in two passes. An out-of-band update on September 14 addressed only the multichannel failures, such as 8-channel and 3D audio modes. On Windows 11 that update was KB5129195 for versions 24H2 and 25H2, and KB5129194 for version 26H1. On Windows 10 ESU and Enterprise LTSC 2021 PCs, it was KB5129236. Microsoft’s notes for it say other audio symptoms were not resolved.
The remaining symptoms were fixed on November 10. Microsoft’s KB5132061 release notes list the USB Audio 1.0 Code 10 fix for Windows 11 versions 24H2, 25H2, and 26H2. BleepingComputer also reported the fix, citing Microsoft’s Release Health dashboard. Other branches ship separate packages, so KB5132061 is not the number every reader should expect.
For Windows 11 23H2, Microsoft’s 23H2 release health page lists KB5131087 as the resolving update. For Windows 10 ESU PCs (versions 21H2 and 22H2) plus Enterprise and IoT Enterprise LTSC 2021, Microsoft lists KB5131096. Consumer and commercial Windows 10 22H2 PCs receive it through the Extended Security Update program. Match your version against the table below, or check Microsoft’s Release Health dashboard.
| Windows version | Resolving November KB (per Microsoft) |
|---|---|
| Windows 11, versions 24H2, 25H2, and 26H2 | KB5132061 |
| Windows 11, version 23H2 | KB5131087 |
| Windows 10 ESU (21H2, 22H2; enrollment required) and Enterprise / IoT Enterprise LTSC 2021 | KB5131096 |
| Windows 11, version 26H1 | KB5132059 |
| Windows Server 2025 | KB5131080 |
| Other branches (Windows 10 LTSC 2016/2019, Windows Server 2012 through 2022) | Separate package per branch, listed on that branch’s Release Health page |
| Option | What it fixes | Source |
|---|---|---|
| September 14 out-of-band update (KB5129195 / KB5129194 on Windows 11; KB5129236 on Windows 10) | Multichannel failures in 8-channel and 3D audio modes only | Microsoft KB5129195 and KB5129236 release notes |
| November 10 security update for your branch | Remaining USB Audio Class 1.0 symptoms, including Code 10 | Microsoft Release Health and KB5132061 notes |
| Switch device to 2-channel stereo | Temporary relief for multichannel failures, based on customer reports | Microsoft Release Health (customer reports) |
| Use a USB Audio Class 2.0 device | Outside the scope of this specific bug; not a guarantee against other audio faults | Microsoft Release Health (scope note) |
The update ships through normal Windows Update on supported Windows 11 versions. On Windows 10, KB5131096 reaches version 21H2 and 22H2 PCs only if they’re enrolled in the ESU program, while Enterprise and IoT Enterprise LTSC 2021 get it through their own LTSC servicing. A Windows 10 22H2 PC that isn’t enrolled in ESU no longer receives security updates, so it won’t get this fix. Like any monthly security update, the package also carries other security and quality fixes; the USB audio repair is one item in it.
The Reaction
Community reaction is still forming. We haven’t seen verified reports of the November fix failing.
What to Do Next
Open Settings > Windows Update, click Check for updates, install the November security update for your Windows version, and restart.
If audio still fails, go to Settings > Windows Update > Update history. Make sure the November update for your specific branch shows as installed, not just any KB number you found online. If you use a multichannel device, check that the September 14 fix or a later update is there too.
If Code 10 persists after both updates, the cause may lie elsewhere. Check the cable, the port, the device’s driver or firmware, and the device itself.
Can’t update right now? Microsoft’s release health entry notes that some customers restored audio on multichannel devices by switching to 2-channel mode. Treat that as a stopgap. If you’re replacing a budget headset anyway, a USB Audio Class 2.0 headset or USB DAC falls outside this bug’s documented scope.
Our Take
Install the November update that matches your Windows version. Don’t keep pausing it. Holding back security patches to protect a headset is a bad trade.
For most readers this is a contained problem. Microsoft limits the bug to USB Audio Class 1.0 devices and lists a resolving November update for the branches it documents, though persistent failures can still have another cause.
The real trap is the timeline. If you installed the September 14 patch and still had silence, you may have thought your hardware died. That may not be the case.
Wrapping Up
The November 10 update that matches your Windows version is the fix that matters. After you install it, reboot, then unplug the USB device and plug it back in. Then check Device Manager. If the entry shows no warning icon and you hear sound, the fix stuck. If Code 10 follows the device to a different port or another updated PC, suspect the device, its driver, or its firmware rather than this bug.