After August update Hyper-v Win10VM crashes when connecting via RDP

DavidPatterson said:

This may sound weird, but check to see how many virtual processors you are using. My guess it is only one. I have similar issues with the VM hanging when there is only 1 virtual processor. Up it to 2 and see if that helps.

Thanks David, yes that did the trick. I worked on it yesterday after reading the GPO fix and that was mentioned also. Id dint know if it was the GPO that fixed or the increase of Virtual Processors, but they are working fine now and 0% CPU usage and east to RDP in again. Thanks. I have paused updates, but should be fine I'm hoping.

DavidPatterson said:

This may sound weird, but check to see how many virtual processors you are using. My guess it is only one. I have similar issues with the VM hanging when there is only 1 virtual processor. Up it to 2 and see if that helps.

This is the correct answer, and the only thing that helped me. I've been battling this problem for many weeks. Increase the virtual processors. Just do it, it works.

I believe 1909 fixed this problem for me but I have not seen anyone else confirm this. I attempted disconnect from RDP from a VM without applying the group policy fix. It reconnected without problems after 1909 patch.

I also read that updating GPU drivers could fix the problem (and I updated my GPU drivers as well).
Can anyone else confirm this fixed on 1909 ?

gurkburk said:

I believe 1909 fixed this problem for me but I have not seen anyone else confirm this. I attempted disconnect from RDP from a VM without applying the group policy fix. It reconnected without problems after 1909 patch.

I also read that updating GPU drivers could fix the problem (and I updated my GPU drivers as well).
Can anyone else confirm this fixed on 1909 ?

I just updated to 1909, undid the Group Policy fix, and I'm also not having the issue anymore.

It seems that updating to 1909 is the ticket.

I've just completed some upgrade work and found that without updating 1903 to 1909 but simply by updating AMD chipset and video drivers to the latest, the RDP/Hyper-V problem has fixed itself (even with VM having only 1 vCPU thread).

Was: AMD Radeon v19.10.22 (video driver: v26.20.11022.3 - 4/6/2019)
Upgraded to: AMD Radeon v19.11.3 (video driver: v26.20.13031.18002 - 15/11/2019)
& AMD Chipset v1.9.27.1033 - 27-09-2019

I then upgraded Windows from 1903 to 1909 and it didn't break the fix! (Small mercies!)
-> I therefore wonder if there is actually a fix in 1909 or if the 'fix' is due to a driver update occurring behind the scenes.

I guess AMD tweaked their driver to track Microsoft's constantly changing the latest iteration of the last "version" of Windows*

* Except when we choose to modify it as will, on the fly in ways we won't warn you of!

This is interesting because most of you get stuck at 12% CPU utilization, but my Win10 VM gets stuck at 24% CPU utilization every time.

My physical system is 16GB.
My Win10 VM is 4GB (set to dynamic if it matters).

Does this help? Do you guys that are getting stuck at 12% have half of either of those?

I am running the 1909 update and this still happens. Happened before and after the update. Only thing that works is either turn-off or reset of the VM. Can't do a proper shutdown.

Host OS is also 1909 Win10 by the way. If it matters.

- - - Updated - - -

DO THIS:

Hyper-V Guests with Windows 10 (1903) hangs when using Enhanced Session/RDP? | Microsoft Security Solutions