Windows 11 September 2026 Update Can Break USB Audio Class 1.0 Devices

Microsoft has confirmed that the September 2026 security updates can prevent some USB Audio Class 1.0 devices from starting or producing sound. Out-of-band updates released on September 14 address the 8-channel or 3D-audio symptom only. Code 10, no audio output, volume locked at zero, and unavailable or unresponsive sound settings remain unresolved.

Issue record

• Issue ID: SPL-MIC-UAC1-001
• Status: open-confirmed — partially mitigated; Code 10/no-output symptoms remain unresolved
• Affected platform: Windows branches named in Microsoft's canonical release-health record
• Originating updates: Branch-specific September 2026 security updates
• Update date: September 8, 2026
• Affected device class: some USB Audio Class 1.0 devices
• Named device models: Unknown — Microsoft has not published a model list
• Affected-unit count: Unknown
• Fix status: resolved-pending-verification for the 8-channel/3D-audio symptom only
• Last checked: October 2, 2026

Partial mitigation released September 14

Microsoft released out-of-band updates on September 14, 2026 that address the symptom in which an otherwise working USB Audio Class 1.0 device fails in 8-channel or 3D-audio mode. Microsoft explicitly says the same update does not resolve the other documented symptoms: Code 10, no audio output, volume locked at zero, or unavailable/unresponsive sound settings.

For Windows 11 24H2/25H2, Microsoft identifies KB5129195 as the OOB update. For Windows 11 23H2 it identifies KB5129242. Branch-specific packages differ across Windows 10 and Windows Server releases. Owners should use the release-health page for their exact Windows branch rather than installing a KB named for another branch.

Microsoft's consolidated issue entry now lists these affected platforms:

• Windows 11 26H2, 26H1, 25H2, 24H2 and 23H2
• Windows 10 22H2, 21H2, Enterprise LTSC 2019 and Enterprise LTSC 2016
• Windows Server 2025, 2022, 2019, 2016, 2012 R2 and 2012

The scope remains limited to some USB Audio Class 1.0 devices. It must not be expanded to USB Audio Class 2.0, Bluetooth, HDMI, built-in audio or every USB DAC.

What Microsoft confirmed

After the September 8 security updates, an affected USB Audio Class 1.0 device may show Device Manager error “This device cannot start (Code 10),” produce no sound, leave volume controls stuck at zero, or make Windows sound settings unavailable or unresponsive. Some otherwise working devices can also fail when 8-channel or 3D-audio modes are enabled.

Microsoft's September 14 OOB updates mitigate only that multichannel symptom. The remaining symptoms are still under investigation, so this record stays open.

What owners can do

• Confirm the Windows version, installed KB and OS build in Windows Update history.
• If the only symptom is failure in 8-channel or 3D-audio mode, install the branch-appropriate OOB update and retest the exact device and mode.
• If Code 10, no audio output, zero or unresponsive volume, or unavailable sound settings remain, treat the issue as unresolved.
• Do not call the hardware fixed solely because the OOB update installed successfully.
• Where practical, test the same device on a system that has not installed the affected update, or on another supported operating system, before concluding that the audio hardware failed.
• Keep the device manufacturer's driver and firmware guidance separate from the Windows issue. Microsoft has not published a complete affected-model list or a device-firmware remedy.
• IT administrators needing an immediate workaround for Code 10, no-output, zero-volume or unavailable-settings symptoms should contact Microsoft Support for Business; Microsoft has not published a general consumer workaround for these remaining symptoms.

SoundPath Lab does not recommend broadly removing a security update. Microsoft has not published update removal as its general workaround for this audio issue, and doing so may remove security protections.

What this means for buyers

A buyer should not treat a single post-update failure as proof that a DAC, interface, headset or speaker is defective. Confirm the active USB-audio class and the exact Windows branch first. The September 14 OOB packages reduce one specific multichannel failure mode; they do not clear the wider compatibility risk.

For a new purchase, confirm whether the product supports USB Audio Class 2.0, offers a manufacturer driver, can switch USB-audio modes, or provides another input. These are resilience checks, not proof of immunity from every Windows issue.

Evidence and verification

Evidence level: E3 — platform owner acknowledged. Microsoft confirms the regression, affected branches, symptoms and partial mitigation.

SoundPath Lab has not independently reproduced the issue or verified the OOB mitigation on a named audio device. Exact affected models, device counts and the final fix date remain Unknown.

Issue timeline

• September 8, 2026: Originating security updates released for the applicable Windows branches.
• September 11, 2026: Microsoft opened the USB Audio Class 1.0 known-issue record.
• September 14, 2026: Microsoft released branch-specific OOB updates that address the 8-channel/3D-audio symptom only.
• September 20, 2026: SoundPath Lab expanded the platform scope to Microsoft's current list and changed the status to partially mitigated; Code 10, no-output, volume and sound-settings symptoms remain open.
• September 29, 2026: Microsoft added Windows 11 26H2 to the affected-platform list and kept the issue at Mitigated. The September 14 OOB update still resolves only the 8-channel/3D-audio symptom; the remaining symptoms stay open. Microsoft now directs IT administrators needing an immediate workaround to Microsoft Support for Business.

Sources

• Microsoft Windows 11 25H2 release health — September 29, 2026 update
• Microsoft KB5129195 for Windows 11 24H2/25H2
• Microsoft Windows 11 23H2 release health
• SoundPath Lab Product Issues & Limitations

Revision history

• October 2, 2026: Added Windows 11 26H2 to the affected scope from Microsoft's September 29 release-health update; recorded Microsoft Support for Business as the published immediate path for unresolved symptoms. Status remains open-confirmed and partially mitigated; no independent device retest.
• September 20, 2026: Added Microsoft's September 14 partial mitigation. The 8-channel/3D-audio symptom is resolved-pending-verification only; Code 10, no-output, volume and sound-settings symptoms remain open. Expanded platform scope only to branches named by Microsoft.
• September 13, 2026: Initial record created from Microsoft's confirmed release-health notice. Scope remains limited to some USB Audio Class 1.0 devices; model list, affected-unit count and independent reproduction are Unknown.