Windows – Can’t run Hyper-V, but all hardware indicate that it’s good to go

bioshyper-vwindows 8.1

I'm trying to get my Hyper-V to work on my home computer. As I see it, all my hardware supports Virtualization and the software SecurAble is saying Good to go. Yes in Hardware D.E.P. and Yes to Hardware Virtualization.

My Motherboard is GA-Z68X-UD3H-B3 and my CPU is Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (8 CPUs), ~3.7GHz. BIOS is updated and factory defaults after update.
Virtualization is enabled in the BIOS too.

I found this post about my motherboard: Does VT-d need hardware support (besides the CPU)?
And as I read it, I can run Hyper-V. But when I start my virtual machine I get the message:

Virtual Machine 'Name os Hyper-V machine' could not be started because the hypervisor is not running.

The message indicates that I haven't enabled all settings for virtualization, but I can't see what that is now, and therefor asking for help here 🙂

Best Answer

After a long time looking at this issue, and not being able to find a solution for it, I found a solution for the issue and it solved my problem.

Source for solution: http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/01/19/hyper-v-virtual-machines-do-not-start-after-using-startup-repair.aspx

Title: Hyper-V virtual machines do not start after using Startup Repair

Over the weekend, I attempted to reconfigure some of the drives in my Hyper-V server at home. Note that I said attempted. I ran into hardware issues and ended up having to revert back to my old configuration - but somehow in all of this – I broke my system disk.

Specifically it would not boot any more.

This did not phase me because I knew that the excellent startup repair tool in Windows would soon have me up and running – which it did.

But I was surprised to find that when my system did finally boot – none of my virtual machines started up. When I tried to start the virtual machines manually, I was informed that the hypervisor was not running.

After scratching my head for a moment, I realized what had happened. Startup repair had rebuilt my boot configuration data store to get my system up and running. But it did not know that Hyper-V needs to have some specific settings enabled in the boot configuration data store in order to start the hypervisor.

I quickly opened an administrative command prompt and ran the following command:

bcdedit /set hypervisorlaunchtype auto

After that I rebooted the system and successfully started my virtual machines.

Cheers, Ben

The solution was this command line below and a computer restart:

Related Question