KB5124008 kills sound on USB Audio Class 1.0 devices on Windows 11 (September 13, 2026)
Chapters
TL;DR
USB audio devices stopped working on Windows 11 after KB5124008, September's security update, and Microsoft has confirmed it: the known issue on its Windows release health dashboard was opened at 18:36 PT on September 11, 2026 and last updated at 19:10 PT that evening, with the status Confirmed. Windows Latest published the detailed account on September 13, 2026: no output, the Device Manager error about the device not starting with Code 10, unresponsive volume controls, unresponsive Sound settings and misbehaving microphones. The fault is limited to USB Audio Class 1.0 devices, and there is no fix, only a switch to 2-channel mode that restores audio on some of them.
- Microsoft's status is Confirmed, and it says it is working on a resolution. Nothing has shipped as of September 13, 2026.
- Microsoft's own symptom list: the Device Manager error This device cannot start (Code 10), no audio output, volume controls unresponsive or stuck at zero, and Sound settings unresponsive or unavailable.
- Some devices work in plain stereo and fail in multichannel, 8-channel or 3D audio modes, and Microsoft says some customers have restored audio by switching to 2-channel mode.
- The issue is limited to USB Audio Class 1.0 devices and lists Windows 11 26H1, 25H2 and 24H2, with no server release affected. Wireless devices appear unaffected so far.
- Removing KB5124008 brings sound back and gives up September's security fixes with it.
What Microsoft confirmed
The release health entry says USB audio devices might fail to start or produce no sound. Its symptom list is short and precise: an error in Device Manager reading "This device cannot start (Code 10)", no audio output, volume controls unresponsive or remaining at zero, and Sound settings unresponsive or unavailable. The scope line is the one that decides whether this is your problem: this issue is limited to USB Audio Class 1.0 devices.
Microsoft opened the entry at 18:36 PT on September 11, 2026 and last updated it at 19:10 PT the same evening. It lists Windows 11 26H1, 25H2 and 24H2 as affected, and no server release. Microsoft Support carries the same problem as the first entry in the KB5124008 known issues section, published September 8, 2026, noting that some devices function in stereo but fail in multichannel, 8-channel or 3D audio modes, and that Microsoft is working on a resolution.
What people at the keyboard see
Windows Latest adds the parts Microsoft's entry leaves out. Audio can fail completely immediately after the reboot that finishes the update, so the machine comes back silent with no obvious cause. Microphones malfunction as well as outputs, which matters if your calls run through a USB headset or an interface. Multichannel configurations are lost. The Sound settings page itself can stop responding, which removes the first place most people would look.
Its other useful observation is a negative one: wireless devices appear unaffected so far. Combined with Microsoft's own line that the fault is limited to USB Audio Class 1.0 devices, that gives a rough boundary, and newer USB audio hardware has not been implicated either. Microsoft has published no list of affected models, so the device's own specification is the only reliable check.
| Item | Detail |
|---|---|
| Known issue | USB audio devices might fail to start or produce no sound |
| Status | Confirmed, opened September 11, 2026 at 18:36 PT, last updated 19:10 PT |
| Scope | USB Audio Class 1.0 devices only; Windows 11 26H1, 25H2 and 24H2; no server release |
| Device Manager | This device cannot start (Code 10) |
| Other symptoms | No output, volume controls unresponsive or at zero, Sound settings unresponsive |
| Workaround | Switch the device to 2-channel mode, or use different audio hardware |
| Fix | None as of September 13, 2026; Microsoft says it is working on a resolution |
The same update's other open problems
KB5124008, released on September 8, 2026 for builds 26200.9445 on 25H2 and 26100.9445 on 24H2, is now the common factor in several separate problems. Windows Latest lists Explorer crashes, File History backup failures, Remote Desktop problems and Linux virtual machine problems alongside the audio failure. I covered the File History reports in the September 8 post, Remote Desktop Services in the September 11 post and the Explorer.exe black screen in the September 12 post.
The workaround, and what it costs
Microsoft's published workaround is that some customers have been able to restore audio by switching to 2-channel mode. Where it works, the cost is obvious and limited: you lose surround and 3D audio on that device and get stereo sound back. For a headset on a call, that is no loss at all. For a 7.1 setup or a studio interface running eight channels, it is the whole point of the hardware.
The other option in both accounts is different audio hardware, with wireless devices reported as unaffected so far. Removing KB5124008 restores sound and takes September's security fixes off the machine, which is a trade to make deliberately and to reverse as soon as a corrected update exists.
What you can do today
1. Open Device Manager and look at the audio device. If it shows This device cannot start (Code 10) on a PC that took KB5124008, you have the confirmed issue and not a broken speaker.
2. Check the device's specification before you buy anything. Microsoft says the fault is limited to USB Audio Class 1.0 devices, so a Class 2.0 interface or a wireless headset is unlikely to be affected.
3. Set the device to two channels in its advanced audio properties, and drop 8-channel or 3D audio modes. This is Microsoft's own workaround, and it has restored audio for some customers.
4. If sound has to work today and 2-channel mode does not help, use different hardware for now. That is the second workaround in Microsoft's own entry, not a sales pitch.
5. Do not reinstall drivers repeatedly or reset the machine. This is a confirmed defect in the update, and a clean install will land you on the same build with the same fault.
6. Keep the update installed if you can live without that device for a few days, because Microsoft says it is working on a resolution. Removing KB5124008 works, and it leaves the machine without September's security fixes until you put it back.
Frequently asked questions
Which audio devices are affected by KB5124008?
Microsoft says the issue is limited to USB Audio Class 1.0 devices on Windows 11 26H1, 25H2 and 24H2. Some of them work in stereo and fail only in multichannel, 8-channel or 3D audio modes, and wireless devices appear unaffected so far.
Has Microsoft fixed the USB audio failure?
No. The release health entry was Confirmed as of 19:10 PT on September 11, 2026 and Microsoft says it is working on a resolution. As of September 13, 2026 the only remedies are 2-channel mode, different hardware, or removing the update and losing September's security fixes.