Share via

Windows 11: RDP session intermittently hangs at "Please wait" (no session visible in quser; requires reboot to recover)

Pankaj Vashisht 20 Reputation points
2026-01-01T16:56:31.7833333+00:00

Environment

  • Product: Windows 11 (remote and client both Windows 11)
  • Machine role: Single-user desktop
  • Remote PC name: Pankaj32
  • User type: Local account
  • Usage pattern: Long-running Python workloads (dozens of python.exe processes), frequent RDP use

Summary

After a clean reboot, RDP works normally for some hours. Over time (usually 12–24 hours) and several connect/disconnect cycles, Remote Desktop connections for the main user begin to intermittently hang on the "Please wait" screen. Eventually the failure becomes persistent: every RDP attempt gets stuck at "Please wait" indefinitely.

During the Hang

  • No new RDP session appears in quser / query user
  • qwinsta shows only:
    • services – Disconnected
    • console – Active
    • rdp-tcp – Listen
  • CPU and memory usage are low (e.g., CPU ≈ 2%, RAM ≈ 26%), even with ~80 Python processes running
  • Leaving the client at "Please wait" for 10+ minutes keeps the connection open; no timeout or disconnect is logged

Reproduction Steps

  1. Reboot the Windows 11 remote PC
  2. Log in locally at the console with the main user
  3. Start long-running Python workloads (many python.exe instances)
  4. Connect via RDP from a Windows 11 client using the same user account
    • RDP connects and works normally
  5. Over the next 12–24 hours, repeat cycles of:
    • Disconnecting RDP (closing client window or letting it drop)
    • Reconnecting from the same client with the same user
  6. After some time, RDP connections begin to show intermittent:
    • "Please wait…" for an extended period
    • Sometimes they succeed after 2–3 attempts
  7. Eventually, every RDP attempt for that user gets stuck at "Please wait" indefinitely

Observed Event Logs

TerminalServices-RemoteConnectionManager / Operational

For each failing attempt:

  • Event ID 261 – Listener RDP‑Tcp receives a connection
  • Event ID 1149 – Remote Desktop Services: user authentication succeeded

This indicates the network connection and authentication succeed.

TerminalServices-LocalSessionManager / Operational

Around the same time:

  • Event ID 40 (Information) – "Session 1 has been disconnected, reason code 5"
  • Event ID 24 / 25 / 41 / 42 (Information) – Session disconnect/reconnect events
  • Event ID 59 (Information) – e.g., RpcGetCurrentSessionCapabilities from CertPropSvc; no failure code

There are no Error-level or Warning-level entries in TerminalServices‑LocalSessionManager when the RDP client is stuck on "Please wait".

Security Log

  • Shows successful logon events (4624) for the user when connecting via RDP
  • No logon failure (4625) around the failing attempts

Key Observations

  • The failure happens after 261/1149 (connection + authentication), but before a session appears in quser
  • The RDP connection is not dropped; it remains at "Please wait" for at least 10 minutes with no error
  • No explicit error is logged in TerminalServices logs
  • The console session for the same user remains active and stable
  • High process count (~80 Python processes) does not cause high CPU or memory usage

Impact

  • Cannot use RDP to monitor or debug long-running workloads mid-run
  • Only way to restore RDP is to sign out or reboot, which terminates the long-running jobs
  • No log-backed error to act on; the logon pipeline appears to stall silently

Request

  1. Investigation into why RDP logon for an already logged-in user can hang at "Please wait" with successful connection/auth but no visible RDP session and no Error logs
  2. Guidance or a fix to prevent the RDP logon pipeline from stalling, or provide a way to recover RDP without terminating the existing console session
  3. If this is a known Windows 11 issue, confirmation of affected builds and any existing hotfixes or workarounds that do not require signing out or rebooting between long runs
