HomeSeptember 2026 patch cycleKB5124008: USB Audio 1.0 Code 10, fixed in November
Call: DeployCategory: EnterpriseCategory: End-user appsfrom 2026-09
KB5124008: USB Audio 1.0 Code 10, fixed in November
Part of September 2026 patch cycle
- Vendor
- Microsoft
- Products
- Windows 10, Windows 11, and Windows Server 2016-2025
- Published
- Status
- Resolved
Call: Deploy. Resolved November 10. Microsoft confirmed it and fixed it. The November security updates fix the USB Audio Class 1.0 bug that came in with September’s updates. KB5132061’s notes say: “Fixed: USB Audio 1.0 devices might fail to start and display error code 10 in Device Manager after installing a recent security update.” Release health marks it resolved on November 10 for Windows 11 24H2 and 26H2 (KB5132061), Server 2025 (KB5131080) and Server 2016 (KB5131291). Windows 10 22H2 release health marks it resolved by KB5131096. For two days, the KB5131096 article itself still listed the bug as a known issue, with the old line that Microsoft was “working to address the other symptoms.” That’s what some patch lists picked up. On Nov 12, Microsoft corrected the article. Its change log now reads “Known issue fixed: ‘USB Audio 1.0 devices might fail to start and display error code 10 in Device Manager…’”. Server 2022 was already fixed in October by KB5129237. Install November, then turn your headsets back up to eight channels if you had dropped them to two.
What broke: Some USB Audio Class 1.0 devices, the simple class-compliant headsets, DACs and speakers, stopped working after the September 2026 updates (KB5124008 and its equivalents):
- Code 10 in Device Manager
- no sound
- volume controls that did nothing
Multichannel setups (8-channel and 3D audio) failed too. The out-of-band update KB5129195 fixed that part first.
Who was hit: Windows 10, Windows 11 and Windows Server machines with affected UAC1 devices. Microsoft had it at Mitigated from September 29 until this month.
If it’s still broken after November: Check that the November update actually installed (see the KB5132061 install-failure post). Until it does, switch the device to 2-channel output, which was the workaround all along.
Sources: KB5132061 release notes (opens in a new tab), release health 24H2 (opens in a new tab), release health 26H2 (opens in a new tab), release health Server 2025 (opens in a new tab), release health Server 2016 (opens in a new tab), PatchTriage (opens in a new tab), release health Windows 10 22H2 (opens in a new tab), KB5131096 release notes (opens in a new tab).
Sources
- https://support.microsoft.com/en-us/servicing/os/windows-11/2026/11/kb5132061-windows-11-24h2-25h2-26h2-security-update (opens in a new tab)
- https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24h2 (opens in a new tab)
- https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-26h2 (opens in a new tab)
- https://learn.microsoft.com/en-us/windows/release-health/status-windows-server-2025 (opens in a new tab)
- https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-1607-and-windows-server-2016 (opens in a new tab)
- https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-25h2 (opens in a new tab)
- https://patchtriage.com/2026-10/known-issues-2026-10 (opens in a new tab)
- https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22h2 (opens in a new tab)
- https://support.microsoft.com/en-us/servicing/os/windows-10/2026/11/kb5131096-windows-10-21h2-22h2-security-update (opens in a new tab)