Please Wait on black screen

Have an administrator identify and log off only the affected Remote Desktop session, because a stalled existing session can reconnect to a black screen without requiring a server restart.

End the affected session

From another administrative session, the server console, or a management host with permission to administer the server:

1. List the sessions:

query session /server:SERVERNAME

2. Locate the affected username and note its session ID.
3. Warn the user that logging off closes applications and can discard unsaved work.
4. Log off that session:

logoff SESSION_ID /server:SERVERNAME /v

logoff deletes the selected session and requires Full Control permission when terminating another user’s session.^1^

5. Reconnect and confirm that a fresh desktop loads.

If normal logoff cannot clear the malfunctioning session, reset that session:

reset session SESSION_ID /server:SERVERNAME /v

A reset forcibly deletes the session and carries the same unsaved-data risk.^2^

Do not use a script that logs off every session unless the entire RDS host is affected; Microsoft warns that doing so can cause unsaved data loss for all connected users.^3^

If the problem returns

The next action depends on the server and connection type:

• Windows Server 2012 R2, particularly after repeated disconnect/reconnect cycles: install the applicable current Windows updates. Microsoft documents a reconnect-related black-screen condition in which ending the session restores the display, with historical fixes in KB4103724 and KB4284863.^4^
• Older Windows Server 2003 only: in mstsc.exe, select Show Options → Experience, clear Persistent bitmap caching, and reconnect. Microsoft’s article documenting this fix applies specifically to Windows Server 2003, so it should not be treated as the primary fix for newer servers.^5^
• Azure Virtual Desktop using Windows 10 Enterprise multi-session 22H2: open Event Viewer → Windows Logs → Application and look for Microsoft-Windows-AppModel-State, Event ID 10, mentioning Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy with error -2147024893. Only when that exact signature exists, install KB5045594 or a later applicable update and register the broker package through a user logon script as documented by Microsoft:^6^

Add-AppxPackage -Register `
  -Path "C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AppxManifest.xml" `
  -DisableDevelopmentMode

If every user is affected

If no user can complete sign-in, check the host from its console or another remote-management channel:

Get-Service TermService, UmRdpService
qwinsta

Both services should be running, and qwinsta should show rdp-tcp in the Listen state. Microsoft’s general RDP procedure also covers checking the listener certificate, port, firewall, and Group Policy when these checks fail.^7^

If the session still hangs after a fresh logon, collect the server version, whether one or all users are affected, whether this is AVD or conventional RDS, and the exact “Please wait” text—especially whether it names Local Session Manager or User Profile Service. Those details determine the applicable profile, logon-service, or version-specific branch.

References

1. logoff
2. reset session
3. How to Log off all Remote Desktop Session Users from a Command Prompt
4. Poor performance or application problems during remote desktop ...
5. A black screen appears while sign-in - Windows Server
6. AVD users might experience extended time on a black screen during logon and SSO failures | Microsoft Support
7. General Remote Desktop connection troubleshooting - Windows Server ...