33

I've created and run Hyper-V guests on this machine in the past. VT extensions are enabled in the BIOS; no changes made there. I've changed my boot device order recently.

How can I ensure that Hyper-V's host hypervisor is started on Windows startup?

When attempting to start a VM, the Hyper-V Manager error shows:

An error occurred while attempting to start the selected virtual machine(s).

Failed to restore virtual machine state.

Virtual machine 'Windows 10 Tech Preview' could not be started because the hypervisor is not running.

enter image description here

The Hyper-V Virtual Machine Management service is set to Automatic.

enter image description here

I've previously run bcdedit /set hypervisorlaunchtype auto as Administrator.

No other VM products like VMWare or Virtualbox is installed.

  • Check it in the services if it set to automatic at startup technet.microsoft.com/en-us/library/ee956894(v=ws.10).aspx – Scorpion99 Dec 29 '14 at 21:46
  • 1
    Have you got any other Hypervisors installed/running? ie: VirtualBox, or VMware? – Ƭᴇcʜιᴇ007 Dec 29 '14 at 21:59
  • Following up what @Ƭᴇcʜιᴇ007 mentioned, different hypervisors on your system can seriously mess your system up and they can conflict with each other. – AStopher Dec 29 '14 at 22:01
  • 2
    Because Hyper-V is a type 1 hypervisor, it has to be started before the Windows kernel, much like Xen. As such, bcdedit or similar tools are indeed your best bet. Fiddling with Windows Services, on the other hand, will solve nothing. Likewise, having VirtualBox or VMware installed won’t change anything. They will simply refuse to run when Hyper-V is enabled. – Daniel B Dec 29 '14 at 22:35
  • 2
    Actually, bcdedit /set hypervisorlaunchtype auto solved that for me + cross checking bios settings for virtualization and updating bios firmware. Running bcdedit again will confirm if the settings has been set. – Norman Apr 13 '16 at 18:26
40

I had exactly same problem and tips by Daniel B and Norman helped me: Running bcdedit alone revealed that hypervisorlaunchtype was indeed set to off so bcdedit /set hypervisorlaunchtype auto followed by a reboot did the trick.

I am reposting their comments as an answer to preserve them.

This was caused by (unsuccessful) attempt to run Android emulator from Android Studio.

  • 2
    Had same problem after cloning my system disk to new SSD by Samsung Data Migration utility. Using bcedit fixed the issue... – Michal Levý Sep 23 '17 at 8:14
  • Seems to fix the issue for me. thanks – FindOutIslamNow Apr 29 '18 at 8:18
  • Cause for me was cloning to a new drive as well. bcdedit "boot loader section" needs to say "hypervisorlaunchtype Auto". – Orangutech Mar 16 at 4:48
14

Since I've tried to install Docker for Windows, I found out that my CPU just can't run Hyper-V although I could install it.

This page explains that Windows 8 Hyper-V Client (and I think Windows 10 too) requires a SLAT-capable CPU to run. To check your CPU capabilities, use the Coreinfo utility (https://technet.microsoft.com/en-us/sysinternals/cc835722) with the option -v, the '-' character indicates that the feature is missing. Here you can see my CPU is missing every feature needed to run Hyper-V

Maybe your CPU lacks some features too, hope it helps !

protected by Community Nov 29 '16 at 13:04

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.