Remote Desktop Stuck on "Please Wait"?

How Can I Diagnose and Terminate Hung RDP Sessions Using Remote PowerShell or CMD?

When RDP is stuck on "Please wait," it's often due to zombie user sessions or mismanaged session states. These can persist on the target machine, preventing new connections from initializing correctly.

Use query user to identify stuck sessions

Remote into the host machine using PowerShell remoting or SSH, and then run:

query user

This command returns the list of active, disconnected, and idle user sessions with their session IDs and status.

Example output:

USERNAME     SESSIONNAME        ID  STATE        IDLE TIME      LOGON TIME
john.doe          rdp-tcp#5                 2   Active        .                       27/10/2026 09:23 AM
                          rdp-tcp#6                 3   Disconnected     1:05                 27/10/2026 07:45 AM

Look for sessions in the “Disc” (Disconnected) or “Down” state. These may be interfering with new connections.

Reset the Problematic Session

Use the session ID you identified above to reset the stuck session:

reset session 3

This command forcefully terminates the specified RDP session on the host, clearing any login blocks.

Transitional Insight

If the session reset doesn’t restore connectivity or the host continues to hang on "Please wait," the issue may involve the RDP client process or Windows services on either the client or server side. Let’s look deeper.

How Can I Kill RDP client-side processes to recover local responsiveness?

The hang can originate from the client machine. On current Windows systems, Remote Desktop Connection (mstsc.exe) remains available for traditional RDP connections, while Windows App replaces Microsoft's retired standalone Remote Desktop client for accessing Azure Virtual Desktop, Windows 365 and Microsoft Dev Box.

Identify Active RDP Processes

Open Command Prompt as Administrator on the client:

Check whether Remote Desktop Connection (mstsc.exe) or Windows App is running and unresponsive. The older standalone Remote Desktop client (msrdc.exe) reached end of support on 27 March 2026, and should no longer be presented as Microsoft's current client.

Force-Kill the RDP Process

Terminate it to restart a clean session:

This immediately ends the client-side session and avoids lingering cache states or handshake errors.

Note for IT Admins

Windows App is Microsoft's supported client for Azure Virtual Desktop, Windows 365 and Microsoft Dev Box. If a connection becomes unresponsive, identify the application in Task Manager and close the affected process before reconnecting. For traditional RDP connections using Remote Desktop Connection, mstsc.exe remains the relevant process.

How Can I Restart Windows Remote Desktop Services to Unblock the Host System?

At the OS level, RDP relies on several background services to handle authentication, session initialization, clipboard sync, and user environment loading. A corrupted or blocked service may prevent logon from completing.

Restart TermService to Refresh RDP Core

On the remote host, run:

You may see a warning that other services will be affected. This is normal for remote environments, but ensure no critical operations are underway.

Restart SENS and Dependencies

Some RDP hangs involve the System Event Notification Service (SENS) or dependent RPC services. Restart them in order:

Optionally:

Pro Tip: Use Get-Service and sc for Validation

Run this PowerShell line to validate the service state:

Get-Service -Name TermService, SENS | Format-Table Name, Status, StartType

Use sc qc TermService to confirm dependency chains.

Check Recent Windows Updates for Known RDP Issues

Recent Windows updates have introduced additional causes of Remote Desktop connection failures and sessions becoming unresponsive. Before resetting services repeatedly, check the Windows version, installed updates and Microsoft's Windows release-health documentation.

• Windows 11 24H2 (2025): Updates released in early 2025 caused some UDP-based RDP connections to Windows Server 2016 or earlier to disconnect after approximately 65 seconds. Microsoft resolved this issue with KB5053656, released on March 27, 2025.
• Windows 11 24H2/25H2 and Windows Server 2025 (September 2026): Security updates caused instability in Remote Desktop Services in some environments, including failed logins and servers stuck on "Please wait for the Remote Desktop Configuration." Microsoft resolved the issue through out-of-band updates KB5129195 for affected Windows 11 versions and KB5129235 for Windows Server 2025, released on 14 September 2026.
• Windows 11 24H2/25H2 (October 2026): Microsoft also documented RDP connection failures affecting non-administrator users on remote hosts with Administrator protection enabled after KB5124010 or later updates. This issue produces error 0xC000000D rather than a typical "Please wait" screen, but it is relevant when diagnosing broader remote login failures.

If the problem began immediately after a Windows update, compare the installed KB numbers with the relevant release-health page and install the latest cumulative update containing Microsoft's fix. Avoid resetting sessions or restarting critical services before determining whether a documented Windows issue is responsible.

How Can I Perform a Clean Boot to Rule Out Software Conflicts?

Background applications—especially security tools or remote management suites—can interfere with user profile loading and remote logon scripts.

Configure a Clean Boot Environment

On the host machine:

1. Press Win + R, type msconfig, hit Enter.
2. Go to the Services tab.
3. Check "Hide all Microsoft services."
4. Click Disable All.
5. Go to Startup > Open Task Manager > Disable all startup apps.
6. Reboot the system.

Observe Post-Boot RDP Behaviour

Attempt to reconnect via RDP If the issue disappears, enable startup services in batches to identify the conflicting component.

Common Culprits

• Antivirus programs with RDP filtering.
• Third-party credential managers.
• Remote assistance tools with screen hooks.

How Can I Adjust Group Policy to Prevent Session Conflicts?

In domain or multi-user environments, misconfigured Group Policies can lead to session overlaps, orphaned credentials, or repeated logon loops.

Navigate to the Correct Policy Setting

Run gpedit.msc, then:

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

Enable "Restrict RDS Users to a Single Session"

Set the following to Enabled :

• Policy : Restrict Remote Desktop Services users to a single session

This ensures that reconnect attempts resume the previous session instead of creating a new (potentially broken) one.

Force Policy Update and Session Reinitialization

After changing the policy, run:

You may also want to reboot the machine or restart TermService to apply changes fully.

How Can I Automate All Fixes with a Combined Recovery Script?

For recurring incidents, it’s efficient to script a one-liner that resets sessions and restarts services without rebooting.

Master Recovery Command

If Remote Desktop remains stuck on "Please Wait," use the appropriate recovery command depending on whether the issue originates from the client or remote host.

On the client: For traditional Remote Desktop Connection (mstsc.exe), close the unresponsive process:

taskkill /IM mstsc.exe /F /T

If you use Windows App, close the affected application through Task Manager instead.

On the remote host: If clipboard redirection is unresponsive, restart its process:

taskkill /IM rdpclip.exe /F /T

If the session remains blocked and Remote Desktop Services needs to be restarted, run the following from an elevated Command Prompt using an independent administrative connection:

net stop TermService && net start TermService

Important: Restarting Remote Desktop Services can interrupt active user sessions. Use this command only after checking for affected users and ensuring that alternative administrative access is available.

Discover TSplus: A Smarter Remote Desktop Solution

TSplus Remote Access is engineered to eliminate common RDP frustrations, including the dreaded “Please wait” screen. With features like centralised session management, smart reconnection, and web-based access, it ensures reliable and responsive connectivity across all environments. TSplus empowers IT admins with full control over remote sessions—no reboots, no stuck logins, just smooth, secure access.

Conclusion

The “Remote Desktop stuck on ‘Please wait’” issue is more than a minor inconvenience—it’s a symptom of deeper problems like unclosed sessions, misconfigured services, or system conflicts. By understanding the technical causes and applying targeted fixes, IT professionals can swiftly restore access and minimise downtime. However, for lasting stability and efficiency, relying solely on manual RDP troubleshooting may not be enough in demanding or large-scale environments.