Windows 7 remote desktop connection goes black

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 R2 server.

In the Application eventlogs there were lots of errors with eventID Faulting application name: explorer. UAC was disabled. I just enabled it, reboot the server, and then I was able to log in with multiple working sessions. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:.

Archived Forums. Windows 7 User Interface. Sign in to vote. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. Server is working perfectly but when I do RDC screen is only black. How can I fix this issue. I've seen this happen before 3 or 4 times when a user just closes their session instead of logging out of it. This often happens to me when I connect to Windows 7 x64 machine. This brings up the "lock your computer" screen.

Lock-Unlock and you are in! Click the link with the words "Remote desktop Connection" Link. Log off and log in back again. It happens if user disconnects the session but not log off properly. VMware console is black, RDP connection is black and it even happened with a physical server but only domain joined servers.

No way to get into safe mode: always black. Server works OK, services run normally and can connect remotely with powershell and WindowsAdminCentre and my usual remote tools. Just no GUI. So I've examined a server with process monitor procmon. Even if the cause of registry corruption may be different for different users, procmon showed me what was wrong.

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.

I had a similar issue remoting into a desktop running Windows 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 This technique worked for me once. 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 R2 server.

In the Application eventlogs there were lots of errors with eventID Faulting application name: explorer. 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. Many people, including me and many, have problems with this.