Forum Discussion
USB Audio Class 1.0 Code 10/no-audio issue fully resolved in KB5127648 and Windows 11 26H2?
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; }
Microsoft acknowledged the USB Audio Class 1.0 issue associated with the September 2026 Windows update line.
KB5129195 fixed the multichannel (8-channel / 3D audio) symptom, but Microsoft documentation indicated that other USB Audio Class 1.0 symptoms remained unresolved.
Specifically:
- Device Manager Code 10 errors
- No audio output
- USB audio device initialization failures
- Unresponsive volume controls or sound settings
KB5127648 has since been released and Windows 11 26H2 is now available.
Can Microsoft clarify:
- Is the USB Audio Class 1.0 issue now fully resolved?
- If resolved, which KB is considered the final fix?
- Does Windows 11 26H2 include the complete fix?
- When will the Windows Release Health entry move from Mitigated to Resolved?
We are currently delaying approval of Windows 11 cumulative updates because the available documentation remains unclear regarding the remaining Code 10 / no-audio symptoms.
We have already had to disable automatic approval of Windows 11 updates in our enterprise patch-management workflow pending clarification.
Ridiculous that Microsoft continues to fail at QA
1 Reply
Your concern is specifically the remaining Code 10/no-audio failures, rather than the multichannel symptom already fixed. Microsoft's documentation still makes that distinction: KB5129195 and later updates address the 8-channel/3D-audio behavior, while the other symptoms remain under investigation.
The KB5127648 article still lists USB Audio Class 1.0 startup failures, no output and unresponsive controls as a partially resolved known issue. Windows Release Health continues to mark it Mitigated and includes Windows 11 26H2 among affected platforms. Therefore, those documents do not establish KB5127648 or 26H2 as a complete fix, and they provide no final-fix KB or date for changing the status to Resolved.
For approval, pilot the affected device models on the target build and record hardware IDs, driver versions and symptoms. Microsoft directs IT administrators needing a workaround for unresolved symptoms to Support for Business. Use that case for deployment-specific guidance rather than assuming the feature upgrade resolves it.
