It's a classic scenario for any administrator: You are connected to your Windows Server via Remote Desktop, and suddenly, the screen freezes. You assume the connection dropped.
But it hasn't. If you disconnect and reconnect, you realize that your "blind" clicks actually registered. The session was alive, but the display was frozen.
This is not a bug; it's a protocol issue. And yes, there is a permanent fix.
Modern Windows versions (Server 2019/2022, Windows 10/11) prioritize UDP (User Datagram Protocol) for RDP connections. UDP is fast and great for streaming, but it has zero tolerance for packet loss.
If your internet connection has even a micro-drop (common in Wi-Fi or long-distance routing), the UDP stream breaks, freezing your screen. Meanwhile, your mouse clicks (sent via TCP) keep working.
The solution? Force RDP to use the rock-solid TCP Protocol.
This is the best method as it applies to all users connecting to the server.
gpedit.msc
Set "Select RDP Transport Protocols" to "Use only TCP"
If you don't want to navigate menus, or if you are using Windows Server Core, use this command to apply the same setting instantly.
(Value 1 means TCP Only. Value 0 is Dual UDP/TCP).
If you don't have Admin rights on the server, you can force your own computer to disable UDP for RDP sessions.
gpedit.msc.For these changes to take full effect, a server reboot is recommended. Alternatively, open CMD as Admin and run gpupdate /force.
Your RDP connection might feel slightly less "smooth" on animations, but it will be rock-solid and will never freeze on connection hiccups again.
Even TCP can't fix a bad network. Switch to ErkmenHost Dedicated Servers premium Anti-DDoS network. Low latency, high uptime, and no packet loss.