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

VegaDiscoveries · 05 Sep 2019

I have a customer who had this exact problem. After trying everything mentioned here (plus more) - the crashing of the VM persisted. After 4 hours we ended up restoring a backup from prior to the Windows update and set the vm to defer updates.

We are anxious to hear if Microsoft gets this resolved - or if a better fix is identified.

Ben Hastings · 05 Sep 2019

Techface said:

Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Remote Session Environment -> Using WDDM Remote Desktop Connection Video Drivers -> set to DISABLED

I recommend to do it like so rather than editing the registry like I posted earlier. Even though it should come down to the same effect.

Note: The setting needs a reboot to be effective!

@Techface Good to know which update causes it. I wasn't sure but it couldn't have been there all along since 1903 was released. If memory serves, the troubles started only a few weeks ago in my case.

AjN3806 · 14 Sep 2019

MontyP said:

Thanks for that tip.
In the mean while, MS released (in the last 24 hrs) KB4512941 as a follow on to KB4512508. I tried it to see if it fixed the subject problem but, unfortunately, it didn't. -> Roll back KB4512508 and disable updates seems to be the way to go for now.

Has this been fixed properly by Microsoft yet?
I've just stumbled across this problem in the last couple of days when my Hyper-V Windows 10 VM upgraded to 1903. My Hyper-V Host however was still on 1803, which I'm upgrading now manually to 1903. KB4512508 isn't currently installed on my host, but I guess it must be on the VM...no it's not? What now....

Code:

Source        Description      HotFixID      InstalledBy          InstalledOn
------        -----------      --------      -----------          -----------
AJNDESKTOPQA  Security Update  KB4515383     NT AUTHORITY\SYSTEM  14/09/2019 12:00:00 AM
AJNDESKTOPQA  Update           KB4515384     NT AUTHORITY\SYSTEM  14/09/2019 12:00:00 AM

The VM doesn't have internet either? There's no DNS returned with ipconfig /all and adding them manually doesn't work either?

Code:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : AjNDesktopQA
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : gateway

Ethernet adapter Ethernet 3:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : TAP-Windows Adapter V9
   Physical Address. . . . . . . . . : 00-FF-9E-87-EF-E1
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 4:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter #2
   Physical Address. . . . . . . . . : 00-15-5D-01-01-0C
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
<snip>
   IPv4 Address. . . . . . . . . . . : 192.168.0.26(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, 14 September 2019 11:44:05 PM
   Lease Expires . . . . . . . . . . : Sunday, 15 September 2019 12:44:19 AM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 385881437
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-0E-82-5F-00-15-5D-01-01-0C
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VPN Client Adapter - VPN
   Physical Address. . . . . . . . . : 00-AC-84-1F-62-F1
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

gurkburk · 18 Sep 2019

I can confirm having this problem. Seems to be related to enhanced sessions since August patch.
This leads me to believe when MS fixed the Bluekeep vulnerability they also broke RDP connections to HyperV guests.
I used to be able to "save" a machine in running state and just restore and continue where I left of.
Now it all just hangs and productivity is down.

Reverting to older versions would make me vulnerable to Bluekeep and put my host at risk since I analyze malware in the guests. Is my only way forward to switch virtualization environment ?

win10k · 18 Sep 2019

I've been pulling my hair out for the past month dealing with this issue since upgrading to 1903. I was about to downgrade to 1803 until I found the workaround to disable WDDM. Hoping MS will fix the issue properly so I can revert back to using WDDM which is supposed to be better/faster for RDP.

Interestingly, I don't have this issue with Windows Server (2016 or 2019) using latest builds.

AjN3806 · 29 Sep 2019

This is still a problem that remains un-resolved for my VM at least. I had disabled Windows Updates and was working fine on 1803, until I accidentally left the VM running un-attended for a couple of days, and Windows Updates fixed itself, and upgraded and the problem returned.

MontyP · 04 Oct 2019

I'd left a Win10 1903 system running with WDDM disabled via local group policy but when investigating why the VM had once again become problematic, found the policy had reverted back to 'Not Configured'.

The only updates logged recently are daily antivirus definition updates.

Can anyone shed light on why this policy would revert without help given it's a stand alone machine?

buckmurdock · 11 Oct 2019

Techface said:

Customize the GPO to use WDDM XDDM for RDP connections:
Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Remote Session Environment -> Using WDDM Remote Desktop Connection Video Drivers -> set to DISABLED

This issue has been driving me nuts and your solution fixed it. Thank you for sharing this!

gqchris · 22 Oct 2019

AjN3806 said:

This is still a problem that remains un-resolved for my VM at least. I had disabled Windows Updates and was working fine on 1803, until I accidentally left the VM running un-attended for a couple of days, and Windows Updates fixed itself, and upgraded and the problem returned.

Same here. I pushed my windows updates back and they triggered again, and I am back to square one. Has anyone made any headway on this? Unbelievable this is continuing.

DavidPatterson · 23 Oct 2019

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.