Skip to content
TroubleGrid

USB Audio No Sound or Code 10 After Windows Update KB5124008

Last verified November 2026Tested against Fixed by KB5132061 (10 November 2026) — OS builds 26300.9974 / 26200.9974 / 26100.9974, Windows 11 26H1 — fixed by KB5132059 (10 November 2026), OS build 28000.3501, KB5132061 applies to 26H2 and 25H2 all editions, and 24H2 Enterprise and Education only, Windows 11 24H2 Home and Pro — end of updates 13 October 2026, so the fix does not reach this version, KB5124008 (8 September 2026) — the update that caused this, KB5129195 (14 September 2026 out-of-band — 24H2 and 25H2, fixed the multichannel symptom), KB5129194 (14 September 2026 out-of-band, 26H1), KB5127648 (13 October 2026) — did not fix it; superseded by KB5132061, Also listed as affected: Windows 11 23H2, Windows 10 22H2 and 21H2, LTSC 2019 and 2016, Windows Server 2012–2025Well documented

Install the November 10, 2026 Windows security update. Microsoft marked this issue Resolved that day, and KB5132061 — OS build 26300.9974 on Windows 11 26H2, 26200.9974 on 25H2, 26100.9974 on 24H2 — fixes the symptoms that had been left open: Code 10, no sound at all, and dead volume controls. The multichannel half was already fixed by the 14 September out-of-band update, and KB5132061 is cumulative, so one update now covers both. One catch: it applies to 26H2 and 25H2 in all editions but to 24H2 in Enterprise and Education only, so a 24H2 Home or Pro PC has to move to 25H2 or 26H2 to receive it. On 26H1 the equivalent update is KB5132059.

This page is only about the KB5124008 regression, and as of 10 November 2026 it has a real fix rather than a workaround. The check in the second step still earns its ten minutes if the update does not help you, because it tells you whether you were hitting this specific bug or an ordinary audio fault — and the ordinary fixes (reinstalling the device, changing enhancements, swapping to an analog cable) were reported not to help here.

Symptoms

  • Device Manager shows "This device cannot start. (Code 10)" on a USB audio device
  • A USB headset, DAC or audio interface that worked before September 8, 2026 produces no sound
  • Volume controls are unresponsive or stay at zero
  • Sound settings are unresponsive or unavailable
  • The device plays fine in stereo but is silent in 7.1, 8-channel or 3D/spatial modes
  • The device broke right after the PC upgraded itself to Windows 11 version 26H2

Why this happens

KB5124008 broke the USB Audio Class 1.0 path

Microsoft’s release-health entry states the issue is limited to USB Audio Class 1.0 devices. Windows drives those with its in-box class driver usbaudio.sys, which it loads automatically when a device enumerates as USB Audio-compliant. Devices that enumerate as USB Audio 2.0 are driven by a different in-box driver, usbaudio2.sys, and fall outside the scope Microsoft describes; a manufacturer’s own driver overrides the class driver entirely. Microsoft never published a root cause, only the scope — and on 10 November 2026 it moved the entry to Resolved, naming KB5132061 as the fix.

Install the November 10, 2026 Windows security update · Confirm this is the KB5124008 regression before changing anything · Switch the device to 2-channel (stereo) output · Uninstall KB5124008 — only if you cannot install the November update

Multichannel modes fail even when stereo still works

Microsoft notes that some affected devices kept working in standard stereo configurations and failed only when multichannel audio features were used, including 8-channel or 3D audio modes. That is why a headset could look healthy in Device Manager, pass a stereo test tone, and still be silent in a game set to 7.1 surround. This half was fixed first, by the out-of-band update of 14 September 2026; the rest waited until 10 November.

Install the November 10, 2026 Windows security update · Switch the device to 2-channel (stereo) output · Uninstall KB5124008 — only if you cannot install the November update

Fixes

Install the November 10, 2026 Windows security update

about 20 min

Microsoft moved this known issue to Resolved on 10 November 2026. KB5132061 fixes the symptoms the September out-of-band update left open — Code 10, no sound at all and unresponsive volume controls — and being cumulative it carries the earlier multichannel fix too.

