How can I stop Remote Desktop from freezing on Windows 11 23H2?

Remote Desktop keeps freezing randomly on my Windows 11 23H2 machine, especially during longer sessions or when I switch between apps. I’ve already tried updating drivers and checking my network, but the issue still happens. Can anyone share specific settings tweaks, patches, or known workarounds that actually fix this freezing problem on Windows 11 23H2?

Not all RDP freezes are the same, so matching the fix to the symptom saves a ton of time.

Screen frozen but stuff still happens in the background? That’s graphics/encoding. Whole session just dies? Transport or network. Freezes when you copy/paste? Almost always rdpclip.exe. Drops after sitting idle? Keepalive isn’t configured.


Things that actually worked, in order of impact:

1. Force TCP only — biggest win by far. RDP defaults to UDP+TCP and UDP gets janky fast on any packet loss or VPN weirdness. Kill UDP on the client:

HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ClientfClientDisableUDP = 1

Or via GPO. One environment with flaky WAN links, about 70% of freeze tickets disappeared after pushing this.

2. Disable persistent bitmap caching — low risk, quick to test. Uncheck it in mstsc’s Experience tab or add bitmapcachepersistenable:i:0 to your RDP file.

3. Idle drops? Set a keepalive around 60 seconds via GPO on the RD Session Host. Also check your firewall/VPN session timeouts on port 3389.

4. Copy/paste freezes? Test with redirectclipboard:i:0 in your RDP file. If that stabilizes things, rdpclip is your guy. You can also just kill and restart it: taskkill /f /im rdpclip.exe && rdpclip.exe

5. Wi-Fi bad, ethernet fine? Stop blaming RDP and look at NIC drivers, offload features (RSS, checksum offload), MTU, and VPN rekey timers. Had one site where a specific AP firmware was dropping UDP packets — forcing TCP only was the workaround until they updated.


TCP-only + 60s keepalive + updated NIC drivers covers like 80% of cases in my experience.

If you want a more traditional, step-by-step writeup, this one lines up with a lot of what I wrote here and goes into the Windows 11 23H2 angle:

5 Likes

Since Mike covered UDP and bitmap cache already, here’s what else I’d check:

Kill hardware GPU scheduling on your client — Settings > Display > Graphics > Change default graphics settings. This thing causes way more RDP stalls on 23H2 than it should, especially with mixed GPU setups. Reboot after.

Simplify mstsc rendering — Drop colors to 16/24bit, uncheck Desktop composition and Font smoothing in the Experience tab. Also find mstsc.exe in Graphics settings and set it to Power saving.

Fix power plan on the remote machine — High performance or at minimum set processor floor to 50-80%. If the host is parking CPUs aggressively you’ll feel it as random stutters. Also disable PCI Express Link State Power Management in advanced power settings.

If the remote is a Windows 11 laptop, disable Dynamic Refresh Rate. RDP encoder doesn’t play nice with it jumping around.

Clean boot the remote — msconfig > selective startup, kill all non-Microsoft services and startup items. If freezes stop, something like GeForce overlay, FancyZones, or a clipboard manager is hooking into rendering and locking the session.

Test without AV real-time protection — some EDR tools inspect RDP traffic and cause exactly these kinds of pauses. If disabling it helps, add exclusions for mstsc.exe rather than leaving it off.

Also make sure both machines are on the latest 23H2 cumulative update — Microsoft has quietly fixed a few RDP rendering issues in recent rollups.


Adding to what’s been said, a few more things nobody mentioned yet:

Kill audio and printer redirection first — seriously underrated. Local Resources tab in mstsc, set audio to “Do not play.” Printer redirection is even worse, Office apps can hang the whole session for seconds just enumerating redirected printers. Disable both temporarily and see what happens.

On the remote host, disable “Use hardware graphics adapters for all RDS sessions” in gpedit — Computer Config > Admin Templates > RDS > Session Host > Remote Session Environment. Better than nuking GPU features on the client side.

Check Event Viewer before randomly flipping settings — TerminalServices-ClientActiveXCore on the client, RDP-Graphics on the host. If you see repeated reconnect events you didn’t notice, your “freeze” might just be the client hiding short drops. That’s a network/MTU problem, not Windows.

Fast Startup — disable it on the client machine. It can preserve broken driver states across reboots, which is exactly why “I already restarted” sometimes doesn’t fix anything.

Try a fresh local user profile on the remote — if a new account is smooth but yours isn’t, you’re chasing profile corruption or a bad logon script, not RDP itself.

Skip the generic tweaks already covered by @sognonotturno, @sternenwanderer and @mikeappsreviewer; here are angles they mostly did not touch that often fix “freezes when I multitask for a long time” on Windows 11 23H2.


Check Task Scheduler on the remote for OEM updaters, OneDrive, or backup clients that spike every few minutes — that “random freeze during long sessions” is often just a background task slamming disk or CPU, which RDP shows as a hang. Also try a fresh local user profile on the remote before chasing anything else, because 23H2 is noticeably less forgiving with bloated or corrupted profiles during app switching.