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.
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 processid to end the process. Start TermService using net start TermService.
I am still working on a solution.–Aug 24 '16 at 2:03. Remote Desktop – Black Screen Of Death The IssueUsing 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).
Windows 10 1903 (May update) black screen with Remote Desktop: I upgraded my secondary machine from 1809 to 1903. When I access it now using Remote Desktop all I get is a black screen in the RDP windows. I then upgraded my primary machine to 1903 hoping that would help, but no. Fortunately I also have GoToAssist installed so I was able.
While logged in and stuck on the black screen of death. 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.
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.
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. 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. 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.
I have a Windows 2008 Server that I have been connecting to once a month remotely to apply OS updates. I'm sorry, I didn't have an email address assigned after the recent change in the Microsoft message boards so I did not receive notification of this reply.This problem also occurred logging directly onto the server.
So it was not an RDP problem. When we logged on at the physical server, the screen went black after the welcome message displayed. However, the mouse cursor was still visibleand functional. We had no option at that point except to perform a hard reboot. When the server rebooted, everything worked normally.Rob Kraft. I have the same problem. My system is windows server2008 enterprise without hyper-v, run as a guest OS on top of HYPER-V, I send ctrl+alt+del get to login screen, after I login as administrator, I get black screen except the mouse point on the screen, Ican login as other account get normal screen, only administrator's account has this problem.
After I rebooted the guest OS, problem dissappeared, I can login as administrator and get normal screen by using RDP. But after a two weeks todaythis problem is coming back again. There is no change to the system, don't know what is cauing the problem and how to prevent?Thanks.Edward Hua. Hello all,I am having the same issue - only CTRL-ALT-END doesn't do anything for me. CTRL-ALT-DEL only lets me open task manager on my client computer, not in the remote session - this is even when choosing the 'Apply Windows key combinations' to be 'On the remotecomputer'.I'm running Windows 7, with dual screen (I've tried telling it to use only one monitor) - but I seem to be ok to remote in using my wifes username and password. It is only my own.When I press buttons (such as CTRL ALT DEL/END) I can hear a sound like the 'Default Beep' sound in windows.Tried a lot of things. I do feel like it sits on the 'Welcome' message for far longer than it normally does.As per another thread I found on the same issue, I tried connecting with a smaller resolution to reset the bitmap cache (as per support.microsoft.com/kb/555840).In the same thread someone posted they had the problem occur because they left a game on their client computer in full-screen mode.
I had a game open, tried closing that but no luck.I notice I have some updates pending install, will try installing those and restarting.Update: Restart didn't work. Update was only a security update for Silverlight. Am now updating graphics drivers but I doubt this will work because as mentioned above I can log in fine using my wifes username/password. I may need to remote in with hersand restart the server.