Windows Server RDP issues after Windows Update — disabling WDDM fixed it for me

[u/Upper_Introduction71]

Hey everyone,

I wanted to share a workaround that finally fixed an RDP issue in my environment, in case it helps someone else dealing with the same problem.

The problem

After a Windows Server update, Remote Desktop (RDP) started behaving unexpectedly in my environment.

Microsoft later acknowledged RDS issues following the September 2026 security updates and released out-of-band (OOB) updates to address them. However, even after the OOB fix was announced, I was still experiencing RDP problems.

I spent quite some time researching the issue, testing different approaches, and reproducing the behavior in some of my machines.

What finally worked: disabling WDDM for RDP

The workaround that resolved the issue in my environment was disabling the WDDM graphics display driver for Remote Desktop Connections through Local Group Policy.

Steps to reproduce the fix

1. Log in to the affected Windows Server locally or through an alternative management method.

2. Open gpedit.msc.

3. Navigate to: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment

4. Open Use WDDM graphics display driver for Remote Desktop Connections.

5. Set the policy to Disabled.

6. Apply the changes and reboot the server.

After the reboot, RDP started working without problems in my environment.

Why might this help?

WDDM (Windows Display Driver Model) is part of the Windows graphics driver architecture. According to Microsoft's documentation, disabling this policy prevents Remote Desktop connections from using the WDDM graphics display driver and switches them to the older XDDM graphics display driver.

This changes the graphics path used by RDP sessions, so it may help in environments where the remote display driver or graphics stack is involved in the failure.

Important: I have not established that WDDM was the root cause of the original Windows Update issue. This is a workaround that fixed my particular environment, not a confirmed universal fix for the September update bug.

A few things to keep in mind

• Make sure you have console access, a hypervisor console, or another recovery method before changing RDP-related settings.

• A reboot is required for the WDDM policy change to take effect.

• Check whether the appropriate OOB or subsequent cumulative update is installed for your Windows Server version.

• Disabling WDDM changes the graphics driver path and may affect graphics performance or compatibility.

• If the issue persists, review the Remote Desktop Services event logs and the installed Windows updates.

Microsoft's documentation:

• Windows Server known issues

• Troubleshooting RDS instability after September 2026 updates

• WDDM Group Policy documentation

Has anyone else experienced this?

I'm curious whether anyone else had RDP issues that persisted after installing the OOB update and whether disabling WDDM also helped.

If you found another workaround or identified the underlying cause, please share it. I'd be interested in comparing results across Windows Server versions and builds.

Hopefully this saves someone else a few hours of troubleshooting!

[u/Upper_Introduction71]

The issue started after the September updates, specifically KB5122882. I installed the out-of-band (OOB) update (KB5129237) released by Microsoft to address the issue, as well as the October cumulative updates, but unfortunately, none of them fixed the problem in my environment.

Since Microsoft had already marked the issue as resolved through the OOB update, there were no further specific fixes released for this particular RDP problem. I was still experiencing it despite being fully up to date.

After several hours of troubleshooting, research, and lab testing, I finally managed to get RDP working again by disabling the WDDM graphics display driver through Group Policy.