Description: Microsoft's confirmed September 2026 USB Audio Class 1.0 bug can cause silence, Device Manager Code 10, and stuck volume controls. Check affected Windows 11 versions, partial fixes, and safe next steps.
If a USB headset, DAC, or other audio device went silent after the September 2026 Windows updates, check whether it uses USB Audio Class 1.0. Microsoft has confirmed that some devices using that standard may fail to start with Device Manager Code 10, produce no sound, or have frozen volume controls. The September 14 update fixed a specific multichannel problem, but other symptoms remain under investigation as of October 16.[1][2]
Identify the update before changing anything
Press Win + R, type winver, and note whether you have Windows 11 24H2, 25H2, or 26H2. Open Settings → Windows Update → Update history. For 24H2 and 25H2, Microsoft's release-health record traces the issue to the September 8 KB5124008 security update. The October 13 KB5127648 release still lists the USB audio issue among known problems.[1][2]
| What you see | Check safely | What to do next |
|---|---|---|
| No sound | Settings → System → Sound: confirm the output device and volume | Select the correct output and reconnect the device |
| “This device cannot start (Code 10)” | Device Manager → audio device → Properties → Device status | Record the device model, Windows version, and update date |
| Volume stuck at zero or Sound settings unresponsive | Test another available output device | Check the vendor's guidance; avoid deleting drivers blindly |
| Only 8-channel or 3D audio fails | If supported, test ordinary 2-channel stereo | Check updates from September 14 onward; Microsoft says this specific symptom was fixed |
Is every USB headset affected?
No. Microsoft limits this issue to USB Audio Class 1.0 devices. Check the manufacturer's specifications for your exact model; “USB audio” on a box is not enough to identify the class. Code 10 can also occur for unrelated reasons, so the timing of an update is evidence to investigate, not proof of causation.[1]
What has Microsoft fixed?
The out-of-band KB5129195 update on September 14 addressed failures involving 8-channel or 3D audio modes. It did not clear all reports of devices failing to start, silence, or unusable volume controls. Microsoft's October 13 release notes still describe those remaining symptoms and direct business IT administrators needing urgent help to Microsoft Support for Business.[2][3]
Try the reversible checks first: select the right output, reconnect the device, and restart Windows when convenient. Keep a note of any Code 10 message. Do not start with a factory reset, forced driver removal, or uninstalling security updates. Rolling back updates can remove security fixes; managed PCs should go through their IT team.
Bottom line
A silent USB device after the update is a reason to check the audio class, error code, and update history before replacing hardware. Installing the October update does not guarantee that every Class 1.0 symptom is gone. The useful first move is diagnosis, not pressing the volume-up key until it begs for mercy.
Sources (checked October 16, 2026): [1] Microsoft Windows 11 24H2 release health https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24h2/ ; [2] Microsoft KB5127648 (October 13) https://support.microsoft.com/en-us/servicing/os/windows-11/2026/10/kb5127648-windows-11-24h2-25h2-26h2-security-update ; [3] Microsoft KB5129195 (September 14) https://support.microsoft.com/en-us/servicing/os/windows-11/2026/09/kb5129195-windows-11-24h2-25h2-security-update
