Windows emergency update after September patch: USB audio and more
Microsoft's Sept 14, 2026 out-of-band updates fix multichannel USB audio, Remote Desktop instability, and Hyper-V Plan9 sharing after the September security patch. Check Windows Update.
Michael Narehood
If last week’s September security update made your Windows PC weird, check for updates again. Microsoft shipped out-of-band (emergency) packages around September 14, 2026 to fix problems introduced by the September 2026 Security Update. This is the follow-up to our September Patch Tuesday home guide.
The home-relevant headline is USB audio. Some USB Audio Class 1.0 devices kept working in ordinary stereo, then failed when you switched into multichannel modes such as 8-channel or 3D audio. Microsoft lists that case as fixed in the OOB packages. Other USB audio failures (Code 10, total silence, stuck volume) are not fully cleared yet. Install anyway if Windows offers the update, then verify what still breaks.
What the emergency packages fix
Coverage from BleepingComputer and Pureinfotech, plus Microsoft’s own KB pages, describe three buckets that matter for people at home:
- Multichannel USB Audio Class 1.0: devices that were fine in stereo but failed in 8-channel / 3D-style modes. Fixed in the OOB notes for the current Windows 11 packages (KB5129195).
- Remote Desktop Services instability after the September security update: failed connections, sign-in trouble, or related tools hanging. Most home users never notice this. If you Remote Desktop into another PC at home (or into a relative’s machine), this is why the OOB exists.
- Hyper-V Linux Plan9 folder sharing: shared host folders missing or inaccessible inside some Linux VMs. Mentioning this for the small set of home lab / hobby VM users. Not an enterprise fleet story.
Microsoft’s KB5129195 page also notes additional security work (including protections tied to a User-Mode Power Service elevation issue). Treat the OOB as both a bugfix and a cumulative package that still wants a reboot.
Which KB you want (by Windows version)
Confirm your version with Settings → System → About, or run winver, then match the package:
| Windows version | Out-of-band KB | Build after install | Notes |
|---|---|---|---|
| Windows 11 26H1 | KB5129194 | 28000.2956 | Offered through Windows Update |
| Windows 11 25H2 | KB5129195 | 26200.9457 | Cumulative OOB for 25H2 / 24H2 |
| Windows 11 24H2 | KB5129195 | 26100.9457 | Same KB as 25H2, different build |
| Windows 11 23H2 | KB5129242 | 22631.7584 | Reported as an optional / non-security packaging in some write-ups; still install it if you are hitting the bugs |
| Windows 10 22H2 (and related ESU / LTSC paths covered by the package) | KB5129236 | see KB | Relevant if you are still on home ESU Windows 10 |
You do not need every row. You need the one that matches the PC in front of you.
Remaining USB audio problems (do not panic-uninstall)
Microsoft still documents a known issue after the September 8 security update: some USB Audio Class 1.0 devices may fail to start, show Device Manager Code 10, produce no audio, leave volume stuck at zero, or make Sound settings unresponsive. The multichannel fix in the OOB does not claim to clear that whole list. Microsoft says it is still working on the rest (KB5129195 known issues; also summarized by BleepingComputer).
Practical split:
- Stereo works, multichannel / 3D / 8-channel fails: the OOB is aimed at you. Install, reboot, retest that mode.
- Code 10 / total silence / dead volume slider: install the OOB anyway if offered, then check Device Manager. If it is still broken, you are in the known-issue bucket, not a reason to rip out September’s security fixes. Watch Microsoft’s release notes for the next audio fix. Temporary workarounds people have used include forcing a simple 2-channel / stereo configuration when the device allows it.
Install steps
- Open Settings → Windows Update.
- Click Check for updates.
- Install the out-of-band cumulative update if Windows offers it (names will look like KB5129195 / KB5129194 / KB5129242 / KB5129236 depending on version).
- Restart when asked. Leaving the reboot for later leaves the broken bits running.
- Open Windows Update again and confirm required updates are clear.
- Confirm the build: press Win + R, type
winver, and match the table above.
If you are on 23H2 and the package sits under optional updates, open the optional list and take KB5129242 when you are affected.
Quick checks after reboot
- Play audio in stereo, then (if you use them) retest multichannel / spatial / 8-channel modes on the same USB device.
- If you Remote Desktop to another home PC, try a short session.
- If you share folders into a Hyper-V Linux VM via Plan9, confirm the share appears again.
- If Device Manager still shows Code 10 on a USB audio device, note it, keep the security updates installed, and wait for Microsoft’s remaining audio fix rather than uninstalling September’s patch set.
Bottom line
September’s security update needed an emergency follow-up. For a home PC, prioritize the OOB that matches your version (KB5129194, KB5129195, KB5129242, or KB5129236), reboot, and confirm with winver. Expect multichannel USB audio to improve. Do not expect every Code 10 / silent-USB case to vanish yet. If you skipped the original September patch day checklist, start with the Patch Tuesday home article, then take this OOB.
Sources: Microsoft KB5129195, KB5129194, KB5129242, KB5129236, BleepingComputer, Pureinfotech.
Image: Microsoft Windows marketing imagery (from Microsoft Windows 11 / Meet Windows materials).
