Windows 11 continues to grapple with challenges following its recent updates, particularly concerning audio functionality on certain PCs. The emergency update, KB5129195, released on September 14, aimed to rectify issues stemming from the September Patch Tuesday update (KB5124008) but has inadvertently introduced new complications.
Initially, the September update disrupted Remote Desktop Protocol (RDP) connections and rendered host folder shares inaccessible in Linux virtual machines, impacting applications like Claude Cowork. Users faced frustrating scenarios where RDP connections would drop unexpectedly or become stuck during configuration. Additionally, Claude Cowork lost its ability to interact with local files, despite prior permissions being granted.
Microsoft acknowledged these concerns, clarifying that the problems were linked to the recent Windows 11 update. In their updated documentation, the company noted:
“Applications or sandbox environments that depend on these shared folders might display an error indicating that no Plan9 drive shares were mounted. Claude Cowork and the Windows Subsystem for Linux (WSL) are two of the applications affected by this issue. Standard Hyper-V virtual machines that do not use the Plan9 feature are not affected by this issue.”
Fortunately, the emergency update KB5129195 addressed these RDP and Claude Cowork issues, while also incorporating changes from previous updates. This cumulative patch advances Windows 11 25H2 to Build 26200.9457 and 24H2 to Build 26100.9457. Users can verify their build version through Settings > System > About.
However, the emergency update has not been without its own set of problems. Reports indicate that audio functionality remains compromised on some devices, with certain enterprise systems experiencing disruptions in secure trust relationships with their domains, complicating login processes. For consumers, this could mean devices may operate without any audio output, irrespective of the updates applied.
While Microsoft has not disclosed the number of affected users, it has updated its support documentation to reflect the ongoing audio issues. The emergency update has been linked to error messages such as “This device cannot start (Code 10)” in Device Manager, alongside a persistent volume issue where controls become unresponsive. Microsoft’s investigation suggests that only USB audio devices are affected, yet user reports indicate a broader impact.
As the situation stands, the timeline for resolving these audio issues remains uncertain. Microsoft has committed to investigating the root cause and will provide updates as they become available. Users who have not yet experienced audio problems should remain vigilant, as the gradual rollout of Windows 11 features could mean that issues may arise in the near future.
Windows 11’s emergency update doesn’t list a fix for AMD GPU errors
In addition to audio concerns, reports have surfaced regarding GPU issues on AMD systems following the September update. Users have encountered driver timeouts, black screens, and system freezes, even outside of gaming contexts. Affected models include a range of Radeon GPUs, such as the RX 6600, RX 7700 XT, RX 7800 XT, RX 7900 GRE, RX 7900 XTX, and RX 9070 XT, indicating that the problem is not isolated to a single model.
Some users have attempted to resolve these issues by reverting to older GPU drivers, but this has not proven effective. Interestingly, uninstalling the September update appears to alleviate the problems, casting suspicion on the Windows Update itself as a potential culprit. Unfortunately, the emergency update KB5129195 does not address these GPU errors, leaving users seeking solutions.
