75

I've been having this issue since I updated (fresh install) to Windows 10 Professional. I used to connect to my computer via RDP through WAN and LAN with no issues.

After installing W10 and setting up everything correctly (ports, static IP etc) I still can connect, but during the day it randomly kicks me out and I can't successfully log in afterwards. It makes a secure connection and connects, but I get a black screen without a cursor and disconnects a few seconds after that without any errors.

It's an Intel i7 desktop with nVidia GPU with the latest drivers.

Things that I know/tried:

  1. When issue occurs, I can replicate it on Windows, Mac, or iPads/iPhones over LAN or WAN.

  2. Rebooting temporarily fixes the problem, until it starts happening again.

  3. Disabling bitmap caching or changing resolution on RDP client doesn't fix it.

  4. Pressing CTRL + ALT + END doesn't do anything.

  5. Created a new account and tried logging on to that to test if it is account related, still didn't log in.

  6. Did a sfc /scannow to do a system scan and fix corrupt files, it came out with no errors.

  7. I checked the event log and apparently WINLOGON keeps crashing. It only says "the windows logon process has unexpectedly terminated"

I ran out of options to fix this, any help will be appreciated.

Sami Kuhmonen
  • 2,123
  • 1
  • 20
  • 29
asansal
  • 751
  • 1
  • 5
  • 3
  • Is it the client or the server that you reboot that fixes the problem? – cdavid Sep 21 '15 at 23:22
  • Have you tried using a VPN and not exposing 3389 to the WAN? – Linef4ult Sep 22 '15 at 05:36
  • Me too. It's not this - http://www.tenforums.com/network-sharing/12445-rdp-w10-disconnected-after-few-seconds.html because I have passwords on all the accounts, and it does the same thing regardless of local console connections status. – nerdfever.com Jan 09 '16 at 20:04
  • I have been experiencing this issue with server 2012 R2, and while the issue may not be related, the symptoms are very similar. Black screen and rebooting the server fixed it for a while. I don't have an answer, but I have it linked to TermService service crashing, despite not much in the logs indicating it. TermService is unusual since it can't be stopped via services.msc, but you can use `tasklist /svc | findstr /C:TermService` to identify the Process ID and `taskkill /F /PID [process_id]` to end the process. Start TermService using `net start TermService`. I am still working on a solution. – Johnny Keeton Aug 24 '16 at 02:03
  • What happens if you disable the **Smart Card Device Enumeration Service**? I've experienced this problem on a variety machines and multiple times traced it back to this service. No clue why; other than this service is called when an RDP session is created. – I say Reinstate Monica Dec 01 '16 at 02:07
  • Has anyone managed to resolve this? – mythofechelon Jan 06 '17 at 16:11
  • Also curious if anyone has resolved this issue? I have exactly the same scenario. – Todilo Dec 22 '17 at 11:38
  • 1
    @Todilo See my answer below. – Syntax Error Mar 12 '18 at 22:39
  • This just started happening to me after working fine for years. It happens randomly after being connected a while, and it's either a frozen screen or solid bg color. Really annoying. – Dirigible Mar 28 '19 at 14:57
  • I get the black screen only in a very specific situation: when I am working on the Recycle Bin of the remote computer, permanently deleting some of its content. At some point, I get a message about a "protocol error" and the RDP connection breaks. When I try to reconnect, the first two or three attempts fail. At that point, every time I try to connect, I get the black screen. None of the suggested solutions has worked for me. The only remedy has been to reboot the remote PC, which solves the problem. But that's too bad because the remote PC is at a different location. – Alessandro Aug 19 '20 at 15:52

15 Answers15

62

Remote Desktop – Black Screen Of Death

The Issue

Using Remote Desktop the remote screen turns black right after login and you have no control. The issue appears to be caused by Screen Caching and accessing a system with different display resolution or RDP window sizes.