Applies to: Windows 11 26H2 (all editions), Windows 11 25H2 (all editions), Windows 11 24H2 Enterprise and Education, Windows 11 26H1 (via KB5132059)

  1. Select Start > Settings > Windows Update and select Check for updates. Install what is offered and restart when prompted.
  2. Confirm the build afterwards. The 10 November 2026 update produces OS build 26300.9974 on Windows 11 26H2, 26200.9974 on 25H2 and 26100.9974 on 24H2. On Windows 11 26H1 the equivalent update that day is KB5132059, OS build 28000.3501.
    winver
  3. Check that your edition is covered. Microsoft lists KB5132061 as applying to Windows 11 version 26H2 in all editions, version 25H2 in all editions, and version 24H2 in Enterprise and Education editions only. If winver reports 24H2 Home or Pro, the update will not be offered to you — those editions reached end of updates on 13 October 2026, and moving to 25H2 or 26H2 is what puts the PC back in line for monthly fixes.
  4. Reconnect the device and test it. A device that showed "This device cannot start. (Code 10)" should now start cleanly, and a frozen volume slider should move again.
  5. If you had switched the device to 2-channel as a stopgap, you can put it back. Open the Sound control panel, select the device on the Playback tab, click Configure and choose the surround layout you had before.
    mmsys.cpl
  6. If the symptoms survive the update, this known issue is probably not what you are hitting — Microsoft now lists no remaining open symptoms for it, and KB5132061 itself records no known issues. Run the check in the next fix, then fall back to the general no-sound steps.

Confirmed by the vendor.

Source: Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft

Confirm this is the KB5124008 regression before changing anything

about 5 min

Worth running if the November update did not fix it. This tells you whether your device is actually on the USB Audio Class 1.0 driver that Microsoft’s issue is limited to, or whether you are chasing the wrong bug.

Applies to: Windows 11 26H2, Windows 11 25H2, Windows 11 24H2, Windows 11 26H1

  1. Press Windows+R, type winver and press Enter. KB5124008 produces OS build 26100.9445 or 26200.9445. Build 26100.9974, 26200.9974 or 26300.9974 means you already have the 10 November 2026 security update, which Microsoft says resolves this issue — if symptoms persist on that build, this known issue is not your fault.
    winver
  2. To confirm the update by name, go to Start > Settings > Windows Update > Update history and look for KB5124008 in the list.
  3. If winver reports Windows 11 version 26H2, read the build check below differently. Microsoft lists this known issue against 26H2 itself rather than against a particular KB — the originating update on its 26H2 release-health entry is recorded as N/A — so there is no build number that tells you whether you have the bug. The Device Manager checks that follow are what identify it.
  4. Search for "Device Manager" in the Start menu and open it. Expand Sound, video and game controllers, right-click your USB audio device and select Properties.
  5. On the General tab, check whether the device status reads "This device cannot start. (Code 10)". Device Manager also marks a device that has a problem with a yellow exclamation point.
  6. Switch to the Driver tab and select Driver Details. If the listed file is usbaudio.sys, the device is running on the USB Audio Class 1.0 driver — the only class Microsoft says this bug affects. If it is usbaudio2.sys, your device is enumerating as a USB Audio Class 2.0 device and Microsoft's known issue does not describe it.
  7. If a manufacturer's own driver is listed instead, note that Microsoft documents partner drivers as overriding the in-box class driver. In that case your problem more likely belongs to that driver than to this update, and the manufacturer's support is the better place to start.

Confirmed by the vendor.

Source: Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft

Switch the device to 2-channel (stereo) output

about 5 min

Only a stopgap now, for a PC that cannot take the November update yet — a 24H2 Home or Pro machine waiting to move version, or one where updates are held. Microsoft’s wording was that switching to 2-channel restored audio for "some customers", not all.

Applies to: USB Audio Class 1.0 devices that fail only in multichannel modes, Windows 11 26H2, where no fix has shipped for any of the symptoms

  1. Open Start > Settings > System > Sound.
  2. Open the classic Sound control panel. On Windows 11 it sits under the advanced section of that page; on Windows 10 it is listed as Sound Control Panel. If you cannot find the link, press Windows+R and run mmsys.cpl instead.
    mmsys.cpl
  3. On the Playback tab, select your USB audio device and click Configure. If a surround layout such as 7.1 Surround is selected, choose Stereo and finish the wizard.
  4. If the device offers no Configure option, open Properties > Advanced instead and pick a 2-channel default format, then click Apply.
  5. Play something to test. If sound returns, the device works but is limited to stereo. If you had not yet installed the 14 September out-of-band update, install it — it restores multichannel on the devices it covers, so you may not need to stay in stereo at all.

