Microsoft confirms September updates break USB audio on Windows 11
Updates KB5124008 and KB5124012 trigger 'Code 10' errors for legacy USB Audio Class 1.0 devices.
Microsoft has confirmed that its September 8, 2026, security updates are causing total audio failure for a subset of Windows 11 users. The bug creates a critical conflict with specific hardware, leaving users without sound output or functional volume controls.
The issue is tied to cumulative updates KB5124008 and KB5124012. Affected users report a "Code 10" error appearing in the Device Manager, a signal that the system cannot start the hardware device. According to Microsoft's release health documentation, the failure is strictly limited to USB Audio Class 1.0 devices, which typically include older or generic USB digital-to-analog converters (DACs) and headsets. The bug impacts Windows 11 versions 24H2, 25H2, and 26H1, though Windows Server remains unaffected.
A problematic patch cycle
This audio failure is part of a wider, unstable September Patch Tuesday cycle. While the updates were intended to secure the OS and resolve existing bugs—including a fix for Remote Desktop audio redirection—they introduced new regressions. Specifically, KB5124008 has been linked to failures in Hyper-V environments, where HCS-managed virtual machines encounter problems sharing host folders with Linux VMs using the Plan9 protocol.
The security trade-off
This bug disrupts essential hardware functionality for users relying on legacy or generic USB audio equipment. Because the failure is embedded within critical security updates, users are placed in a difficult position: they must choose between maintaining the security posture of their system or uninstalling the updates to restore basic audio functionality. For professional users relying on external DACs for monitoring or communication, the loss of audio output represents a significant productivity blocker.
What to watch
Microsoft has not yet provided a timeline for a formal patch to resolve the USB Audio Class 1.0 conflict. Users currently experiencing the Code 10 error will need to monitor the Windows Release Health dashboard for a revised update. It remains to be seen if Microsoft will issue a targeted hotfix for the audio driver or if a full rollback of the affected KB packages will be the only immediate solution for those with legacy hardware.