Microsoft Fixes USB Audio Code 10 Errors on Windows 10, Windows 11 and Server

The fix is narrower than the headline suggests, and the version details matter if you manage more than one machine.

What broke​

According to Microsoft's release health entry, some USB Audio Class 1.0 devices could fail to start or produce no sound. Microsoft lists four symptoms:

• Device Manager shows "This device cannot start (Code 10)."
• No audio output.
• Volume controls don't respond or stay stuck at zero.
• Sound settings don't respond or aren't available.

Microsoft says the issue is limited to USB Audio Class 1.0 devices. Not every USB audio device is affected. A USB-C or USB-A plug doesn't tell you which audio class a device uses, so check the model's specifications with the manufacturer if you're unsure. An ittrip.xyz troubleshooting guide makes the same point: a USB connector does not identify the audio class, so confirm the model and its specifications with the manufacturer.

Another group of users saw a variation of the bug. When BleepingComputer first reported the problem on September 14, 2026, some users said their USB speakers failed only when multichannel features such as 3D audio or 8-channel modes were turned on.

Summary: The bug affects one class of USB audio hardware, but its symptoms range from total silence to failures that only appear in surround-sound modes.

How the issue unfolded​

1. September 8, 2026. BleepingComputer reported, citing Microsoft's release health dashboard, that the problems started after the September security updates KB5124008 and KB5124012 were installed. At that point the issue was described as affecting only Windows 11 24H2 and later.
2. September 14, 2026. According to BleepingComputer, Microsoft released out-of-band updates that fixed the 8-channel and 3D audio failures. An ittrip.xyz summary of Microsoft's issue record describes the same two-stage fix: failures with eight channels or 3D audio were corrected on September 14; the remaining symptoms were resolved with the November 10 update and later ones. The Microsoft pages reviewed for this article don't show the September out-of-band KB numbers, so treat that stage as reported rather than confirmed.
3. November 3, 2026. The detailed issue entry on Microsoft's Windows 11 26H2 release health page was opened at 19:36 PT. That entry describes the problem as appearing after installing 26H2 and lists the originating update as "N/A." It doesn't name the September packages, which is why the September origin above is attributed to BleepingComputer.
4. November 10, 2026. The entry was marked resolved at 10:00 PT, alongside Patch Tuesday.

Who is affected: more than Windows 11​

In September the problem was described as a Windows 11 24H2-and-later bug. Microsoft's affected-platform list is now much longer:

Being on one of these versions doesn't mean you have the bug. You also need a USB Audio Class 1.0 device. Even so, admins who assumed their Windows 10 LTSC kiosks or Server 2016 boxes were safe should check again.

Which update fixes it​

For Windows 11, Microsoft's support page for KB5132061 covers:

• Windows 11 26H2 (all editions), build 26300.9974
• Windows 11 25H2 (all editions), build 26200.9974
• Windows 11 24H2 Enterprise and Education, build 26100.9974

The release notes for these versions include this line: "USB Audio 1.0 devices might fail to start and display error code 10 in Device Manager after installing a recent security update." For 24H2, KB5132061 also fixed an issue where audio could not be played via HDMI or DisplayPort on some AMD graphics cards.

Don't treat KB5132061 as the fix for every platform in the table. Microsoft says the issue is resolved by the November 10 security update "and later updates" across all affected platforms. The documentation reviewed here doesn't list the KB number for each Windows 10 and Windows Server release. Some reporting fills in parts of the picture, but check these before relying on them:

• TheTechHacker reports that Windows 11 26H1 gets the fix through KB5132059.
• A MalwareTips forum post relaying the November notes says version 23H2 also has the same release notes except the USB audio bug-fix. That's odd, because Microsoft lists 23H2 as affected. IT-Connect also describes this month's release as the last update for Windows 11 23H2. If you still run 23H2 with USB Audio 1.0 hardware, check the 23H2 release notes and release health page yourself.

