USB Audio Not Working After a Windows 11 Update? How to Fix the Code 10 Error

Few things are more annoying than sitting down at your computer, plugging in your USB headset for a call, and hearing... nothing. No sound, no microphone, just silence — even though the same headset worked perfectly last week. If this happened to you shortly after a Windows update, I have good news: your headset is probably fine, and so are your speakers. What you are very likely looking at is a known bug that arrived with a recent Windows 11 update, and it has a name: Code 10.

I am Muhammad Hafeez, and on this blog I walk through tech problems in plain English, step by step. In this guide I will help you confirm whether this bug is your problem, explain why it happened, and take you through the fixes worth trying — in the order I would try them myself — before you spend money on a new headset you do not need.

Table of Contents

• Is This Your Problem? The Symptoms of the Code 10 Bug
• Why It Happened: The September Update and USB Audio Class 1.0
• Fix 1: Unplug, Change Port, Disable and Re-Enable the Device
• Fix 2: Update, Roll Back or Reinstall the Audio Driver
• Fix 3: Switch the Device to Stereo (2-Channel) Mode
• Fix 4: Make Sure the September Emergency Fix Is Installed
• Last Resort: Removing the Update (and Why to Think Twice)
• What If Your Sound Problem Is Something Else?
• Common Mistakes to Avoid
• Frequently Asked Questions
• The Bottom Line

Is This Your Problem? The Symptoms of the Code 10 Bug

This bug has a very specific fingerprint. Run through this checklist:

• Your wired USB headset, USB speakers or USB DAC stopped working right after a Windows update in September or October 2026.
• The device still lights up, and it works fine on another computer.
• In Device Manager, the device shows a yellow warning triangle.
• When you open the device's Properties, the Device status box says: "This device cannot start. (Code 10)".
• Your laptop's built-in speakers may still work normally, because they do not use the same USB path.

Here is how to check. Right-click the Start button and open Device Manager. Expand Audio inputs and outputs and Sound, video and game controllers, then double-click your USB device and read the Device status on the General tab. If you see Code 10 and the timing matches a recent update, you are in the right place. If the device does not appear in Device Manager at all, skip to the last section of this guide — that points to a different problem.

Why It Happened: The September Update and USB Audio Class 1.0

Most USB headsets and speakers never needed a special driver from the manufacturer. They use a standard driver built into Windows itself, called USB Audio Class 1.0. That convenience is exactly what turned against them here.

On September 8, 2026, Microsoft released the update KB5124008 — and that update broke USB Audio Class 1.0 devices. Headsets, speakers and DACs that rely on the built-in class driver suddenly failed to start, producing the Code 10 error. Microsoft confirmed the problem as a known issue on its release health pages in late September, so this is not guesswork: it is an acknowledged Windows bug.

The frustrating part is that it is still not fully fixed. The October 13 update, KB5127648, still lists the issue as known, and the October 28 preview update, KB5127936, fixed other bugs but not this one. So at the time of writing there is no single official patch that makes the error vanish for everyone — which is why the workarounds below matter. And let me say it once more, because it saves people money: nothing is physically wrong with your device.

Fix 1: Unplug, Change Port, Disable and Re-Enable the Device

Start with the simplest reset. It sounds basic, but it forces Windows to load the class driver fresh, and it genuinely revives the device for some people.

1. Unplug the device completely and wait about 30 seconds.
2. Plug it into a different USB port — ideally one directly on the PC or laptop, not through a hub or dock.
3. Restart the computer with the device plugged in.
4. If it is still silent, open Device Manager, right-click the device, choose Disable device, wait a few seconds, then right-click it again and choose Enable device.

Test with a short video and a quick voice recording to check both the speakers and the microphone. If sound is back, you are done — no need to continue.

Fix 2: Update, Roll Back or Reinstall the Audio Driver

Even though the class driver is built into Windows, refreshing its installation can clear a bad state left behind by the update.

1. In Device Manager, right-click your USB audio device and open Properties, then the Driver tab.
2. Click Update driver and choose Search automatically for drivers.
3. If the Roll Back Driver button is available (not greyed out) and your problem began right after a driver change, try rolling back.
4. If neither helps, right-click the device and choose Uninstall device. Then unplug it, restart the PC, and plug it back in — Windows will reinstall it from scratch.

Driver trouble after an update is not limited to sound, by the way. If your wireless connection also started misbehaving around the same time, our guide to why your Wi-Fi keeps disconnecting on Windows 11 walks through that fix ladder too.

Fix 3: Switch the Device to Stereo (2-Channel) Mode

One workaround reported by many owners of affected devices is worth trying next: some multichannel USB audio devices fail under this bug while plain stereo output still works. Forcing 2-channel mode can bring the sound back.

