Quick Fix: Virtual Machine Could Not Be Started Because The Hypervisor Is Not Running

I got smacked with this error message today which says the virtual machine could not be started because the hypervisor is not running as seen below:

hypervisor not running small

I double checked Intel-VTx and DEP was enabled in the BIOS and then discovered there were no event logs under Application and Services Logs > Microsoft > Windows > Hyper-V-Hypervisor in the Event Viewer. I would’ve thought an event or two should be logged since I enabled the hyper-v feature and also created a virtual machine.

Fortunately there’s a short one-liner I ran in an elevated command prompt to set the hypervisor to launch upon boot up:

bcdedit /set HypervisorLaunchType auto

set hypervisor auto

You’d think the hypervisor would be set to launch automatically after having enabled the feature in the first place, right?

My experience with Hyper-V up to now has been on the server side with the fully fledged hypervisor on Windows Server 2012 R2. So I decided to make use of client hyper-v on my Windows 10 computer for building reference images when I hit this snag

Advertisements

6 thoughts on “Quick Fix: Virtual Machine Could Not Be Started Because The Hypervisor Is Not Running

  1. Hello,
    I tried to configure it but I get some errors as follows:

    The boot configuration data store could not be opened.

    Access is denied.

    Any help will be appreciated

  2. Thank you – worked for me. Not sure exactly what stage of the below stopped it working for me in the first place.

    Long story short, but TLDR; for most – Lenovo running Windows 10, hadn’t looked at using hyper-v for a long time, turned it on in BIOS, installed and ran 7 and 10 VMs successfully.

    Then found that launching the previously installed Leapdroid (on the host) would blue screen the computer. Turned it off in BIOS, used Leapdroid successfully, turned it back on in BIOS, launched Leapdroid and blue screened. That problem at least identified, if not solved.

    Turned it back on BIOS, tried to launch virtual machines and started getting the message in the title of the article.
    Ran your suggested solution, all good.
    Leapdroid now stopped development anyway as the guys joined Google and orphaned it, so now need to find a new Android VM solution for those rare occasions.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s