Microsoft Patches RDS and Hyper-V Issues While AMD GPU Crashes Persist

Microsoft has released an emergency out-of-band update for Windows 11 to address several critical regressions introduced during its September 8 Patch Tuesday deployment. The intervention, issued on September 14, 2026, aims to stabilize systems following a massive security release that addressed a record-breaking 974 vulnerabilities across the Microsoft ecosystem.

The emergency patches focus on restoring core functionality for remote workers and developers. High on the priority list is a fix for Remote Desktop Services (RDS), which suffered from widespread instability that caused connection drops and sign-in failures for many users after the initial September update.

Abstract visualization of virtual machine connectivity and network nodes.
The emergency fix restores critical folder sharing capabilities for developers using environments.

Developers using Hyper-V-based Linux virtual machines also receive a significant fix. A bug in the initial patch cycle broke host folder sharing via the Plan9 protocol. This emergency release restores the ability for virtual machines to access these shared directories.

For users on specific Windows 11 builds, the updates are identified by the following Knowledge Base (KB) numbers:

  • KB5129194: For Windows 11 version 26H1.
  • KB5129195: For Windows 11 versions 24H2 and 25H2.

For enterprise users on versions 24H2 or 25H2, Microsoft is utilizing “hotpatching” technology where eligible, which may allow the update to be applied without requiring a full system restart.

The update also provides a restoration of audio functionality. It specifically addresses a bug that disabled 8-channel and 3D audio modes for USB Audio Class 1.0 devices.

Despite the emergency intervention, several high-profile issues remain outstanding. Reports indicate that users with AMD Radeon GPUs are still facing system freezes and driver timeouts that were not addressed in this out-of-band release. Users experiencing these specific hardware conflicts may need to wait for a subsequent update or a driver-side fix from AMD.

More From Category

More Stories Today