Windows 10: Hyper-V feature failing to start VMSwitch, looks like a broken driver?

I've been running docker on my computer for weeks, but yesterday my Hyper-V installation broke and docker fails to start. My computer was shut-off the previous night unexpectedly, so that might have been the cause. After digging in further Hyper-V manager cant load the VM switch manager. The failed drivers seem to point to this isn't related to Docker at all as I've also completely uninstalled docker and am still getting errors. I can open Hyper-V Manager, but clicking on Virtual Switch Manager errors with "An error occurred while trying to retrieve a list of virtual switches. The generic operation on computer 'XXX' failed: generic failure." I cant create VMs because VMSwitch is failing to start.


Event logs show the following

Warning (source Kernel-PnP): The driver \Driver\VMSP failed to load for the device ROOT\VMS_VSMP\0000.
Error (source Hyper-V-VmSwitch): Failed to initialize VMSwitch driver due to error {Operation Failed}

Removing and re-adding Hyper-V features (Turn Windows features on and off) did not do anything

Tried the command and it did not resolve the issue: netcfg -d


I'm on Windows 10 Enterprise 1809

:)

 

Hyper-V Broken after Feature Update

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>

 

Event 22:Hyper-V VMSWITCH/Event 27 i40eb Network Link is disconnected.

Hello Team,

I have Windows Server 2016 with Hyper-V cluster role installed and I,m using network Team.

When the server starts I receive a error - - in system event log. Event 22:Hyper-V VMSWITCH&Event 27 i40eb Network Link is disconnected.

kindly help to fix the issue.

 

Hyper V deativication

Hi Geoffrey,

Hyper-V lets you run an operating system or computer system as a virtual machine on Windows. Before proceeding in disabling
Hyper-V, please create a backup of your files for security purposes.

To disable Hyper-V, please follow the steps below:

• On the Cortana search box, type Turn Windows Features on or off and press
  Enter.
• Look for the Hyper-V folder.
• Uncheck the tick-box next to the main Hyper-V folder and click
  OK.
• Restart your PC.

Should you have further questions, please let us know.