2

I just reinstalled all Hyper‑V features after disabling them for using another hypervisor that didn’t support pci‑e passthrough. There aren’t more details besides the virtual machine id. It’s happening with all virtual machines, even with the simplest case like above.

I know there are a lot of questions like this one which tells the issue has it’s root with nested virtualization, but in my case, the host Windows is running directly on the real hardware, and this is in the official virtmgmt.msc that the issue is happening as well as the Start-VM Powershell command.

How to get more details about the issue, like the said component which isn’t running ?

user2284570
  • 2,020

1 Answers1

2

After a few months of running in circles I found a fix for my problem with exactly the same symptoms. Hopefully this helps you or others.

I had SVM enabled, everything seemed to check out and should have worked. Hyper V feature as well as Virtual Machine Platform all uninstalled and reinstalled multiple times. Continued to have the "one of the Hyper-V components is not running" as well as other issues with WSL.

I found an error in the Event Viewer application under Applications and Service Logs->Microsoft->Windows->Hyper-V-VMMS->Admin. This error indicated "The virtualization infrastructure driver (VID) is not running." I checked device manager and found that the Microsoft Hyper-V Virtualization Infrastructure Driver was disabled. Enabled and everything started working.

If you don't have that exact error you might find something else in the Hyper-V event logs. Mine was getting this specific error upon reboot, and different errors when attempting to boot a VM.

Full disclosure I believe I updated this to windows 11 as a pseudo bare-metal VM running on unraid with PCI-e passthrough which may have caused my issue.

hybrdthry911
  • 121
  • 1