How to Fix Remote Desktop Stuck on “Please Wait” in Windows 11

Below, we go through every fix in order, starting with the fast ones you can do from your own PC and ending with the host-side changes that stop the freeze from coming back.

Why does RDP get stuck on “Please wait”?

After you enter your credentials, the remote Windows PC has to do several things before showing the desktop: check the network quality, start the Remote Desktop services for your session, load your user profile and apply Group Policy. If any of those steps hangs, you see “Please wait” forever.

The usual causes are:

• RDP’s network detection (connect-time and continuous detection) hanging during login.
• Problems with RDP’s UDP transport between your PC and the host.
• A disconnected or frozen old session for the same user on the host.
• The User Profile Service or Group Policy processing taking too long.
• A pending or problematic Windows update on the host.
• Display, scaling or multi-monitor settings in the client.

Fix 1: Wait, then cancel and reconnect

It sounds too simple, but give it two or three minutes the first time. Right after updates, the host may be finishing configuration work in the background. If nothing changes, close the RDP window and connect again. Very often, the second attempt goes straight to the desktop.

Fix 2: Sign out the stuck session

If an old session for your account is frozen on the host, every new connection tries to reattach to it and hangs. You can clear it from another PC on the same network (with admin rights on the host) using Command Prompt:

query session /server:HOSTNAME
logoff SESSIONID /server:HOSTNAME

Replace HOSTNAME with the remote PC’s name or IP, and SESSIONID with the ID shown for your user. Alternatively, sign in to the host with a different user account, open Task Manager, go to the Users tab, and sign out the stuck user.

If nothing else works, restart the host remotely:

shutdown /r /m \\HOSTNAME /t 0

Fix 3: Change the connection speed in the client

On your local PC, open Remote Desktop Connection (mstsc), click Show Options, and go to the Experience tab. Change the connection speed from “Detect connection quality automatically” to LAN (10 Mbps or higher). This skips the automatic quality check that often triggers the freeze, and it usually gets you past “Please wait” so you can apply the permanent fixes below.

While you’re on the Experience tab, also uncheck “Persistent bitmap caching”. A corrupted bitmap cache can cause freezes and black screens. You can also clear the cache by deleting the files in %LOCALAPPDATA%\Microsoft\Terminal Server Client\Cache while RDP is closed.

Fix 4: Turn off UDP on the client (force TCP)

By default, RDP uses UDP as well as TCP. When UDP misbehaves on your network, VPN or router, sessions can hang at login or freeze later. Forcing TCP only is one of the most reliable fixes; it’s also the workaround that was widely used when Windows 11 22H2 caused RDP freezes.

Using Group Policy (Windows 11 Pro/Enterprise):

1. On your local PC, press Win + R, type gpedit.msc and press Enter.
2. Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client.
3. Open Turn Off UDP On Client, set it to Enabled, and click OK.
4. Restart your PC and try connecting again.

Using the registry (works on Windows 11 Home too): Open Command Prompt as administrator and run:

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" /v fClientDisableUDP /t REG_DWORD /d 1 /f

Restart afterwards. To undo it later, set the value to 0 or delete it.

Fix 5: Turn off network detection on the host

This is the main long-term fix for the login freeze. Once you can access the remote machine (using Fix 3 or a different user), open gpedit.msc on the host and go to:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections

Open Select network detection on the server, set it to Enabled, and choose Turn off Connect Time Detect and Continuous Network Detect from the drop-down. Click Apply and OK.

In the same Connections folder, you can also open Select RDP transport protocols, enable it, and choose Use only TCP if UDP is causing problems for every user who connects to this host.

Then apply the changes with:

gpupdate /force

Restart the host if the freeze continues.

Fix 6: Fix “Please wait for the Remote Desktop Configuration”

This message means the host’s Remote Desktop services are still preparing your session. If it never finishes:

