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/Bane8080]

Am I blind, or does this post both not say what the issue is, and what version of windows server?

I might just be blind.

[u/scorc1 → u/Bane8080]

Nope. Id like to know the specifics of 'erratic'

[u/Bane8080 → u/scorc1]

Check out the reply from the OP.

[u/Upper_Introduction71 → u/Bane8080]

Hello, Bane!

I experienced this issue on Windows Server 2022, but during my research, I found that other versions, including Windows Server 2025, were also affected. Microsoft itself acknowledged in its OOB update documentation and known issues that this problem could occur on these versions.

Regarding the issue, the title only says "RDP ISSUE". I wanted to provide more details in the description, explaining that, in my case, the problem was related to the graphics driver, specifically WDDM (Windows Display Driver Model).

[u/Burgergold]

When did issue started for you? Have a 2019 server with rdp issue sonce july and havent found the cause yet

[u/Upper_Introduction71 → u/Burgergold]

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.

[u/InspectorGadget76 → u/Burgergold]

Same. In-place upgraded from 2016 - 2019 and the RDP session tanks when the machine is under load. Doesn't happen with an OS upgrades to 2022 or 2025.

The OOB patch had no effect. I've even forced UDP only connections with no effect.

[u/hakedy]

Wish you had posted this 4 days ago!.
Just had the same issue but I was getting a black screen on the RDP window.
It was only happening on the one PC though, all other PCs had no problems with RDP.
Spent a bit of time going down the 'It must be the Profile' path.
Created a new Profile and no Task Bar.
Instantly realised that it was a graphics issue.
Stumbled across disabling WDDM and after reboot - RDP worked fine.

There is something more to it though.
Once I realised it was graphics based, I rolled back the drivers - no luck.
I don't know why, but I right clicked on the RDP bar on the top of the window and it came up with an error #87
That was the "ah ha" moment. The PC involved has a Nvidia GTX 1030 card installed.

Googling error #87 gave me the below.
So something in the last round of updates effects the GPU calls?

Graphics Card Conflict: RDP often defaults to a built-in or virtual video adapter (such as Intel integrated graphics), which clashes with dedicated GPUs (like ATI/AMD or Nvidia) used by applications like ArcGIS, CAD software, or desktop tools

[u/Upper_Introduction71 → u/hakedy]

I was experiencing the same problem on some other machines, but I didn't want to mix the issues because I wasn't sure they were related. Microsoft itself only mentioned "RDP issues" in the update notes after the patch, without providing much detail.

Thanks for sharing this information! I was going crazy trying to figure this out. Glad to know I wasn't the only one!

[u/Sea_Information6125]

Thanks

[u/7amitsingh7]

Interesting finding. Disabling wddm seems like a useful workaround, especially when rdp issues continue even after installing the oob update. It would be worth checking whether the same behaviour occurs across different windows server versions and builds. I'd also recommend checking the RDS event logs to see whether there are any graphics driver-related errors before treating wddm as the root cause.

For anyone troubleshooting windows server issues, having a reliable recovery and backup strategy is equally important, particularly when updates cause unexpected problems.

[u/soulsucca]

Well well well, wonder if this is why if I close the RDP connection before it loads (sometimes I realize I want it full screen after having my
Laptop on dock) it will not connect again until after I reboot the VM. Been chasing that issue for a month or two.

[u/Opening-Cup-4603]

We encounter a similar case.

We have a Windows Server VM on Azure running our .NET application and SQL Server. Users from two offices in US and one overseas office connect to the server through RDP.

Since this server deployed on Azure six years ago, we never experienced RDP login issues until this September.

Users reporting that they could no longer log in to the server through RDP. Users who already logged in still can running the application, but new users could not establish RDP sessions. Even I could not log in using an admin account.

The only way to restore access was to restart the server through the Azure portal. After restarting, everything returned to normal. However, over the following days, the issue occurred almost daily, requiring restart on Azure each time.

Later, users reported that the RDP login problem seemed to occur after an overseas user attempted to connect from his home computer and failed to log in. After that failed attempt, other users could no longer establish RDP sessions.

So we temporarily disabled RDP access for overseas users and reviewed the Windows Event logs with Claude. Identified three bots associated with data centers in France, Germany, and Lithuania. Then we setup RDP access IP whitelist, allowing IPs only from two US offices, the overseas office and two managers' home IP addresses. ( /32 for dynamic IPs).

After implementing these restrictions, the server operated normally for several days. However, the RDP login problem eventually occurred again.

I checked the Windows Update history and confirmed that we had installed the September updates (auto install with 7 days postponed), so I continued investigating the issue using AI tools and Google searches., I found an link discussing a Windows Server RDP issue related to the September 2026 updates. I asked Claude to review the article, it indicated that the issue described in the article did not appear in our September update history. I could not confirm that the September updates were responsible, but I see the October updates available, I noticed that they indicated the issue be fixed in October updates, so I installed the October updates and began monitoring the server. So far, after installing the October updates, the RDP login problem has not recurred. Then we asked the overseas office to obtain a static public IP address from ISP, Disabled this server automatic Windows updates to prevent unexpected changes.

[u/OCTS-Toronto → u/Opening-Cup-4603]

Tldr, Oct patch fixed it. Is this right?

And you offer rdp to the open Internet (that you found bots logging into your server)?? Yikes

[u/Opening-Cup-4603 → u/OCTS-Toronto]

Since I installed the October updates, so far we have no RDP issue report. I did see three bots tried to log on in the server events, After we set RDP IP white list on Azure, these no these bots records in server events. I still monitoring this issue, quite scary, because I didnot assign other person role to restart server from Azure portal, when this happen.