Windows emergency patch fixes three breaks, not every audio bug
Microsoft's September 14 out-of-band update addresses remote sessions, Linux VM folder sharing and USB multichannel audio, while another USB audio fault remains open.
The 60-second version
A September 14 Windows out-of-band release repairs three specific problems after the September security patch, but leaves one USB audio issue unresolved.
Key points
- Remote Desktop Services instability and sign-in failures are among the fixes.
- Hyper-V Linux guests regain access to Windows host folders shared through Plan9.
- Some USB Audio Class 1.0 devices regain 8-channel or 3D audio; a separate Code 10 or no-output issue remains under investigation.
Verdict. Check the support page for your Windows version and the exact symptom before calling the entire September patch fixed.
Microsoft released an out-of-band Windows update on September 14 to repair several problems introduced by its September security patch. Its Windows 11 26H1 notes name Remote Desktop Services, host-folder sharing with Hyper-V Linux guests, and USB multichannel audio. The fixes do not cover every reported USB audio failure.
What the repair covers
For 26H1, Microsoft identifies the emergency package as KB5129194, OS build 28000.2956. Its update history lists KB5129195 for 25H2 and 24H2. These numbers are version-specific: don't install or recommend the 26H1 package as though it applied to every Windows machine.
| Remote sessions | RDS instability could disrupt RDP connections or sign-in and leave related tools unresponsive. |
|---|---|
| Linux virtual machines | Host folders shared with HCS-managed Linux VMs through Plan9 could be missing or inaccessible. |
| USB multichannel | Certain USB Audio Class 1.0 devices worked in stereo but failed in 8-channel or 3D modes. |
The audio caveat
Microsoft explicitly distinguishes the multichannel fix from a separate USB Audio Class 1.0 problem: some devices still fail to start with Device Manager Code 10, play no sound, or leave volume and sound settings unresponsive. Its September 14 notes say a resolution for that issue is still in development.
What to do
If a device or managed fleet began failing after September 8, match its Windows release and symptom against Microsoft's release notes before applying the appropriate update. Administrators should test remote-session and virtual-machine workloads, and keep tracking the open USB issue rather than treating this package as a universal rollback.
The independent account from The Verge also identifies remote desktop, Hyper-V sharing and audio as the drivers of the emergency release. This is a targeted repair, not evidence that every September regression has ended.