Confirmed by the vendor.

Source: Microsoft, Microsoft, Microsoft, Microsoft Q&A, Microsoft

Uninstall KB5124008 — only if you cannot install the November update

Advancedabout 20 min

Superseded. Since 10 November 2026 there is a supported fix that keeps your security updates, so install that instead. This stays here only for a machine that genuinely cannot receive KB5132061 and is still broken.

Applies to: Windows 11 24H2, Windows 11 25H2, Windows 11 26H1

Before you do this

Uninstalling a security update leaves your PC without that month’s security fixes until you reinstall it, and Microsoft advises understanding the risks before removing one. Microsoft has not recommended this workaround for this bug — it comes from reader reports. On 24H2, 25H2 and 26H1 a supported update fixes the multichannel symptom without this tradeoff, so only consider uninstalling if your symptom is one that update does not cover. On 26H2 this route does not apply at all: the issue is recorded against the version itself rather than a removable KB, so there is no KB5124008 to uninstall. Windows will offer the update again, so it only sticks if you also pause updates.

  1. Try the November 10, 2026 security update first. It resolves this issue and removes any reason to give up security fixes.
  2. Select Start > Settings > Windows Update.
  3. Under More options, select Update history.
  4. Under Related settings, select Uninstall updates.
  5. Select KB5124008 in the list, choose Uninstall, and restart when prompted. Microsoft notes that some updates cannot be uninstalled — if KB5124008 is not listed, this route is not open to you.
  6. To stop Windows reinstalling it straight away, use the Pause updates control in Settings > Windows Update. Windows allows a pause of up to 35 days.
  7. Do not leave the pause running. The fix now exists, so resume updates and install KB5132061 (or your version’s 10 November 2026 update) as soon as the PC can take it.

Reported to work by 2 users; not confirmed by the vendor.

Source: Microsoft, Microsoft, Microsoft Q&A, Microsoft, Microsoft

Known issues

  • Resolved. Microsoft moved this entry to Resolved on 10 November 2026 on the Windows 11 24H2, 25H2 and 26H2 release-health pages, naming that day’s security update, KB5132061, as the fix for the remaining symptoms. KB5132061 lists it under Audio as "Fixed: USB Audio 1.0 devices might fail to start and display error code 10 in Device Manager after installing a recent security update", and records no known issues of its own.

    Affects Windows 11 26H2 (OS Build 26300.9974), Windows 11 25H2 (OS Build 26200.9974), Windows 11 24H2 (OS Build 26100.9974), KB5132061 (10 November 2026) · Status: fixed

  • The multichannel half was fixed two months earlier. The out-of-band update of 14 September 2026 — KB5129195 on Windows 11 24H2 and 25H2, KB5129194 on 26H1 — resolved the symptom where a device worked in stereo but went silent in 8-channel or 3D audio modes. KB5132061 is cumulative and later, so there is no longer any reason to hunt that out-of-band update down separately; installing the November update covers both halves.

    Affects KB5129195 (14 September 2026, 24H2 and 25H2), KB5129194 (14 September 2026, 26H1) · Status: fixed

  • Windows 11 24H2 Home and Pro do not receive this fix on that version. Microsoft lists KB5132061 as applying to version 24H2 in Enterprise and Education editions only, and 24H2 Home and Pro reached end of updates on 13 October 2026, so no monthly update carrying the fix will be offered. Moving the PC to 25H2 or 26H2 is what puts it back in line for it.

    Affects Windows 11 24H2 Home, Windows 11 24H2 Pro · Status: open

  • The fix is one day old and no reader has confirmed it yet. KB5132061 shipped on 10 November 2026 and this page was re-checked on 11 November. Microsoft states it resolves the remaining symptoms, but the Microsoft Q&A thread behind this page still ends on 14 September 2026, so there is no independent report either way on whether the update restores a device that was showing Code 10. If it does not, that is worth telling us.

    Affects KB5132061 (10 November 2026) · Status: unknown

If none of this worked

If you are already on OS build 26100.9974, 26200.9974 or 26300.9974 — the 10 November 2026 update — and the device is still silent, this known issue is no longer a candidate: Microsoft lists it as resolved on that build and records no remaining open symptoms. The same applies if Driver Details shows usbaudio2.sys or a manufacturer driver, or if the device fails on a second PC too. Microsoft’s issue is limited to USB Audio Class 1.0 devices, so Bluetooth headsets and motherboard analog outputs were never in scope. Start from the general no-sound checks instead.

