Remote Desktop Black Screen: 3 Fast Fixes That Work

Windows Errors Intermediate 👁 13 views 📅 Jun 23, 2026

Remote Desktop shows black screen after connecting. Usually a graphics or session issue. Here's the real fixes.

1. Turn Off Persistent Bitmap Caching (Most Common Fix)

This is the fix that works 9 times out of 10. When you connect to a remote PC, Windows saves little pieces of the screen (bitmaps) to make things faster later. But sometimes those saved pieces get corrupted or out of sync, and you end up with a black screen instead of your desktop.

Here's how to turn it off:

  1. Open Remote Desktop Connection. You can find it by typing mstsc in the Start menu search bar, then press Enter.
  2. You'll see the login window. Don't type anything yet. Instead, click the Show Options button at the bottom left. It's a small arrow pointing down.
  3. After you click it, you'll see a tab labeled Experience. Go ahead and click that tab.
  4. Under Performance, you'll see a list of checkboxes. Find the one that says Persistent bitmap caching. Uncheck it.
  5. Below that, there's a drop-down menu labeled Choose your connection speed to optimize performance. Select LAN (10 Mbps or higher) from that menu.
  6. Now click Connect and enter your credentials. After you connect, you should see the desktop instead of a black screen.

If that didn't work, try the next fix.

2. Reset the Remote Desktop Session (Second Most Common)

Sometimes the remote session itself is stuck. This happens a lot when you disconnect without logging off properly — like closing the laptop lid or losing internet. The old session is still running in the background, but it's broken. When you reconnect, you get a black screen because the new connection can't talk to the old session.

Here's what to do:

  1. On your local computer, open a Command Prompt as administrator. Press the Windows key, type cmd, right-click Command Prompt in the results, and choose Run as administrator.
  2. A dark window will appear. Type this command exactly and press Enter:
    query session
    You'll see a list of sessions. Look for one with a number like 1 or 2 next to your username. That's the stuck session.
  3. Now type this command, replacing 1 with the session number you found:
    rwinsta 1
    Press Enter. This will forcefully reset that session.
  4. Close the Command Prompt. Now open Remote Desktop again and connect normally. This time you should get a fresh session with no black screen.

A quick note: If you don't have admin rights on the remote PC, this won't work. You'll need to ask the IT person to do it for you.

3. Disable the Remote Desktop CredSSP Encryption (Less Common But Works)

This one is more technical. Sometimes the encryption that's used to protect your connection gets in the way. The black screen happens when the remote PC can't negotiate the encryption level your local PC is asking for. This is more common when connecting between different Windows versions — like Windows 10 to an older Windows Server 2012 R2.

Here's how to lower the encryption temporarily:

  1. Press Windows key + R on your keyboard. A small Run box pops up.
  2. Type gpedit.msc and press Enter. If you're on Windows Home edition, this tool isn't available. Skip to the registry method below.
  3. In the Group Policy Editor, go to:
    Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
  4. Find the setting named Require use of specific security layer for remote (RDP) connections. Double-click it.
  5. Select Enabled in the top left. Then under Security Layer, choose RDP from the drop-down menu.
  6. Click Apply, then OK. Close the Group Policy Editor.
  7. Restart your computer for the change to take effect. After rebooting, try the Remote Desktop again.

If you don't have gpedit.msc (Windows Home users):

  1. Press Windows key + R, type regedit, and press Enter.
  2. Go to this path in the left panel:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
  3. On the right side, look for a value named SecurityLayer. If it's not there, right-click an empty space, choose New > DWORD (32-bit) Value, and name it SecurityLayer.
  4. Double-click SecurityLayer. Set the value to 0 (that's the RDP security layer). Click OK.
  5. Close the Registry Editor and restart your PC.

A warning: This lowers the encryption level. It's fine for a home network or a lab, but don't use this on a corporate network without checking with your IT team. They might have security policies that require higher encryption.

Quick Reference Table

CauseSymptomsFixTime to Apply
Persistent bitmap caching corruptionBlack screen after connect, no cursor, or cursor onlyUncheck Persistent bitmap caching in Experience tab2 minutes
Stuck remote sessionBlack screen after reconnect, especially after disconnected without logoffRun rwinsta command in Command Prompt3 minutes
CredSSP encryption mismatchBlack screen between different Windows versions, or after Windows updateSet Security Layer to RDP in Group Policy or Registry5 minutes

Try these in order. The bitmap caching fix is the easiest and most likely to work. If you still get a black screen after all three, the problem might be with the remote PC's graphics driver. In that case, update the video driver on the remote computer and try again.

Was this solution helpful?