I have 5 virtual machines installed on my hyper V and i have not used them or hyper v in over a year. Tried to boot one up and i get 'virtual machine could not be started because the hypervisor is not running' error.

I have not changed any settings since iv used it, i have no idea why its not working anymore, hyper v is enabled in BIOS and everything should be working. Iv googled a bit but cant find any solution that fixes it.

I am running Windows 8.1

so far i tried:
running command - bcdedit /set hypervisorlaunchtype Auto
disabling and re enabling hyper v in BIOS
changing DEP settings
making sure all boxes ticked for hyper v in Turn Windows features on or off.


paying 300 fg if you can find solution that works.

This post was edited by -=vasya=- on Oct 19 2016 06:54am

What version of Windows?

Windows 8.1

sorry should have mentioned that and iv also edited my post with things that iv already tried so far

any one ?

This post was edited by -=vasya=- on Oct 20 2016 03:47am

Bios been updated since it last worked? I'd try that if possible. Who's the computer or motherboard manufacturer?

Alternatively, save the vm's somewhere, remove the hyper v role, and then reinstall it.

Nope, you mean try bios update? Its Asus board

I was gonna try reinstalling that but i dont wanna lose all my setting, i have some virtual switches set up etc...

Im sure there must be a way of fixing it with out uninstalling, just makes no sense why it stopped worked all of the sudden

This post was edited by -=vasya=- on Oct 20 2016 07:31am

In BIOS, you have virtualization enabled? In Windows, you have DEP enabled? Something worth noting is that your machine would have to be completely powered down and then started for either of these changes to take effect. A reboot wouldn't work.

Are you comfortable working at the command line? You can, using powershell, export the entire hyper v configuration to an XML file which can then be imported back in.

Is there some sort of hypervisor service that was shutdown and not running in the background.

I don't dealnwith windows servers so it's only a guess.

The error sounds like the application is failing to communicate with a background service.

yup both enabled and i did try powering down my PC

Nope, dont know nothing about that stuff



Not sure everything looks fine in Services

I was playing with virtual switches last time i used it, maybe that fucked it up somehow ?

Yea I don't know. I usually use QEMU for my virtualization needs.