Common questions

Has Microsoft fixed this?
Yes, as of 10 November 2026. The release-health entries for Windows 11 24H2, 25H2 and 26H2 all moved to Resolved that day, naming KB5132061 — the 10 November 2026 security update — as the fix for the symptoms that were still open: Code 10, no sound at all, unresponsive volume controls and unresponsive sound settings. The multichannel symptom had already been fixed by the out-of-band update of 14 September 2026. KB5132061 is cumulative, so installing it covers both. Note that the fix is new: it shipped the day before this page was last re-checked, and no reader report confirming it either way had appeared yet.
Which update do I actually need?
The 10 November 2026 security update for your version of Windows. On Windows 11 26H2, 25H2 and 24H2 that is KB5132061, producing OS builds 26300.9974, 26200.9974 and 26100.9974 respectively; on 26H1 it is KB5132059, OS build 28000.3501. Microsoft lists KB5132061 as applying to 26H2 and 25H2 in all editions but to 24H2 in Enterprise and Education editions only. If you are on an older Windows version that Microsoft lists as affected — Windows 11 23H2, Windows 10 22H2 or 21H2, LTSC or Server — the fix is in that version’s own 10 November 2026 security update rather than in KB5132061.
I am on Windows 11 24H2 Home. Why is the update not offered to me?
Because 24H2 Home and Pro reached end of updates on 13 October 2026, and Microsoft lists KB5132061 as applying to 24H2 in Enterprise and Education editions only. Those editions no longer get monthly updates at all, so the fix cannot reach you on that version. Moving to Windows 11 25H2 or 26H2 puts the PC back in line for monthly updates, this one included. Until then the 2-channel stopgap below is what is left.
Does this affect Bluetooth headsets or my motherboard’s audio?
No. Microsoft states the issue is limited to USB Audio Class 1.0 devices, so Bluetooth and onboard analog outputs are outside the scope of what it confirmed.
Will reinstalling the device in Device Manager fix it?
It was not reported to help while the bug was unfixed. Reporters on Microsoft’s Q&A forum tried uninstalling and reinstalling the headset in Device Manager, changing audio enhancement settings, and using a 3.5 mm analog cable, and none of those restored multichannel audio. Install the November update instead.
Should I still uninstall KB5124008?
No, not unless you cannot install the November update and the device is still broken. Uninstalling a security update to work around a bug that now has a supported fix costs you the security fixes for nothing. The steps are kept at the end of this page for the narrow case where KB5132061 cannot reach the machine.
Which Windows versions were affected?
Microsoft’s affected-platforms list covers Windows 11 versions 26H2, 26H1, 25H2, 24H2 and 23H2, Windows 10 versions 22H2 and 21H2, Windows 10 Enterprise LTSC 2019 and 2016, and Windows Server versions from 2012 through 2025. Windows 11 26H2 was added when that version reached general availability on 29 September 2026 and spent six weeks with no fix available; it is now resolved along with the rest.

Did this fix work?

If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.

Report a problem with this page

Related problems

