Error: Virtual Machine could not be started because the hypervisor is not running

SUMMARY

After recovering a Hyper-V server using the integrated bare metal recovery feature, you receive the error: Virtual Machine could not be started because the hypervisor is not running.

ISSUE

Purpose

To explain how to resolve an error that can occur after recovering a Hyper-V server using the integrated bare metal recovery feature

Description

After recovering a Hyper-V server, you could receive the following message when starting up its VMs:  “Virtual Machine could not be started because the hypervisor is not running.”

Resolution

To resolve this issue, complete the following steps:

  1. Run the following command on the Hyper-V server: bcdedit /set hypervisorlaunchtype Auto
  2. Reboot the Hyper-V server.
  3. You can now start the VMs.

Additional Information

For more information about the integrated bare metal recovery feature, see Windows integrated bare metal recovery in the Unitrends Administrator’s Guide.

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section