The Solution(s)

  • While logged in and stuck on the black screen of death
    1. Press CTRL+ALT+END, or CTRL+ALT+FN+END on laptops. This calls Task Manager and in most cases you’ll immediately see the Desktop.
    2. If only Task Manager but no Desktop appears try running Explorer from Task Manager: File > New Task > Explorer.exe
  • Try connecting at a different resolution.
  • Access the remote computers Computer Management or Services MMC and cycle the Remote Desktop Services service.
  • Update display drivers, both on the connecting machine and on the machine you are connecting too.
    1. Some users are experiencing this with Nvidia GPUs. The Geforce Experience program has a "Share" feature aka "shadow play"; when enabled some people experience the problem. Try to disable it, restart and see if it helps.
    2. Check the display settings at the remote host and see if there is a phantom monitor present. Might need to change which monitor is the primary one
  • Start a new RDP client on your desktop but BEFORE you click CONNECT, click the SHOW OPTIONS link, click the DISPLAY tab and set the DISPLAY CONFIGURATION to a low resolution like 640×480.
  • Try turning off Fast Startup
    • This feature only works when you do a SHUTDOWN and then Boot. It doesn't effect a RESTART.
    • Go to Control panel, Power Options and select Choose What the Power Buttons Do on the left.
    • Then select Change Settings That are Currently Unavailable near the top center of screen...
    • Lower down on the window, uncheck Fast Startup.

Prevention

  • Disable bitmap caching for your RDP connections
  • Confirm RDP account has full administrative rights on remote system
  • Access the remote computer using consistent resolution – Full screen may help
  • Confirm both systems' video drivers are up to date

Resources

(Google it at Microsoft support sites; I have too low a reputation to post links)

  • Disable Bitmap Caching 2012
  • Hotfix for “Black screen during a Remote Assistance session in Windows Vista, in Windows Server 2008, in Windows 7, or in Windows Server 2008 R2”
  • The lock screen is black or blank and does not respond to keyboard or swipe actions in Windows 10 Technical Preview

Disable Bitmap Caching

Community
  • 1
dadde
  • 720
  • 5
  • 8
  • 9
    None of this works, maybe this issue has resurfaced with a different cause.. – Dirigible Mar 28 '19 at 14:59
  • 3
    As of 2019/6/28 **Windows 10 v1809** the above steps worked. I only needed to perform _"While logged in and stuck on the black screen of death "_ steps **1** & **2** – Deleted Jun 28 '19 at 02:12
  • Another work-around (how I fixed it permanently) is to just install/use the RDC Manager for all RDP: https://www.microsoft.com/en-us/download/details.aspx?id=44989 - I like it better anyway.. – B. Shea Jul 07 '19 at 14:39
  • Pulling up ctrl + alt + delete worked for me. I logged out from that screen and upon rdp'ing back in, the desktop loaded normally – TabsNotSpaces Jun 15 '20 at 20:05
  • I run into this issue when acessing RDP from home, while it works fine on the same laptop in office. My guess it has something to do with a network – ADOConnection Dec 12 '20 at 10:30
  • Amazing. The first solution works for me. Just a small note - to open Task Manager directly I just typed "ctrl+shift+escape" – Colm Bhandal Apr 22 '21 at 16:44
  • warning on using ctrl-alt-del, for me it was on my host machine, so i accidentally logged myself out, losing unsaved work. – Chris C Jun 22 '23 at 15:39
10

I tried all of the above suggestions but none of them worked for me. I just wanted to restart the remote machine to see whether it will fix the issue. It indeed worked.

I did the following to restart the remote machine via command line (with admin privilege) as I could not find a way to restart the remote machine via RDP.

Step 1: Login to the remote machine

net use \\<remote machine IP>\IPC$ <password> /USER:<username>
Ex: net use \\192.168.0.1\IPC$ password1 /USER:user1

Step 2: Restart remote machine

shutdown /r /m \\<remote machine IP>
Ex: shutdown /r /m \\192.168.0.1
Rajaraman Subramanian
  • 221
  • 2
  • 7
5

None of the other answers worked for me, I finally found something that did, after a lot of digging. Use the Group Policy Editor (or download the superior "Policy Plus"), and disable UDP. You can find this in policy rds/client or rds/host/connection/select protocols, or in the registry at SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client

There are a lot of settings to fiddle with in there, you could also try disabling RemoteFX graphics.

Dirigible
  • 291
  • 3
  • 5
4

I've had the same problem - switch from 32bit to 24bit colours and it will let you connect as normal. All other settings can be left on their defaults.

Picture of RDP settings with 24bit colours highlighted

Syntax Error
  • 232
  • 2
  • 15
3

The remote desktop that I was connecting to had a max resolution of 1600x900, while the home desktop I was connecting from was operating at 1920x1080.

On the black-screen RDP, I did the following to resolve it:

  1. Closed the black-screen RDP using the "x" on the blue bar on top.

  2. Explicitly set the display to 1600x900 in the RDP client, then connected.

