USB Headset or DAC Showing Code 10 After the September Windows Update? What’s Fixed and What Isn’t (2026)

Your USB headset worked on September 7. On September 9 it had a yellow triangle in Device Manager and the volume slider was stuck at zero.

You’re not imagining it, and your headset almost certainly isn’t broken. Microsoft confirmed the bug on its release health dashboard. What most write-ups blur together is that there are two different failures here, and only one of them has a fix.

Find Your Fix

• Which Audio Devices Did the September Update Break?
• Code 10 or Multichannel Only — Which Problem Do You Have?
• How Do You Check If Your Device Is USB Audio Class 1.0?
• How Do You Fix the Multichannel Version?
• What Can You Do About Code 10 Right Now?
• Should You Uninstall KB5124008?
• Tips
• Warnings
• FAQ
• Sources

Which Audio Devices Did the September Update Break?

The September 8, 2026 Windows security update KB5124008 can stop some USB Audio Class 1.0 devices from starting or producing sound, according to Microsoft’s Windows 11 24H2 release health page. USB Audio Class 1.0 is an older driver standard used by many budget USB headsets, small USB DACs, and plug-in USB sound adapters.

Microsoft lists these symptoms:

• Device Manager shows “This device cannot start (Code 10).”
• No audio output at all.
• Volume controls are unresponsive or stuck at zero.
• Sound settings are unresponsive or unavailable.
• The device works in stereo but fails in multichannel modes, such as 8-channel or 3D audio.

The affected list is long. It covers Windows 11 versions 23H2 through 26H2, Windows 10 22H2 and 21H2, and Windows Server 2012 through 2025. BleepingComputer also ties the problem to the related KB5124012 security update.

Devices using USB Audio Class 2.0, Bluetooth, or a 3.5 mm analog jack are not part of the reported issue.

Code 10 or Multichannel Only — Which Problem Do You Have?

A USB audio device that only fails in 3D or 8-channel mode after KB5124008 is fixed by the September 14, 2026 out-of-band update KB5129195, but a device showing Code 10 in Device Manager is not fixed by any update as of Microsoft’s September 29, 2026 status note. Every step after this depends on which one you have.

Table: USB audio symptom triage based on Microsoft’s release health entry for KB5124008 (last updated September 29, 2026).

When I checked Microsoft’s entry, I noticed that the status label says “Mitigated,” which sounds finished. It isn’t. The resolution text says the OOB update only addresses the multichannel symptom and Microsoft is “working to address the other symptoms.”

That one word sends a lot of people chasing a fix that doesn’t exist yet.

How Do You Check If Your Device Is USB Audio Class 1.0?

A USB audio device is Class 1.0 if its hardware ID in Windows Device Manager contains USB\Class_01&SubClass_01 without a newer protocol value, a check described in Admin365’s write-up of the bug. It takes under a minute.

1. Right-click Start and open Device Manager.
2. Expand “Sound, video and game controllers.”
3. Right-click your USB audio device and choose Properties.
4. Open the Details tab and pick “Hardware Ids” from the drop-down.
5. Read the values. Class_01&SubClass_01 points to USB Audio Class 1.0.

While you’re there, check the General tab. If it says Code 10, you have the harder version of the bug.

How Do You Fix the Multichannel Version?

Installing the September 14, 2026 update KB5129195, or any Windows update released after it, fixes the USB audio failure that only appears in 8-channel or 3D audio modes. Most PCs already have it.

1. Open Settings > Windows Update and click Check for updates.
2. Install everything listed, then restart.
3. Run winver (Win + R, type winver). On 24H2 and 25H2 you want build .9457 or higher.
4. Switch your spatial or 7.1 mode back on and test.

If sound still cuts out in surround mode after that, you’re probably dealing with the Code 10 version after all. Recheck Device Manager.

What Can You Do About Code 10 Right Now?

