You connect to your Windows VPS with Remote Desktop, authentication succeeds — and you get a black screen, sometimes with just a mouse cursor. The session is usually fine underneath; something in the display pipeline or the user shell is stuck. Try these fixes in order, from quickest to most involved.

1. Wait a moment, then nudge it

On first login after a reboot or update, Windows may still be preparing the profile or finishing updates. Give it 30–60 seconds. Then:

  • Press Ctrl+Alt+End (the RDP equivalent of Ctrl+Alt+Del) and choose Task Manager or Sign out. Often this alone redraws the screen.
  • Toggle full screen with Ctrl+Alt+Break.

2. Restart Explorer

If Ctrl+Alt+End shows a menu, open Task Manager → File → Run new task → explorer.exe. A crashed or hung Windows Explorer leaves the desktop black; restarting it brings back the taskbar and desktop.

3. Reconnect with different display settings

In the Remote Desktop client (mstsc) → Show Options:

  • Display: choose a lower resolution and True Color (24-bit) or 16-bit instead of 32-bit.
  • Experience: uncheck Persistent bitmap caching — a corrupted local cache is a frequent cause of black or partly black screens.
  • Uncheck Reconnect if the connection is dropped temporarily, then connect again.

On macOS (Windows App), try disabling “Optimize for Retina displays” and lowering the resolution.

4. Sign out the stuck session

A disconnected session in a bad state can be reused when you reconnect. Sign it out from another session or via PowerShell over the VNC console:

quser                    # list sessions and IDs
logoff 2                 # sign out session ID 2

Then connect again — you’ll get a fresh session. On Windows Server you can also connect to the console session: mstsc /admin.

5. Use the VPS console

If RDP stays black, log in through the VNC console in your VPS control panel. You’ll see whether Windows is:

  • still installing updates (“Working on updates… don’t turn off your computer”) — wait;
  • showing an error dialog blocking the session;
  • out of memory or disk space;
  • stuck at a black screen locally too (then it’s not an RDP problem — see below).

6. Disable problematic graphics features

On Windows Server and Windows 10/11, a few RDP graphics settings are known to cause black screens with some clients and drivers. Via Group Policy (gpedit.msc):

Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Remote Session Environment:

  • Use WDDM graphics display driver for Remote Desktop Connections → Disabled
  • Use hardware graphics adapters for all Remote Desktop Services sessions → Disabled

And under Connections: Select RDP transport protocols → Use only TCP (helps when UDP is unreliable or blocked).

Run gpupdate /force and reconnect (sign out first). The UDP change is also helpful when screens freeze or go black on unstable networks.

7. Display and VirtIO drivers

On KVM virtual machines, outdated or mismatched display drivers can cause issues. Check Device Manager → Display adapters for warnings. Installing the current virtio-win drivers (including the display/QXL driver where applicable) can help. See Windows Device Manager.

8. Resource exhaustion

A server out of memory or with a full system drive can fail to create the desktop:

Get-CimInstance Win32_OperatingSystem | Select-Object FreePhysicalMemory, TotalVisibleMemorySize
Get-PSDrive C

Free up space (temporary files cleanup) or stop memory-hungry processes. A VPS that’s routinely short on RAM needs a bigger plan.

9. User profile problems

A corrupted profile can produce a black screen for one user only. Test with another admin account. If that works, back up the user’s data and recreate the profile.

10. Check the event logs

Event Viewer → Applications and Services Logs → Microsoft → Windows → TerminalServices-LocalSessionManager and RemoteDesktopServices-RdpCoreTS often record why a session failed. System and Application logs show Explorer crashes and driver errors. See Windows event logging.

Quick checklist

  1. Wait, then Ctrl+Alt+End → Task Manager → run explorer.exe.
  2. Reconnect without bitmap caching, lower colour depth/resolution.
  3. Log off stuck sessions (quser, logoff).
  4. Check via VNC console: updates, errors, resources.
  5. Group Policy: disable WDDM driver for RDP, TCP only.
  6. Update VirtIO/display drivers.

Related: connecting to a Windows VPS with Remote Desktop and RDP connection errors. Every Windows VPS from VPS.DO includes a VNC console — the safety net for exactly these situations.

  • RDP
  • Windows Server
  • Troubleshooting