Please log in or register to add a comment.
Please log in or register to answer this question.
The logs looked, but we saw nothing, neither on the host nor in virtual reality... I Play with the CPU settings, driver cut. Let's see how it will work.
UPD first day - flight normal.
Please log in or register to add a comment.
usually this happens when the host machine issues, that is, at the moment when the black screen "sags" performance, with virtuallock it is possible to determine the resource monitor under the CPU is the parameter %of the maximum, when there is a drawdown in % drops sharply, it can be seen if pomonitorit. Why is the drawdown you need to test with on the host machine, maybe all of the above
Please log in or register to add a comment.
You need to check the server logs and OS virtual machines, test equipment, installed driver [for guest OS].
Please log in or register to add a comment.
View the task Manager, well, in the end, the answer is likely to have in the log viewer either on the host or inside virtualos.
Please log in or register to add a comment.
1.to check the RAM for bithost. 2.the CPU time is occupied in the trash something [or percent of throws off the load and long time to resume from rest 0_o] 3.screw sags [perhaps in the multitude of virtuallock]
on tambourine in hand and dances around.
Please log in or register to add a comment.
Windows 10 RDP black screen was recently reported by several Microsoft users on the internet on different forums. Microsoft Windows Server 2019 includes several new features especially for Hyper-V and the Security in general [another topic for discussion later] and I have been working intensively with it for the last few weeks. On the other side from the client side, the latest Windows 10 update had some problems and Microsoft rolled it back and re-released it again late 2018. I was hesitant to roll it back to my main working laptop until i run full testing and check the community feedback.
Finally I had all my client machines updated to Windows 1809 where I use to administer my environment and run my demos. Recently I faced an issue with Windows 10 RDP black screen once connected my Windows 10 1809 to Server 2019 as follows:
When trying to RDP [Remote Desktop – MSTSC] from a Windows 10 client [1809] to a Windows server 2019 I get a black screen after entering my credentials and nothing happen except having the black screen for long time till the session ends. This will occur for new windows 10 1809 only so far.
Checking the event viewer on Server 2019 from Application and Service Logs – Microsoft – Windows – RemoteDesktopService-RdpCoreTS
I noticed the below two errors repeated every time the Windows 10 RDP black screen occurs after connecting to server 2019
- ‘Failed GetConnectionProperty’ in CUMRDPConnection::QueryProperty at 2884 err=[0x80004001]
- ‘Connection doesn’t support logon error redirector’ in CUMRDPConnection::GetLogonErrorRedirector at 4199 err=[0x80004001]
The problem is clearly in the URCP mode [Universal Rate Control Protocol] as there were several changes and updates done in 1809 and Server 2019 as per the link below. This protocol is used for Data Exchange between the remote desktop client and the server over UDP.
//msdn.microsoft.com/en-us/library/mt242356.aspx
Solution/Workaround
After investigating this issue with Microsoft they confirmed that its a reported issue and they are working on understanding the problem and issuing a permanent fix, the current available workaround for now is to stop the URCP connection mode by applying the following Registry key on your Windows server 2019.
- On your Server 2019, open the registry editor and navigate to HKLM\SOFTWARE\Microsoft\Terminal Server Client
- Create a new d-word [32-bit] value and name it UseURCP with decimal value of 0
Again this issue will only face Windows 10 1809 clients connected to Server 2019, if you are Windows 10 1803 or earlier or even Windows 7/8 you won’t face this problem.
Hopefully this post can help others facing the same issue.
-
What is the configuration of the VM? Can you share the details?
Was this post helpful? thumb_up thumb_down -
This sometimes happens close the window and reopen most of the time it will come back on
Was this post helpful? thumb_up thumb_down -
What's your build of Windows 10?
I know there's been Registry issues that cause this, but I'd try some other things before messing with that.
Do you have an updated video driver?
-
As it is right now you can even see in the preview pane that the computer is up and running but the big connected windows is just black.
//i.imgur.com/ZyRGL5s.png
I have win 10 1803.
I have the exact same behavior on two different machines. One with a quadro card the other with a 1070ti.
Im trying to setup a new VM so i have deleted and recreated it several times. Just default settings booting from network.
-
I dont really know what the problem was but I updated to win 1809 and the graphic cards driver and now it seems to work.
1 found this helpful thumb_up thumb_down
OK, So when I use RDC [Remote Desktop Connection] to connect to a remote machine, the screen is full of random black areas. The way I managed to resolve this was by unchecking Persistent bitmap caching, as illustrated here:
This same issue occurs when I open a Hyper-V VM console, and to manage that it is necessary not to use Enhanced session mode. This is set up in the Hyper-V Settings > Enhanced Session Mode Policy and Hyper-V Settings > Enhanced Session Mode.
This is what the screen looks like with enhanced session mode:
And this is the same screen with enhanced session mode turned off:
While these solutions do solve my immediate issue, which is not to have those pesky black rectangles, I wonder what could be the cause of this, and, more importantly, is there a way to resolve this issue without turning off enhanced session mode in Hyper-V, as I am really benefiting from the functionality it brings?
Thanks!