1600x900 RDP

  1. While that session was still open, started another RDP client to the same machine, this time with display set to 'Large'.

  2. The first RDP session automatically ended, the second one started at my current monitor's full resolution of 1920x1080.

SNag
  • 1,082
  • 1
  • 10
  • 12
  • While being the simplest, this solution seems to work well. I must also add that, in my case I didn't have to keep the rdp session screen open. I simply closed rdp client, changed the resolution and restarted. – Akanni Mar 16 '21 at 09:43
2

In my case it was python miniconda, which has known issue spoiling PATH on linux in .bashrc, some details are in my answer

stiv
  • 79
  • 1
  • 2
  • 13
2

Repeating a workaround documented by @johnny Keeton above, proposing as answer because it worked for me when the other solutions above did not...

tasklist /svc | findstr /C:TermService to identify the Process ID, and
taskkill /F /PID [process_id] to end the process
net start TermService to restart (though it will restart on its own in my experience)

– Johnny Keeton Aug 24 '16 at 2:03

BobHy
  • 200
  • 4
1

This might not help but I solved it by turning down the resolution. The problem occured as the monitor I was connecting from was 2560x1440, and the remote computer wouldn't allow that. Turning it down to 1920x1080 worked fine and I am now connected with everything showing.

Unknown
  • 11
  • 1
1

I had this issue since I was having different DPI. On my laptop I had DPI set to 125% while a computer I was connecting had 100%. Setting DPI to 100% on laptop solved the problem.

Stanislav Berkov
  • 111
  • 3
1

When I have this issue I move the RDP screen to my default screen and maximize the screen. The RDP screen should no longer be black. I then move the RDP to my secondary screen. Not the best work around, but it works.

Roger
  • 121
  • 3
1

Had the same issue. The following worked out for me:

  1. Right-click the current Graphics item in Device manager, and select "Update driver".
  2. Choose "Browse my computer for driver software"
  3. Choose "Let me pick from a list of device drivers"
  4. Select "Microsoft Basic Display Adapter"
Adi Lester
  • 111
  • 5
1

I had this issue after I installed Oracle VM and a Lubuntu image. Right after the Oracle installation everything was fine and I also managed to install Lubuntu. I've done everything through RDC. Suddenly, the screen went black. I haven't restarted the computer or done anything worth mentioning at all, it just happened. This all happened in one single session.

I then tried restarting the computer manually, I tried all of the above settings which helped other people and I also uninstalled Oracle VM. Nothing helped.

In the end, I restored my computer to the state before I installed Oracle VM with a restore point that was generated automatically by my computer. Now RDC works again and I'm able to see the screen.

tl;dr: use a restore point if RDC used to work but doesn't work anymore

GChuf
  • 1,151
  • 9
  • 21
1

One part of SNag's answer is enough to work for me to workaround the issue: connect with another instance of Remote Desktop while the one with the black screen is still active.

Charles Savoie
  • 21
  • 2
  • This does not provide an answer to the question. Once you have sufficient [reputation](https://superuser.com/help/whats-reputation) you will be able to [comment on any post](https://superuser.com/help/privileges/comment); instead, [provide answers that don't require clarification from the asker](https://meta.stackexchange.com/questions/214173/why-do-i-need-50-reputation-to-comment-what-can-i-do-instead). - [From Review](/review/late-answers/1141289) – Toto Aug 19 '22 at 10:29
  • 1
    @Toto respectfully, it does provide an answer: "connect with another instance of Remote Desktop while the one with the black screen is still active." It is much more succinct and less time consuming to execute than the answer I give credit to (SNag's), and I don't see how it requires any clarification as the answer is complete and sufficient to work around the issue in my case. Please clarify your comment, specifically how it does not provide an answer to the question. – Charles Savoie Aug 24 '22 at 08:49
1

None of the other answers worked for me, but I did eventually find a solution. For reasons that are unclear what make the difference was disabling sharing of printers and smart cards in the RDP settings.

user3241
  • 315
  • 1
  • 9
0

On the remote system remove the Hidden - Microsoft Remote desktop Display Adapter - from the Device Manager Display Adapters listing, restart the remote system.

user88859
  • 11
  • 1
  • Avoid posting answers to old questions that already have well received answers unless you have something substantial and new to add. – Toto Nov 14 '22 at 15:11