Summary: On Windows 11 24H2, 25H2 and 26H2, install KB5132061 or later. On every other platform, install that platform's November 10 security update (or later) and confirm it in its own release notes.

How to fix it, step by step​

1. Confirm you have this bug. Open Device Manager and look under Sound, video and game controllers and Audio inputs and outputs. A USB audio device showing Code 10, together with the symptoms above, points to this issue.
2. Install the November update. Go to Settings > Windows Update and select Check for updates. Microsoft recommends installing the latest security update available for your device.
3. Restart to finish the cumulative update.
4. Check your build. Run winver. You should see 26300.9974, 26200.9974 or 26100.9974 (or higher) on the matching Windows 11 version.
5. Test the device. Make sure the USB device is the selected output, then play something you know has sound. Mixed-News suggests that if your USB audio device still fails after updating and restarting, check the device's status in Device Manager and the manufacturer's support guidance.

Prerequisites for managed and manual installs​

If you install the update from the Microsoft Update Catalog or through WSUS, Microsoft lists these requirements for KB5132061:

• Windows 11 26H2: an update released on or after September 22, 2026 (such as KB5124010) must already be installed, plus servicing stack 26100.9539 or later.
• Windows 11 24H2/25H2: an update released on or after June 10, 2025 (such as KB5060842) must already be installed, plus servicing stack 26100.4193 or later.

To check your servicing stack version, Microsoft suggests running DISM /Online /Get-Packages | findstr /i "ServicingStack" from an elevated command prompt. The Catalog package also includes a checkpoint cumulative update (KB5043080), which must be installed first. DISM installs it automatically if both MSU files are in the same folder.

Admins who got an emergency workaround from Microsoft Support for Business can drop it. Microsoft says you don't need a Known Issue Rollback or special Group Policy once the resolving update is installed.

If the update won't install​

Some people have trouble installing KB5132061 itself. Windows Report says users have seen 0x800f0993 and 0x800f0989 installation errors, while Microsoft lists no known issues for November's update. One user reported that running DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow got the update to install. Windows Report adds that Microsoft has not provided an official fix or explanation, so this is a reported workaround, not official guidance.

If you can't patch yet​

Microsoft hasn't published an official workaround for end users who can't install the update. BleepingComputer reports that some users got their audio back by changing the device's speaker configuration to 2-channel (stereo) mode. That makes sense for the multichannel variant of the bug, but don't expect it to fix a device that won't start at all. It's an unofficial user report, not a guaranteed fix or Microsoft guidance.

Analysis: patches, regressions and Code 10​

This isn't the first time a Windows update has broken USB audio. In January 2025, Microsoft fixed a similar problem caused by the optional preview update KB5050094, which led to playback failures and Code 10 errors on Windows 11 24H2 systems with USB audio drivers. Since then there have also been Intel Smart Sound Technology driver blocks and a Dirac-related safeguard hold.

The bigger problem in this case is the timeline. Microsoft acknowledged the bug within days of the September Patch Tuesday, the multichannel part reportedly got an out-of-band fix on September 14, and the rest took until November. Users of affected hardware had to choose between staying fully patched and having working audio. Small studios, broadcasters and anyone else relying on older class-compliant USB interfaces had a long wait.

In Microsoft's favour, the fix landed in a release that, at publication time, has no known issues listed, according to Microsoft. Reporting from Digital Citizen also says the November update is a large security release, with an actively exploited Outlook flaw among the fixes. You don't have to choose between security and sound anymore.

Bottom line​

• Affected: USB Audio Class 1.0 devices on Windows 10, Windows 11 and Windows Server 2012 through 2025, according to Microsoft.
• Fix: the November 10, 2026 security update and later. On Windows 11 24H2, 25H2 and 26H2, that's KB5132061.
• Admins: check each platform's own update rather than assuming the Windows 11 KB applies everywhere. No Known Issue Rollback is needed after patching.
• Can't patch yet: switching to 2-channel audio is an unofficial workaround that may help.