Windows 7: Black Screen on Login after Remote Desktop sessions

Hi,
I connect to my work computer through a VPN and remote desktop, and often times remote desktop (I use NLA) works once, but after the first disconnect I can't login remotely. Power settings on the computer are set so it never goes asleep and never turns off the display.

In addition, when this happens, I find the computer has a black screen either before or after login when I go into my office to login directly to the computer.

This problem seems to occur on several computers, including on Win 7 Pro x32 and x64.




Thanks,
JB

I use MS RDP and have no issues like that... but it does rearrange all my desktop icons if i remote in from a PC with a 4:3 monitor (I have a 16:10 @ home)... that's very annoying!

I have the same trouble with Windows Server 2008 R2, and am finally narrowing it down to remote desktop connections.

One of the symptoms I see is that I'm getting no monitor sync on my primary desktop monitor for my multi-mon, but the secondary is fine. At the log-in, I can move the mouse way over from the primary monitor and the cursor appears on a black-background on the secondary.

Additionally I can occasionally get the keystroke combo right to "blind" log-in, and then everything is fine - the monitor is re-enabled. Otherwise I've occasionally been able to activate the screen reader.

I've had similar problems after closing a remote desktop connection where I get a black screen with only a mouse cursor from both the console itself and from further remote desktop connections. Microsoft KB 555840 seemed to describe similar problems - (support.microsoft.com/kb/555840). I was able to resolve by remoting in a second time but using a different screen resolution (e.g. 640x480) on the remote desktop connection than the one I used previously. I think this may clear the bitmap cache referenced in the Microsoft KB article.

For what it is worth, when I experience the black screen of agony through remote desktop, I usually get past it by hitting ctrl-alt-home or whatever combination you have for getting the control screen and select logout. That should bring up a menu showing what programs prevent a logout, just select cancel and there you have it, a fixed desktop...

For me, it was accidentally leaving a full screen video game up on the PC I was remoting to. CTRL-ALT-END into task manager, use that to close the application.

While kind of embarassing, I just wanted to add my problem/solution, as this is the number 1 result on google. Hopefully people can figure it out otherwise.

Thank you, casualblair, for posting your solution. CTRL-ALT-END worked fantastically for me even though I don't think I had anything full screen. The moment the task manager was launched, I could see everything else.

Just to throw it out there, TeamViewer didn't work either during this problem (just wouldn't connect, no error messages). I had to restart it once I remote desktoped in.

I had this or a similar problem recently after installing a few apps. I wasn't sure which one was the culprit--f.lux and RightNow CX to name two of them.

After remoting in and getting the inevitable black screen, I loaded compmgmt.msc (right-click My Computer / Manage) on the client machine (the one I connected from), then connected to the remote machine (the one I connected to) and looked at the system events (System Tools / Event Viewer / Windows Logs / System). I noticed within seconds of connecting, the Application Experience service started.

I stopped and disabled (Services and Applications / Services / double-click "Application Experience", choose Disabled, click Stop, then click OK when done) this service, then reconnected. It has worked fine since.

This situation happens when I remote it using '"all my monitors for the remote session" under the Display tab. If I close the RDC without logging off, and then login with a different screen configuration (a different monitor from home) the I get the Black Screen of Death. Ctrl-Shift-End doesn't work in my case.
My experience is different if using a Terminal Server versus standard machine. With the Standard machine I have to close and reopen the RDC, and change to an explicit resolution (not 'fuill screen') under the Display tab. It will come up correctly, and then I have to repeat the process to get "all my monitors..."
For out Terminal server, it will work with explicit resolution, but to the "all my monitors..." I had to Log Off, garggle, spit, repeat.

I swear I posted in here.... anyway, I had this problem and found this fix.

http://knowledge.alzwea.com/?p=330