Windows 11 KB5124008: Audio and RDP

The short answer: If USB audio or Remote Desktop stopped working after the September Windows 11 update, first run winver to find your build number, then check Windows Update for the latest cumulative update. KB5129195 fixes issues involving Remote Desktop Services, Plan9 sharing, and multichannel audio on some USB Audio Class 1.0 devices. However, it does not resolve every audio failure, and the timing alone does not prove that KB5124008 caused the fault.

What Microsoft released on September 14, 2026

On September 14, 2026, Microsoft announced and released the out-of-band cumulative update KB5129195 for Windows 11 24H2 and 25H2. According to Microsoft’s release notes for KB5129195, it addressed three distinct groups of issues:

• instability in Remote Desktop Services,
• inaccessible host folders in Linux virtual machines using Plan9,
• failures in multichannel modes on certain USB Audio Class 1.0 devices.

Windows Central described it as an emergency fix released after the September Patch Tuesday. However, this does not mean that a single previous update caused all three issues.

Microsoft links the fixed Remote Desktop Services issue to KB5122880. Update KB5124008 is associated with other September problems, including some USB audio issues. If RDP and audio stopped working at the same time, you cannot identify a single shared cause without checking the update history.

KB5124008 and KB5129195 are not the same

KB5129195 updates the system to build 26100.9457 on Windows 11 24H2 or 26200.9457 on Windows 11 25H2. Because it is a cumulative update, its fixes may also be included in a later package. Do not check only for the exact KB5129195 label; check the current system build as well.

First, establish the computer’s actual state

Do not uninstall a security update blindly. First, record the system’s state before making any further changes:

1. Press Win + R, type winver, and record the version and build number.
2. Open Settings → Windows Update → Update history.
3. Look for KB5124008, KB5129195, and any newer cumulative updates.
4. Check for updates in Windows Update.
5. Install the offered cumulative package and restart the computer.
6. After restarting, test the same audio output, RDP connection, or shared folder that you used before the update.

If Windows Update does not offer the package, do not repeatedly remove it or install it manually without checking your system version. For a separate troubleshooting guide, see Windows Update cannot be installed.

On a business computer, also note the USB audio device model, the port or docking station being used, the VPN, and the direction of the RDP connection. Without this information, a Windows fault can easily be confused with a peripheral, driver, or network problem.

When USB audio stops working after an update

KB5129195 fixed a specific situation in which certain USB Audio Class 1.0 devices worked in stereo mode but failed when using eight-channel or 3D audio. It is not a universal fix for every device that stopped producing sound after the update.

Microsoft also listed other symptoms on the same page:

• the device fails to start and Device Manager shows Code 10,
• the USB audio output disappears from the system,
• the volume remains stuck at zero,
• the sound settings page stops responding.

Those cases were not resolved by the same fix. After installing the latest cumulative update, therefore check:

1. whether the device is selected under Settings → System → Sound → Output;
2. whether Device Manager shows Code 10;
3. whether the device works without a USB hub or docking station;
4. whether its behaviour changes when connected to another USB port;
5. whether the built-in speakers or another audio output work;
6. whether the same USB device works on another computer.

If only one output is silent, continue with the more detailed guide No sound in Windows 11. If the device disappears only when connected to one socket, the port may be at fault; follow the checks in USB port not working or device not recognised.

When Remote Desktop does not work

KB5129195 addresses instability in Remote Desktop Services that could cause connection failures, sign-in errors, or a server to freeze when Remote Desktop was being configured. According to Microsoft, MMC, RDS Licensing Diagnoser, File Explorer, or the Windows Update page could also stop responding in connection with this issue.

Check the update primarily on the computer that accepts the remote connection. Updating the laptop from which you connect may not change the state of the remote machine.

Before blaming Windows Update, also check:

• whether the target computer is switched on and reachable over the network;
• whether a connection from another client works;
• whether the problem occurs both on the same local network and over a VPN;
• whether Remote Desktop fails for every user or only for one account;
• whether you can access the computer locally before restarting it or uninstalling the update.

If RDP is the only way to reach a business application or data, do not perform repeated remote restarts or uninstall the update without having an alternative access method ready.

When folders disappear from a Linux virtual machine

The Plan9 fix does not apply to every type of network share. Microsoft describes a specific case involving applications that use Linux virtual machines managed through HCS. A folder shared from the Windows host through the Plan9 protocol either did not appear in the Linux system or could not be accessed.

If an ordinary network drive, SMB share, NAS, or files synchronised through OneDrive have disappeared, the Plan9 fix does not explain the problem by itself. For a NAS, first check its network availability using the guide Home NAS cannot be found on the network.

When File History stops backing up

On the same page, Microsoft describes another issue linked directly to KB5124008: File History (Control Panel → System and Security → File History) may stop creating backups. The system displays “Reconnect your drive” even though the backup drive is connected, the date of the most recent backup does not change, and previous versions of files are missing.

According to Microsoft, this issue is resolved in updates released from September 22, 2026 onwards, such as KB5124010. Microsoft lists it as a preview update, so it may not install automatically—look for it among the optional updates in Windows Update, or wait for the next regular cumulative update. If you use File History, check after installing a newer update that the date of the most recent backup has begun advancing again. Until then, do not consider the backup current.

When to look for another cause

Further diagnosis is appropriate if the latest cumulative update is installed, the computer has been restarted, and the original problem persists.

The update is unlikely to be the only explanation if:

• USB audio fails in only one physical port;
• the same device does not work on another computer either;
• RDP fails only from one network or one client;
• the computer also freezes or loses several USB devices;
• the sharing problem does not involve Plan9 and an HCS-managed Linux machine.

In this situation, you need to distinguish a Windows fault from a problem with the driver, USB port, audio device, or network configuration. If you would rather not attempt a risky change yourself, send us the build number, update identifier, and an exact description of the symptoms before bringing in the computer. We can then continue from the checks you have already performed instead of blindly uninstalling updates.

Key takeaways

KB5129195 is a targeted cumulative fix, not confirmation that KB5124008 caused every audio, RDP, or sharing failure. What matters is the build number, the updates actually installed, and the exact type of problem.

First, update Windows to the latest available build and retest the original symptom. Only if the problem remains does it make sense to continue by checking the device, port, driver, or network.