I am running several virtual machines on my laptop using Client Hyper-V. I don’t use them so much, but a few weeks ago I had to recognize that after starting my computer they are always shown as “off-critical”.
My search in the web only gave me results regarding Virtual Machines located on USB-Storage, which was actually leading me to the solution of my problem:
If VMs are located on a USB-Drive which is not connected during computer start-up, they will be shown in Hyper-V Manager as “off-critical”, because the VM Config files cannot be loaded.
This can be resolved by simply connecting the USB and restarting the Virtual Machine Management Service.
My VMs are located on a local partition. Now you would maybe ask why I think that this is the same problem, I will tell you:
The partition with the Virtual Machines is BitLocker protected.
So if I start my computer, the C Drive is being unlocked after typing my PIN and the TPM verification. The D Drive instead, will only be unlocked after the system start-up.
Somewhere in between this, the Virtual Machine Management Service is starting and looking for the XML files. As the partition is still encrypted, it cannot access the VM Config Files.
How to resolve?
I changed the Hyper-V Virtual Machine Management Service Start-Up Type to Automatic (Delayed Start).
With this setting my Virtual Machines are off (like supposed to), but not off-critical after I start my Laptop