Sources

  • Microsoft · Release notes · checked Nov 11, 2026

    • The USB audio known issue is marked Resolved by KB5132061, resolved 10 November 2026 at 10:00 PT
    • Microsoft states the remaining symptoms are resolved in the security update released on 10 November 2026 (KB5132061) and later updates
    • The symptoms are Code 10 in Device Manager, no audio output, unresponsive or zero volume controls, and unresponsive sound settings
    • The issue is limited to USB Audio Class 1.0 devices
    • The 8-channel and 3D audio symptom was resolved by the out-of-band update of 14 September 2026
    • Affected platforms span Windows 11 26H2, 26H1, 25H2, 24H2 and 23H2, Windows 10 22H2 and 21H2, LTSC 2019 and 2016, and Windows Server 2012 through 2025
  • Microsoft · Release notes · checked Nov 11, 2026

    • The USB audio known issue is marked Resolved by KB5132061, resolved 10 November 2026 at 10:00 PT
    • Microsoft states the remaining symptoms are resolved in the security update released on 10 November 2026 (KB5132061) and later updates
    • The symptoms are Code 10 in Device Manager, no audio output, unresponsive or zero volume controls, and unresponsive sound settings
    • The issue is limited to USB Audio Class 1.0 devices
    • The 8-channel and 3D audio symptom was resolved by the out-of-band update of 14 September 2026
    • Affected platforms span Windows 11 26H2, 26H1, 25H2, 24H2 and 23H2, Windows 10 22H2 and 21H2, LTSC 2019 and 2016, and Windows Server 2012 through 2025
  • Microsoft · Release notes · checked Nov 11, 2026

    • On Windows 11 26H2 the USB audio known issue is marked Resolved by KB5132061, resolved 10 November 2026 at 10:00 PT
    • The 26H2 entry lists Code 10, no audio output, unresponsive or zero volume controls and unresponsive sound settings, and does not list the multichannel symptom
    • Microsoft states the symptoms are resolved in the security update released on 10 November 2026 and later updates
    • The issue is limited to USB Audio Class 1.0 devices
  • Microsoft · Knowledge base · checked Nov 11, 2026

    • KB5124008 was released 8 September 2026 producing OS builds 26100.9445 and 26200.9445.
    • The KB5124008 article now lists the USB audio failure among its known issues.
  • Microsoft · Knowledge base · checked Nov 11, 2026

    • KB5129195 is the out-of-band update of 14 September 2026, OS builds 26200.9457 and 26100.9457
    • It applies to Windows 11 version 25H2 and version 24H2
    • It records as fixed: some USB Audio Class 1.0 devices working in stereo but failing in 8-channel or 3D audio modes
  • Microsoft · Knowledge base · checked Nov 11, 2026

    • KB5129194 is the 14 September 2026 out-of-band update carrying the same fixes for Windows 11 version 26H1.
  • Microsoft · Support page · checked Nov 11, 2026

    • KB5132061 was released on 10 November 2026 and produces OS builds 26300.9974 on Windows 11 26H2, 26200.9974 on 25H2 and 26100.9974 on 24H2
    • KB5132061 lists under Audio: "Fixed: USB Audio 1.0 devices might fail to start and display error code 10 in Device Manager after installing a recent security update"
    • KB5132061 applies to Windows 11 version 26H2 all editions, version 25H2 all editions, and Windows 11 Enterprise and Education version 24H2 only
    • KB5132061 states "Microsoft is not currently aware of any issues with this update"
    • The 26H1 security update released on 10 November 2026 is KB5132059, OS build 28000.3501
  • Microsoft · Support page · checked Nov 11, 2026

    • KB5127648 of 13 October 2026 produces OS builds 26300.9711, 26200.9711 and 26100.9711
    • Windows 11 24H2 Home and Pro reached end of updates on 13 October 2026
    • As of 13 October 2026 KB5127648 described the resolution as covering only the 8-channel and 3D audio symptom
  • Microsoft · Documentation · checked Nov 11, 2026

    • Usbaudio.sys is the in-box class driver for devices complying with the USB Device Class Definition for Audio Devices release 1.0
    • Windows loads the USBAudio driver automatically when a device identifies itself as USB Audio-compliant during Plug and Play enumeration
  • Microsoft · Documentation · checked Nov 11, 2026

    • usbaudio2.sys is the in-box driver for USB Audio 2.0 class devices, shipped since Windows 10 release 1703
    • If a partner driver exists on the system or Windows Update, that driver is installed and overrides the class driver
    • usbaudio.sys is identified as the USB Audio 1.0 driver
  • Microsoft · Documentation · checked Nov 11, 2026

    • Device Manager places a yellow exclamation point next to a device that has a problem and shows an error message describing it
  • Microsoft · Support page · checked Nov 11, 2026

    • Updates are removed from Settings > Windows Update > Update history > Uninstall updates, and some updates cannot be uninstalled
  • Microsoft · Support page · checked Nov 11, 2026

    • Windows updates can be paused for up to 35 days from the current date
  • Microsoft · Support page · checked Nov 11, 2026

    • Documents the Sound control panel route for selecting a playback device and changing its configuration, including opening it with mmsys.cpl.
  • Microsoft Q&A · Forum · checked Nov 11, 2026

    • Readers on Microsoft Q&A reported that HyperX Cloud Orbit S headsets lost 7.1 audio after KB5124008, that uninstalling the update restored it and reinstalling broke it again, and that the taskbar volume control froze
    • Reinstalling the device in Device Manager, changing enhancement settings and using a 3.5 mm analog cable were reported not to help
    • The thread carries 7 replies and its last reply is dated 14 September 2026; re-read on 11 November 2026 nobody has reported back on whether the fix worked