Hyper-V 2019: no VM on reboot, have to restart vmms

Question

Hi

We have one Hyper-V core server with a issue when it reboots: VM is missing.

In the event viewer, there is 2 errors:

• Microsoft-Windows-Hyper-V-VMMS, EventID 22052
• Microsoft-Windows-Hyper-V-VMMS, EventID 16300

With a simple "Restart-Service vmms", VM is back...

???

Answer 1

Hi,
Try to set the Hyper-V VMMS start up type to “Automatic (delayed start)” and check again.
Please turn off or uninstall any third-party AV tools on your host.

Best Regards,
Mico Mi

Answer 2

Hi，
I’m glad that you’ve solved your problem.
I had such issue happen also, and a reboot of VMMS always fixed it.
Besides, I found a similar thread and it’s worth checking Ian Carson’s post.

Also wanted to add our experience as well. In the end for us the disappearing VM problem turned out to be corrupted configuration xml files for the VM's. Specifically a single missing ">" in the last line i.e. "</configuration" instead of "</configuration>"
We shut down the Hyper V service, opened the xml file in notepad and added the missing bracket and saved the file, then restarted the base machine. All VM's were online when the restart was complete.

Thanks for your time!
Best Regards,
Mico Mi

-----------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Hi

The issue is not fixed! It happens on every reboot...
XML corruption is something I have think about, but:

• this would not be fixed by a restart of VMMS service !
• we are using a Generation2 VM, so no XML file here

Regards
Clement
SimpleRezo

Answer 4

Hi,
If you create a new VM and point the new VM to the existing VHDX, will this issue still exist?
Best Regards,
Mico Mi

Answer 5

Hi

First time it happens we have recreated the VM and the issue has happened again.

Regards