1. Sign in to the host locally or as another admin user and open services.msc.
2. Check that Remote Desktop Configuration, Remote Desktop Services and User Profile Service are running. Restart Remote Desktop Configuration if it’s stuck. Note that restarting Remote Desktop Services disconnects everyone currently using RDP on that machine.
3. Check Settings > Windows Update on the host. If an update is waiting for a restart, restart the PC. Hosts that are halfway through installing updates often show this message.

Fix 7: Check the user profile

If only one account gets stuck while other accounts sign in fine, that user’s profile is the likely cause. On the host, open Event Viewer > Windows Logs > Application and look for User Profile Service errors around the time of the hang. Large roaming profiles, folder redirection to an unreachable server or a corrupted profile can all hold the login on “Please wait”. Fixing or recreating the profile (after backing up the user’s files) usually solves it.

Fix 8: Simplify display and multi-monitor settings

In the client, open Show Options > Display. Uncheck Use all my monitors for the remote session, pick a normal resolution instead of full screen, and try again. Mismatched scaling between a high-DPI laptop and an external monitor can sometimes freeze the session at login. If this helps, add your monitors back one at a time.

Fix 9: Connect by IP address and check the port

If the PC name resolves slowly or to the wrong address, the connection can hang before sign-in. Try connecting using the host’s IP address instead of its name.

Also check that RDP is listening on the port you expect. On the host, open Regedit and go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp

Look at PortNumber (switch the view to Decimal). The default is 3389. If someone changed it, either connect using HOST:PORT or set it back to 3389 and restart the host. Any port you use must be allowed in Windows Defender Firewall (the built-in “Remote Desktop” rules cover TCP and UDP 3389) and on any network firewall between you and the host.

Fix 10: Check Network Level Authentication and updates

On the host, go to Settings > System > Remote Desktop. Network Level Authentication (NLA) should normally stay on, as it’s more secure. If your client is very old or can’t reach a domain controller, NLA problems can block the login. Updating the client side is a better fix than turning NLA off.

Make sure both your PC and the host have the latest Windows 11 updates. Microsoft has acknowledged and patched RDP freezing and disconnection issues in several past updates. If the problem started right after a particular update, check the Windows release health page for a known issue, install any newer update, and, as a last resort, uninstall the update from Settings > Windows Update > Update history > Uninstall updates.

Still not working?

• Try connecting from a different PC, or use the Windows App / Remote Desktop app instead of mstsc. If it works from elsewhere, the problem is on your client.
• Disconnect from your VPN and test on the same network as the host, if possible.
• Temporarily disable third-party antivirus or security software on the host to test whether it’s slowing logon.
• Use mstsc /admin to connect to the console/admin session on servers.
• Check Event Viewer > Applications and Services Logs > Microsoft > Windows > TerminalServices-LocalSessionManager and RemoteDesktopServices-RdpCoreTS on the host for errors at the time of the hang.

How to stop it from happening again

Keep server-side network detection off on hosts that have frozen before, and keep UDP disabled on clients where freezes return. You lose a little performance on fast networks, but the connection becomes much more dependable. It’s also a good habit to check your RDP Group Policy settings after major Windows 11 feature updates, and to sign out (instead of just closing the window) when you’re done so sessions don’t pile up.

FAQs

Why is my Remote Desktop stuck on “Please wait” in Windows 11?

Usually the remote PC is hanging while checking network quality, setting up the session, or loading your user profile. A stuck old session or UDP issue is also common.

What is the quickest fix?

Reconnect after setting the connection speed to LAN in the Experience tab. If that fails, sign out the stuck session using query session and logoff, or restart the host.

What is the permanent fix?

Enable “Select network detection on the server” with “Turn off Connect Time Detect and Continuous Network Detect” on the host, and turn off UDP on the client if freezes continue.

Will disabling UDP slow down RDP?

Slightly, on fast and stable networks. For most office and support work, you won’t notice much difference, and stability is far better.

Does “Please wait for the Remote Desktop Configuration” mean something is broken?

Not always. It often appears after updates while the host finishes setup. If it lasts more than a few minutes, restart the Remote Desktop Configuration service or the host.

We hope one of these fixes got you past the “Please wait” screen. Which one worked for you? Let us know in the comment section below.