Ask the Community
Groups
Error: Virtual Machine could not be started because the hypervisor is not running - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>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.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h3 data-id="purpose">Purpose</h3> <p>To explain how to resolve an error that can occur after recovering a Hyper-V server using the integrated bare metal recovery feature</p> <h3 data-id="description">Description</h3> <p>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.”</p> <h3 data-id="resolution">Resolution</h3> <p>To resolve this issue, complete the following steps:</p> <ol><li>Run the following command on the Hyper-V server: <i>bcdedit /set hypervisorlaunchtype Auto</i> </li> <li>Reboot the Hyper-V server.</li> <li>You can now start the VMs.</li> </ol><h3 data-id="additional-information">Additional Information</h3> <p>For more information about the integrated bare metal recovery feature, see <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fwww.unitrends.com%2Fdocuments%2Flegacy-rs-ueb-admin-guide%2Fdefault.htm%23cshid%3D1910">Windows integrated bare metal recovery</a> in the <i>Unitrends Administrator’s Guide</i>.</p> </article> </main>