1. Open Settings → System → Sound and, under Output, select your USB device.
2. For the classic route, open Control Panel → Sound, go to the Playback tab, select your device and click Configure, then choose Stereo and finish the wizard.
3. While you are there, click Properties → Advanced and set the Default Format to a 2-channel option (for example, 2 channel, 16 bit, 48000 Hz). As a test, also untick Enable audio enhancements.

If sound returns, simply leave the device in stereo mode until Microsoft ships the real fix. Most calls, videos and music are stereo anyway, so you lose very little in the meantime.

Fix 4: Make Sure the September Emergency Fix Is Installed

Microsoft sometimes pushes small emergency fixes outside the normal monthly update cycle, so it is worth making sure you have not missed any fix released for this problem:

1. Open Settings → Windows Update and click Check for updates. Install everything offered, and restart if asked.
2. In Windows Update → Advanced options → Optional updates, install any audio or driver updates listed there.
3. Test your device again after the restart.

One honest expectation check: in the October 13 update notes (KB5127648), Microsoft still listed this as a known issue, and the October 28 preview did not include a fix. So if Windows Update offers nothing that cures it today, you have not missed a hidden patch — rely on Fixes 1 to 3 for now, and re-check after each new update. And while you are digging around in settings, if your PC has also felt sluggish lately, our guide to speeding up a slow Windows 11 laptop is worth a look.

Last Resort: Removing the Update (and Why to Think Twice)

If the headset is essential — say, your job depends on calls — and nothing above worked, you can remove the update that caused the problem:

1. Open Settings → Windows Update → Update history → Uninstall updates.
2. Find KB5124008 in the list and uninstall it.
3. Restart the computer and test your device.
4. If it works, you can pause updates for a week or two so the update does not immediately reinstall itself.

Now the warning, and it matters: that update also carried security fixes, and Windows may reinstall it later anyway. Removing it trades safety for sound, so treat it as a temporary measure. Keep your browser and antivirus up to date, and let Windows install its updates again once Microsoft confirms the audio bug is fixed.

What If Your Sound Problem Is Something Else?

Not every silent PC has this bug. Use these quick differences to tell:

• All sound is gone, including the built-in speakers — that is a different cause; check your main sound driver and the Windows Audio service instead.
• Sound works in most apps but not in Zoom, Teams or Discord — the app itself has probably selected the wrong output or input device in its own settings.
• A Bluetooth headset will not connect — that is a pairing problem, a separate issue from this wired USB bug.
• The USB device does not appear in Device Manager at all — try another cable and port, and test it on a second computer; that pattern points to hardware.
• The error code is different, such as Code 43 — look up that specific code; this guide covers the Code 10 error from the September update.

Common Mistakes to Avoid

• Buying a replacement headset before checking Device Manager. If Code 10 is showing, the old device is almost certainly fine.
• Downloading "driver updater" tools from random websites. They are a common route to malware. Only use Windows Update or the device maker's official site.
• Skipping the restart after driver changes. Many of these fixes only take effect after a reboot.
• Uninstalling every audio entry in Device Manager at once. You can knock out your working built-in sound too, and turn one problem into two.
• Pausing Windows Update forever after removing KB5124008. You would miss future security fixes — including the real fix for this bug when it lands.

Frequently Asked Questions

What does Code 10 mean in Device Manager?

It means Windows tried to start the device but the driver failed to load — the full message is "This device cannot start. (Code 10)". On USB audio devices after September 2026, it usually points to the update bug covered in this guide rather than broken hardware.

Is my USB headset permanently broken?

Almost certainly not. If the headset works on another computer, the hardware is fine. It is the driver state on your PC that needs fixing, and the steps above are exactly how to do it.

Has Microsoft fixed the Code 10 audio bug yet?

Not fully, as of late October 2026. Microsoft confirmed it as a known issue, it was still listed in the October 13 update (KB5127648) notes, and the October 28 preview update (KB5127936) did not include the fix. Keep checking Windows Update.

Will uninstalling the September update definitely fix it?

It has worked for many people, because it removes the change that broke the driver. But it also removes that month's security fixes, so treat it as a last resort and let Windows update again once Microsoft confirms the real fix.

Does this bug affect Bluetooth headsets too?

No. This problem is specific to wired USB Audio Class 1.0 devices — headsets, speakers and DACs that plug in with a cable. Bluetooth audio uses a different path, so a Bluetooth failure has its own causes.

The Bottom Line

Silence after a Windows update does not mean dead hardware. Confirm the Code 10 error in Device Manager, then work through the fixes in order: reconnect and re-enable the device, refresh the driver, try stereo mode, and make sure no available fix has been missed. Most people get their sound back without spending anything. Save the update removal for a genuine last resort — and keep an eye on Windows Update, because that is where Microsoft's proper fix will arrive.