Windows for business | Windows Client for IT Pros | Devices and deployment | Other
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jason Nguyen Tran 14,360 Reputation points Independent Advisor
    2026-01-05T03:03:40.8566667+00:00

    Hi Pankaj Vashisht,

    Has this solution fixed your problem, or would you like me to keep assisting? If it’s solved, kindly click “Accept Answer” to helps others in the community as well 😊

    1 person found this answer helpful.
  2. leoel 0 Reputation points
    2026-03-19T09:07:59.4266667+00:00

    Hello,

    As a workaround, I would recommend disabling the FastReconnect of RDP on the Host via the following reg key and see if the issue persists:

    HKLM\System\CurrentControlSet\Control\Terminal Server\bAllowFastReconnect

    DWORD

    0
    Let me know.

    Cheers,

  3. Jason Nguyen Tran 14,360 Reputation points Independent Advisor
    2026-01-01T17:49:39.7833333+00:00

    Hi Pankaj Vashisht,

    Based on your observations, the RDP pipeline is completing authentication (Event IDs 261 and 1149) but failing to attach to the existing console session, which explains why no new session appears in quser. This behavior has been reported in certain Windows 11 builds where long-running workloads and repeated connect/disconnect cycles cause the Local Session Manager (LSM) to stall. The presence of multiple Python processes is not the direct cause, but the high process count can increase session state complexity.

    As a workaround, you can try enabling Network Level Authentication (NLA) and ensuring the latest cumulative updates are installed, since Microsoft has addressed several RDP session handling issues in recent patches. Another option is to configure Group Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections > Restrict Remote Desktop Services users to a single Remote Desktop Services session. Enabling this forces reconnections to bind to the existing console session rather than attempting to spawn a new one.

    If the hang persists, you can attempt to reset the RDP service stack without rebooting by running:

    powershell

    net stop termservice  
net start termservice

    This will disconnect active sessions but may allow reconnection without terminating your workloads. For production scenarios, I recommends applying the latest Windows 11 23H2 or 25H2 cumulative updates, as these contain fixes for session reconnection stalls.

    If this guidance helps clarify the issue and provides a path forward, please hit “Accept Answer” so I know your issue is resolved 😊.

    Jason.

    0 comments
  4. Q&A Assist
    2026-01-01T16:56:48.8666667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The issue you are experiencing with RDP sessions intermittently hanging at "Please wait" could be related to several factors, particularly given the usage pattern of long-running Python workloads and the behavior observed over time. Here are some insights and potential troubleshooting steps:

    1. Session Management: The symptoms suggest that the RDP logon pipeline may be stalling. This can happen due to session leaks or memory issues, particularly if non-Microsoft software is involved. Monitoring resource consumption might help identify if a specific process is causing the issue.
    2. RDP Server Memory Issues: If restarting the Remote Desktop Services (RDS) temporarily resolves the issue, it may indicate a memory leak or other resource consumption problem. You can try restarting the RDS service, but be aware that this will disconnect all current users. If the issue persists, consider monitoring memory usage for unusual spikes, especially from non-Microsoft applications.
    3. Event Logs: The absence of error-level logs during the hang is notable. Continue to monitor the Terminal Services logs for any patterns or recurring events that coincide with the hang. This could provide clues about what is happening during the RDP connection process.
    4. Known Issues: There have been reports of RDP sessions freezing or disconnecting after certain updates, particularly with Windows 11. It's advisable to check for any updates or patches that might address these issues. Ensure that your system is updated with the latest patches, as they often contain fixes for known issues.
    5. Workarounds: As a workaround, if the issue occurs, you might consider using a different user account for RDP sessions or testing with a local account to see if the behavior changes. Additionally, if feasible, try to limit the number of concurrent Python processes to see if that alleviates the issue.
    6. Contact Support: If the problem continues and significantly impacts your workflow, consider reaching out to Microsoft support for more tailored assistance, especially if you suspect it may be a bug in Windows 11.

    These steps should help you investigate the issue further and potentially mitigate the impact of the RDP session hangs.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.