Windows 10 and 11 RDP clients are showing very poor graphical performance when connecting to a Windows Server 2008 R2 host. Dragging windows looks like roughly 5 FPS, and applications feel sluggish, even with only one user connected and plenty of server resources available. Linux clients connecting with Remmina are smooth, so the network and server appear generally healthy. The server only uses TCP transport and has no UDP or RemoteFX configuration. It worked normally for years, but the problem was only reported recently, possibly after a Windows client update in April 2026. Connection-quality detection and manually selecting LAN or even a slower connection type in the RDP client made no difference. How can I identify whether a recent Windows client change is responsible, and what workaround should I try?
3 Answers
Some common suggestions are disabling UDP transport and RemoteFX, but those do not apply here: Server 2008 R2 does not provide UDP transport in this setup, and RemoteFX is not enabled.
On one affected Windows machine, try disabling automatic connection-quality detection and explicitly set the RDP experience to LAN. The equivalent saved-connection settings are `connection type:i:6`, `networkautodetect:i:0`, and `bandwidthautodetect:i:0`. If those settings make no difference, test with a clean Windows installation or a client that predates the suspected April update to isolate a client-side regression.
Since Remmina uses FreeRDP, try the Windows build of FreeRDP as a comparison. If FreeRDP is smooth from the same workstation, that would strongly suggest the problem is specific to the Microsoft RDP client rather than the server or network.
I already tested both automatic detection and a manually selected LAN profile, and even tried the 56K modem setting. None of them changed the choppy behavior. I do not currently have an unpatched workstation available, so I may need to create a clean Windows 10 installation for comparison.