The 14 September out-of-band update, KB5129195, repairs that multichannel-mode failure. As of 28 September, Microsoft still lists the Code 10, silent-output and volume/settings problems as unresolved. Installing the patch and still hearing nothing can therefore be consistent with the published status. It does not, by itself, prove the installation failed.
The difference is the symptom, not just the update date
Microsoft's Windows release-health entry calls the issue “Mitigated,” not resolved. Its resolution paragraph singles out the last symptom in its list: devices that function in standard stereo but fail in 8-channel or 3D modes. Some users had restored output in that situation by switching to two-channel mode before the patch; KB5129195 addresses that specific behavior.
A device that cannot start at all presents a different case. Microsoft says affected USB Audio Class 1.0 devices may display “This device cannot start (Code 10)” in Device Manager, produce no output, leave the volume at zero, or make Sound settings unavailable. The KB5129195 notes explicitly warn that other audio symptoms remain unresolved. A generic headline saying the update “fixes USB audio” leaves out the part a silent-device owner needs to know.
The notice is also narrower than “all USB audio.” It identifies some Class 1.0 devices. The shape of a USB plug, or the fact that a headset contains a USB connector, cannot establish that this known issue caused a particular failure. The timing and exact symptom make the notice worth checking; they are not a hardware diagnosis.
Check the KB and build that are on your PC
In Windows 11, open Settings → Windows Update → Update history and check which updates actually installed. Type winver into Windows search to see the version and OS build. Microsoft's release notes assign KB5129195 to build 26200.9457 on 25H2 and 26100.9457 on 24H2. These are the two Windows 11 releases covered by the KB numbers in this article. Microsoft explains where to view update history; its version-check instructions describe winver.
- KB5124008 present; stereo works but surround/3D fails: install the latest available Windows update for your version, restart if prompted, then retest the same mode. Microsoft says the 14 September fix and later cumulative updates address this symptom.
- KB5129195 present; device shows Code 10 or produces no sound: do not interpret the installed patch as a promise of restored output. These symptoms are still open in Microsoft's release-health notice. Record the device name and exact error before changing more settings.
- Different version or no matching September update: do not copy the 24H2/25H2 KB number onto another release. Check that version's own release-health and update-history page before connecting the failure to this incident.
A later cumulative update may contain the earlier repair even if KB5129195 is not shown as a separate recent installation. That is why the version, build and symptom belong in the same check. An installed number alone cannot tell you which of Microsoft's two audio outcomes applies.
What to do with a still-silent device
For a managed work PC, give the help desk four facts: Windows version and build, the installed September KB, the USB device name, and whether ordinary stereo works or the device shows Code 10/no output. That description is more actionable than “the update broke my headphones.” Microsoft directs IT administrators who need an immediate workaround for the still-open symptoms to Microsoft Support for Business. It has not published a general repair in this release-health entry.
For a personal PC, keep the same distinction in mind before replacing hardware or repeatedly reinstalling drivers. If the fault began before 8 September, the system never received the update, or the device is outside the documented class, this notice has not established the cause. There may be another explanation. Conversely, a machine on KB5129195 can remain silent for a reason Microsoft has already acknowledged but not yet fixed.
This is one example of why the installed build matters more than a broad version label. Our Windows 11 26H2 servicing analysis explains a different release boundary; here the relevant boundary is the exact September 24H2/25H2 cumulative update and the specific symptom it repairs. The status above was checked on 28 September 2026 and should be revisited when Microsoft updates the known-issue record.