No Microsoft update fixes the USB Audio Class 1.0 Code 10 error as of September 29, 2026, so the practical options are switching to 2-channel stereo, moving the device into a Class 2.0 mode if it has one, or using a different audio path until a fix ships. Try them in this order.

Method 1: Drop to 2-channel stereo. Microsoft notes some customers restored audio this way.

1. Right-click the speaker icon and open Sound settings.
2. Select your USB device under Output, then go to More sound settings (or Additional device properties).
3. Open the Advanced tab and choose a 2-channel format, such as 2 channel, 16 bit, 48000 Hz.
4. Click Apply and play something.

Method 2: Switch the device to UAC 2.0, if it can. Some USB DACs and headphone amps have a UAC1/UAC2 switch or a firmware setting. Check the manual or the maker’s support page. In Class 2.0 mode the device uses a different driver path that Microsoft hasn’t reported as affected.

Method 3: Use another route for now.

• Plug headphones into the PC’s 3.5 mm jack or monitor audio.
• Pair a Bluetooth headset for calls.
• Borrow any USB Audio Class 2.0 device. Most current USB audio interfaces are Class 2.0.

Here’s where people get tripped up: reinstalling the driver from Device Manager feels like the obvious move. I found that none of the reports Microsoft or BleepingComputer cite describe that fixing Code 10 for this bug, so don’t spend an evening on it.

For businesses, Microsoft’s entry says IT admins who need an immediate workaround for unfixed symptoms should contact Microsoft Support for Business.

Should You Uninstall KB5124008?

Uninstalling the September 8, 2026 update KB5124008 removes that month’s Windows security fixes, so it should be a last resort for a PC that has no other way to get working audio. Microsoft has not listed uninstalling as a workaround.

When I compared the options, the trade-off looked lopsided for most people. A $20 Bluetooth or analog headset gets you through a few weeks. An unpatched PC stays exposed to whatever the September update closed.

If you depend on a Class 1.0 device for paid work and nothing else works, the uninstall path is Settings > Windows Update > Update history > Uninstall updates. Expect Windows to try to reinstall it later, and plan to update again once Microsoft ships a fix.

Tips

• Bookmark Microsoft’s release health page and check the USB audio entry after the October 13 Patch Tuesday. Microsoft says it will update that entry when more information is available.
• If you buy a replacement headset or DAC, look for “USB Audio Class 2.0” or “UAC2” in the spec sheet.
• Keep a cheap analog headset in a drawer. Audio bugs in Windows updates are not rare — a similar Code 10 problem hit Class 1.0 devices in January 2025.

Warnings

• Don’t return or throw out a headset over this. The hardware is fine; the driver path is broken.
• Code 10 has plenty of other causes. If your audio failed before September 8, this bug probably isn’t the reason.
• Third-party “driver updater” tools won’t fix a Microsoft class-driver bug and often bundle junk. Skip them.

FAQ

Does this bug affect Windows 10?

Yes. Microsoft lists Windows 10 versions 22H2 and 21H2 and several Windows 10 LTSC editions among the affected platforms, alongside Windows 11 versions 23H2 through 26H2.

Will the October 2026 Patch Tuesday fix Code 10?

Microsoft has not said. As of September 29, 2026 the release health entry only says it is working on the remaining symptoms and will update the documentation when more information is available.

Are Bluetooth headphones affected?

No. The known issue is limited to USB Audio Class 1.0 devices. Bluetooth and 3.5 mm analog audio are not part of it, which is why they work as stopgaps.

Sources

• Microsoft Learn — Windows 11, version 24H2 known issues and notifications
• Microsoft Support — September 8, 2026, KB5124008
• BleepingComputer — Microsoft: September updates break audio on some Windows PCs
• Admin365 — September 2026 Patch Tuesday breaks USB audio

Fact-checked based on Microsoft’s Windows release health dashboard, Microsoft Support KB pages, and BleepingComputer reporting as of October 1, 2026. Status may change after the October 13, 2026 Patch Tuesday.