Hyper-V Broken after Feature Update

Question

Hello,

Last night the "Feature Update" for Windows 10 installed on my workstation (while I was asleep) and this morning after the reboot, most of my Hyper-V VMs are no longer appearing in Hyper-V manager.

I've done some research and tried a number of different thing suggested on various forum posts and I can't seem to get even a fraction of my VM's back up and running again.

It looks like a reboot was forced without shutting down the VM's first which has somehow corrupted my environment. I'm seeing unusual behaviour such as:

a) I can re-import some VMs back into Hyper-V and they run fine.

b) Other VMs fail to import.

c) Some VMs import successfully but fail to start.

d) Most unusually, some VMs import successfully but after importing they are not shown in the list and they cause other completely separate VMs being removed from the list.

Has this update not only destroyed my machine but half of the virtual machines I've got running on it? Any advice on what I can do to recover?

Regards,

Keith

<Moved from:      Windows / Windows 10 / Windows update, recovery, & backup>

Answer 1

Hi Keith,

Based on the description of your issue, it looks like there might be some issues in terms of how your Hyper-V VMs interacts with the newly updated Windows 10 that caused corruptions. This is something that our members from Technet forums may better be able to assist you with as they are knowledgeable in handling Hyper-V on Windows 10 concerns.

On another note, we've found a thread that can be related to your issue. Kindly see this Technet thread with some members that shared some answers regarding the Hyper-V concern. Though they've provided some thoughts from last year, it's worth taking a shot. Otherwise, it would be best to consult with people from Technet forums for further troubleshooting. Our engineers and developers would be looking further into this concern once you posted your concern.

Kind regards.