Server is working perfectly but when I do RDC screen is only black. This happened before and I fixed it by powering off the server via KVM/IP, but I don't want do that again. How can I fix this issue.

OS: Windows Server 2008 R2 Web Edition SP1

12 Answers 12


I've seen this happen before 3 or 4 times when a user just closes their session instead of logging out of it. Please try the things in the KB article above under JohnThePro's answer.


This often happens to me when I connect to Windows 7 x64 machine. Solution that I use is pressing Ctrl-Alt-End in the RDP window. This brings up the "lock your computer" screen. Lock-Unlock and you are in!

  • This does the job. Ctrl-Alt-End and started task manager. – MYGz Jan 23 '19 at 7:15
  • You're probably not on stack anymore but thank you, it still work just fine in 2019. I wasn't sure what to do since Ctrl-Alt-Del was not working on the remote desktop. – Gainz Nov 5 '19 at 19:25
  • 1
    @Gainz - I'm still here, not as often as before though ;) – demp Nov 7 '19 at 12:03

Here is how to work around the issue. All the above else failed for me.

I am using Windows 7 home Edition.

Before Connecting To RDP,

Click the link with the words "Remote desktop Connection" Link. Ensure you click the link with these words, not the actual URL or saved RDP name.

When the RDP window opens up, click the Options button at the bottom.

Change to Display properties by clicking the Display Tab.

On the Display Configuration Panel, Change the Screen Resolution slightly each time before clicking Connect.

This will ensure your black screen stays away.


Next time it crops up, there is a specific KB article about this issue.



While logon into a remote server by using remote desktop, the following issues may occur:

  1. A slow logon process.
  2. A black screen appear for a while, until the regular desktop appear.


  1. Disable the use of "Bitmap Caching" on the RDP client.
  2. Verity that the server, client and the network equipment using the "MTU" size.

Press CTRL + ALT + END and hit the Task manager. Log off and log in back again. It happens if user disconnects the session but not log off properly.


Tryto get it in full screen and then do an "alt-tab." Maybe it's stuck in a weird application. This technique worked for me once.

  • does not solve. anyway i did a kvm/ip power off and power on since i needed a solution asap. so can not test answers anymore :( – MonsterMMORPG Jan 9 '11 at 22:27

Have you tried logging in as a different user? This happens sometimes on my terminal when a session gets stuck logging out. Ending the session from the remote desktops tool fixes it.


Found this article it list quite alot of possible reasons and their solutions regarding this issue, I was able to fix my issue with by enabling sessions limits as described in the article. http://www.grishbi.com/2015/01/rdp-black-screen/

  • So what actual change did you implement? That article may disappear next week, next month, or next year. – Hyppy Jan 21 '15 at 19:40
  • @karan Like Hyppy mentioned - "What actually fixed the problem?" This site is a great tool, in that information referenced elsewhere can still be found, as long as someone puts that information in the answer. – Signal15 Jan 21 '15 at 20:15

There is also another KB article with a patch for Windows Server 2008 R2.


I installed this patch to solve the issue.

When a user session is disconnected, the black screen showed up occasionnaly on reconnection.

  • This linked support item is for Windows Server 2008 R2 not for Windows Server 2012 as mentioned in the answer. – Fiasco Labs Jan 29 '15 at 5:59
  • Sorry, this was a typo. We are using only Windows 2008 R2. – Lorenz Meyer Jan 29 '15 at 6:14

I had a similar issue remoting into a desktop running Windows 10. The desktop had 2 monitors, one plugged into the on-board graphics and one in a dedicated graphics card. Unplugging the monitor that was using the on-board graphics fixed the issue... presumably something in one of the drivers isn't playing nicely.


UAC. UAC is the problem. That bullshit, yes. In my case the first login was successful and working, but any other consecutive attempt was not working. I was getting either a flickering(unusable) or completely black screen, on RDP or directly on the console of the 2012 R2 server. In the Application eventlogs there were lots of errors with eventID 1000(Faulting application name: explorer.exe, version: 6.3.9600.17415, time stamp: 0x54503a3a Faulting module name: unknown). UAC was disabled. I just enabled it, reboot the server, and then I was able to log in with multiple working sessions. I even disabled back UAC and reboot the server again and things were working normally. Beware of UAC :)


I really don't know this happened to my server but I clicked the blank screen and typed in my password. Boom, it opened up. So I think, in my case, the login screen was not being displayed.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.