Short answer: a black Remote Desktop window means the connection works, but either no picture gets through or no desktop was started. Press Ctrl+Alt+End: if the Windows Security screen appears, the session is alive and the desktop shell (Explorer) is the next suspect. If nothing appears, reconnect without the bitmap cache and over TCP, and if the screen stays black, end the stuck session from the server's console.
:: 1. On your PC: reconnect in public mode (no cached bitmaps) in a 1280 x 800 window
mstsc /v:203.0.113.10 /public /w:1280 /h:800
:: 2. In the black window: Ctrl+Alt+End, Task Manager, Run new task, explorer.exe
:: 3. On the server (console or another session): list sessions, end the broken one
query session
reset session 2Use your server's address instead of 203.0.113.10 and the ID that query session shows for your user instead of 2. Microsoft's mstsc reference says that in public mode Remote Desktop does not cache passwords and bitmaps. reset session deletes the session, and Microsoft warns that unsaved data in it can be lost.
The 30-second checks
- Switch between window and full screen with Ctrl+Alt+Break (or Ctrl+Alt+Pause). Microsoft documents this shortcut only as the mode switch, so treat it as a free first test, not a fix.
- Press Ctrl+Alt+End. In Microsoft's list of Remote Desktop shortcut keys it opens the Windows Security screen of the remote computer. If it appears, Windows is answering and you can go straight to Explorer did not start.
- Disconnect and reconnect with
mstsc /public, in a window rather than full screen and on one monitor. If the picture comes back, the cause is on your side: the cache, the display settings or the transport. - Try another client, for example Windows App instead of
mstsc, or another PC. A black screen that follows you to every client is on the server. - Look at the server's console. On a VPS or dedicated server, a provider's web or out-of-band console, if yours offers one, shows the screen of the machine itself. A boot error or an update screen there means RDP is not the problem.
Symptoms and their likely causes
| Symptom | Possible cause | What to try |
|---|---|---|
| Black after login, Ctrl+Alt+End works | Explorer crashed or was replaced by another program | Start explorer.exe from Task Manager |
| Black or frozen after a few seconds, often only on some networks | UDP transport or a stale bitmap cache | Reconnect with /public, then force TCP |
| Black on one monitor or at a high resolution | Multi-monitor or resolution settings | One monitor, smaller window |
| Black every time you reconnect to an old session | Session stuck after a disconnect | Reset the session from the console |
| Black for every user, after a graphics driver update | GPU or WDDM driver on the server | Update the driver, test the RDP graphics policies |
| xrdp on Linux: black, then disconnected | Same user logged in locally, or a Wayland-only desktop | Log out locally, use an X11 desktop |
1. Turn off persistent bitmap caching
Remote Desktop Connection can keep parts of the remote screen as bitmaps on your disk and reuse them in later connections. A Microsoft support article on a black screen at sign-in recommends disabling bitmap caching on the client; it was written for Windows Server 2003, so on current versions treat it as a cheap test rather than a documented cause. mstsc /public tests without the cache; to switch it off for good:
- 1Open the connection settings
Run
mstscand click Show Options. - 2Clear the cache option
On the Experience tab, clear Persistent bitmap caching.
- 3Save and connect
On the General tab, click Save (or save over your own
.rdpfile), then connect again.
2. Force TCP when the session freezes or turns black
Microsoft's description of the client policy says that unless UDP is turned off, RDP traffic will attempt to use both TCP and UDP. Microsoft documents switching to TCP only in its Dev Box troubleshooting guide, for frequent connection drops. It does not list black screens as a symptom there, so forcing TCP is a test: if the picture comes back, look at UDP handling on the network path.
In gpedit.msc on your PC, go to Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Connection Client and set Turn Off UDP On Client to Enabled. On Windows editions without gpedit.msc, set the same policy value in the registry:
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" /v fClientDisableUDP /t REG_DWORD /d 1 /f
:: undo it once the test is over
reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" /v fClientDisableUDP /fMicrosoft's guide then runs gpupdate /force in an elevated shell and restarts the machine. The server has a matching policy: Select RDP transport protocols under Remote Desktop Session Host → Connections, set to Use only TCP. If TCP fixes it, look at the firewall or NAT in the path rather than leaving UDP off on every PC.
3. Display, resolution and multiple monitors
Several monitors or a very high resolution are worth ruling out. Test with the smallest setup first, then add monitors back:
- On the Display tab of
mstsc, clear Use all my monitors for the remote session and pick a smaller size. mstsc /llists your monitors with their IDs. Theselectedmonitorsline in an.rdpfile takes those IDs, and per Microsoft the chosen displays must be contiguous./spanonly works with monitors of the same resolution placed side by side; Microsoft says vertical spanning is not supported. Use/multimonfor any other layout.desktopwidthanddesktopheightin an.rdpfile accept 200 to 8192 pixels.
On a Mac, one macOS setting blanks the other displays in full screen; it is described in RDP from a Mac. For a smoother picture on a slow line, see making RDP smoother on a slow connection.
4. Explorer did not start
If Ctrl+Alt+End brings up the security screen, Windows is answering, so a missing desktop shell is the next thing to rule out. Start it by hand:
- 1Open Task Manager
Press Ctrl+Alt+End and choose Task Manager.
- 2Run Explorer
Choose Run new task (in the File menu on older versions), type
explorer.exeand press Enter.
If the taskbar appears, Explorer had crashed or never started. Event Viewer, under Windows Logs → Application, may show an error that names explorer.exe. Also check whether something replaced the shell on purpose: Microsoft documents that the policy Start a program on connection (Remote Desktop Session Host → Remote Session Environment, under Computer or User Configuration) hides the Start menu and the desktop, and that an alternate shell line in an .rdp file starts a program instead of Explorer. Open the .rdp file in Notepad and look for it.
5. A session stuck after a disconnect
Closing the RDP window only disconnects. The session keeps running on the server, and the next connection takes you back into it, black screen included. Microsoft describes this exact pattern for Windows Server 2012 R2, Windows 8.x and the first Windows 10 release: after several disconnects and reconnects the session showed only black, and users had to end it from the console. Updates fixed that bug, but ending the session is the same remedy to try when a session on a newer version gets stuck in the same way.
Sign in through the server's console (your provider's, if it offers one) or as a different admin, open Command Prompt or PowerShell as Administrator and end the broken session:
query session # sessions with ID and state (Active, Disc)
logoff 2 # sign out session 2; its programs close
reset session 2 # if logoff does not end it: delete the session
query session /server:SERVER # the same from another Windows machine
reset session 2 /server:SERVER # that can reach SERVER, with admin rights on itThen reconnect. To keep it from happening again, sign out from the Start menu instead of closing the window, or let Windows end disconnected sessions after a time limit, as shown in the connection limit section of multiple RDP sessions. If RDP itself stopped answering, the console steps are in enabling RDP without RDP.
6. GPU or display driver on the server
This applies to a dedicated server or workstation with a real graphics card; a typical VPS gives Windows only a virtual display adapter. Suspect the driver when every user sees black and it started after a driver or Windows update. Install the current cumulative update and the graphics vendor's current driver first, then test with two policies under Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Remote Session Environment:
- Use hardware graphics adapters for all Remote Desktop Services sessions set to Disabled: per Microsoft's policy reference, sessions then use the Microsoft Basic Render Driver instead of the graphics card (on an RD Session Host server that is already the default when the policy is not configured).
- Use WDDM graphics display driver for Remote Desktop Connections set to Disabled: per the same reference, Remote Desktop then uses the XDDM display driver instead of WDDM, and the change needs a restart of Windows. Microsoft has listed XDDM-based remote display drivers as deprecated since Windows Server 2022, with removal planned for a future release, and the policy reference does not say whether newer builds still honour this switch. Test it, but do not count on it on Windows Server 2025.
Run gpupdate /force and restart. Microsoft documents what these switches do, not that they cure black screens; they are a test. If the picture returns, the graphics driver is the culprit. Fix or roll back the driver, then set both policies back to Not Configured.
7. Linux: the xrdp black screen
xrdp runs every session in its own X server (the xorgxrdp module for Xorg, or Xvnc), so the causes differ from Windows. Read /var/log/xrdp-sesman.log first; it records the session start.
sudo tail -n 30 /var/log/xrdp-sesman.log # why the session ended
loginctl list-sessions # is the same user logged in on a seat too?
echo xfce4-session > ~/.xsession # X11 desktop for xrdp (xfce4 must be installed)The same user is logged in locally
The xrdp FAQ says that on systemd distributions one user cannot be logged in on the graphical console and over xrdp at the same time, because both sessions share one session D-Bus. Log out on the console, or use a separate account for RDP.
A Wayland-only desktop
Since Ubuntu 25.10, and in Ubuntu 26.04 LTS, the Ubuntu desktop session runs only on Wayland; the release notes say GNOME Shell can no longer run as an X.org session. It therefore cannot start inside xrdp's X server. Install XFCE and write xfce4-session into ~/.xsession, as in the block above.
startwm.sh
/etc/xrdp/startwm.sh starts the desktop through /etc/X11/Xsession on Debian and Ubuntu. A user guide on the xrdp wiki for GNOME on Ubuntu 24.04 adds unset DBUS_SESSION_BUS_ADDRESS and unset XDG_RUNTIME_DIR just before that line so the session does not crash right after login. It is a community recipe, not an official default.
Frequently asked
Why is my Remote Desktop screen black after I log in?
The connection works, but either the picture does not get through or the desktop did not start. Press Ctrl+Alt+End: if the Windows Security screen appears, start explorer.exe from Task Manager with Run new task. If nothing appears, reconnect with mstsc /public (no bitmap cache) in a small window and test with UDP turned off.
How do I turn off UDP for Remote Desktop?
On the client, set the policy Turn Off UDP On Client to Enabled under Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client. The registry equivalent is the DWORD fClientDisableUDP = 1 under HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client. Run gpupdate /force and restart, and remove the setting again once the test is over.
How do I fix an RDP session that is black every time I reconnect?
The disconnected session itself is broken, and every reconnect takes you back into it. Sign in through the server's console or as another admin, run query session to find its ID, then logoff <ID> or reset session <ID>. Both close the programs in that session, so unsaved work is lost.
Why does xrdp show a black screen?
One documented cause is the same user still logged in on the server's graphical console: on systemd distributions the xrdp FAQ says both sessions would share one session D-Bus, so one user cannot have both at once. Since Ubuntu 25.10, and in 26.04 LTS, the Ubuntu GNOME session runs only on Wayland, so it cannot start in xrdp's X server; use XFCE with xfce4-session in ~/.xsession. The reason is usually in /var/log/xrdp-sesman.log.