Remote Desktop, after logoff, black screen.


  • I am able to Remote Desktop fine from a laptop running Windows 7 into my desktop running Windows 7, the problem is that once I LOGOFF (or disconnect) and go to my desktop, all I see is a black screen with the mouse movement.  CTRL-ALT-DEL does nothing.  I can go back to the laptop and RD into my desktop and it lets me login just fine.  But I have restart the system again by pressing the POWER BUTTON (soft, not hard 4 sec) and it goes to shut down, with nothing to show on the screen other than black and mouse cursor.

    anything I'm doing wrong?
    Tuesday, May 05, 2009 9:21 AM


All replies

  • Are you able to get the task manager by pressing CTRL+SHIFT+ESC?
    If possible: try to click File->New Task (Run...) and then type explorer.exe to se if explorer has shut down...
    Tuesday, May 05, 2009 9:30 AM
  • I think you should update your vedio card driver. find the driver for windows vista and install it.
    Tuesday, May 05, 2009 11:46 AM
  • I have a similar problem. After I log off a session, my HTPC won't send a signal to my TV unless I go into stand by and turn on power again. My video drivers are the latest from NVIDIA. Anything known how to solve that bug?
    Saturday, May 16, 2009 1:55 PM
  • Hi JK,

    It is not a bug. This is a hardware compatibility issue.

    Currently NVIDIA has provided some Windows 7 RC drivers, please check if you have installed correct drive.

    Arthur Xie - MSFT
    Monday, May 18, 2009 4:32 AM
  • Hi! I installed the latest driver for Windows 7 (185.85). But yes, could be a driver issue. I'mjust  gonna wait for the next release and see if it's fixed.
    Monday, May 18, 2009 10:07 AM
  • Nope, no chance, no reaction except for when I enter standby and turn on the PC again. Another problem I recently encountered: after logging into my system via Remote Desktop Client I got a blank black screen with nothing except a (oversized, because of my dpi-settings) mouse cursor. The only way I could solve the problem was to remove my PC from power. Anything known about this problem so far?
    Sunday, May 24, 2009 10:42 PM
  • I get the same problem randomly. When trying to login on my session I got black screen, CTRL+ALT+DEL does nothing. This problem occurs both on local and remote desktop connection

    I'm having the latest drivers from ATI  (HD 5770) for Windows 7 64 bits (Professionnal Edition)

    A scan for virus has been done and nothing has been detected.
    A scan for malware has been done and nothing has been detected.

    This is really annoying ! I never got this problem on Windows XP before... I'm beginning to think that I should not have to purchase Windows 7 !!!


    Wednesday, May 05, 2010 3:51 PM
  • Same problem here with ATI 5700. and Win 7 Pro X64. Going to swap out the video card for another brand and try it.
    Tuesday, May 18, 2010 1:08 AM
  • Same issue here too... ATI 5770 latest catalyst drivers, Win 7 Ult x64. Everything was fine then I had to reinstall Windows because of a corrupt boot record (which wasn't fixable as my files got corrupted in the process as well). I naturally installed the latest cat drivers on reinstall and bam, this happens.

    This really REALLY needs to be fixed.


    Tuesday, August 31, 2010 1:58 PM
  • This thread help me a lot to solve the problem.

    Read the thread of "Brian Grunkemeyer - MSFT - Friday, December 04, 2009 10:58 AM" and try the REGEDIT solution propose by Brian. After applying this trick, I have not had any trouble with this black screen annoyance.

    I hope it will help you


    Tuesday, August 31, 2010 3:51 PM
  • I have solved my issue.

    Let's assume you have all the latest drivers and patches, and all your hardware is generally functioning properly. You also don't have issue logging in normally, eg. black screen of death.

    Let's also assume that you have two monitors and when you go back to login to local computer after RDP disconnects, only one of your monitors wakes up from 'sleep' mode. The other monitor that wakes up is black screen but you can see your mouse if you move it there.

    So, since I have an ATI card, fire up the ATI Catalyst software and go to the desktops&displays section.

    In my case, the screens were reversed. My "Main" monitor was 2 and secondary was 1. I tried switching the cables around but it didn't matter, they would go back the same. I tried to have one monitor only plugged in, then do a detection, then plug second in, and it still didn't matter; they were always sticking to their backwards numbering. I tried to right-click on monitor and 'disable' using the ATI catalyst then enable, but that wouldn't take either.

    So finally, what worked is the following: in the bottom section of desktops&displays where it says "please select a display" right click on your primary monitor and disable it. Primary meaning the one you want to be 1 and is currently 2. Then right-click again and select "replace". Then right-click again and choose "extend". This was the only way to have my monitors how they are supposed to be. 

    Now when I RDP in, then disconnect, the proper monitor wakes up and I can see the login screen. The second monitor stays in the 'standby/sleep' mode. I think this is by design since the main login screen does not know how you want your monitors laid out and it only uses one monitor. This leads me to believe that the multi monitor configuration settings are per-user but the numbering of 1 and 2 is system wide, so you better make sure that 1 is primary in relation to the video card port.


    Hope this steers someone in the right direction, I couldn't find anyone with a decent solution and I suspect there are a few cases where the symptoms are similar but it's a completely different issue.




    Saturday, October 09, 2010 3:08 AM
  • I also found this to help.  I have been working on a deployment of about 150 windows 7 machines and found this to work 90% of the time.  However, there are still times when this method does not work.  Apart from updating the drivers from ATI, I'm not sure what else to try.  I have read all the change logs from the ATI driver updates and found no reference to this display issue.




    Friday, November 05, 2010 1:32 PM