Virtual machine could not be started because the hypervisor is not running - Solved

Printer-friendly version

A while back I had set up a Hyper-V virtual machine, but it had been a while since I've needed to use it again. The time came again recently as I needed a VM to do some OS-specific testing. I got everything set up and started my VM, but was given an error message that said "Virtual machine [name] could not be started because hypervisor is not running." I was a little surprised to see it, since I could see that I had created a VM in the past - however, I remembered a change related to Hyper-V that I had made recently. While doing some experimentation with Xamarin, particularly with the Android emulator I encountered the issue of the Intel HAXM being unable to function because of a conflict with Hyper-V. To resolve I had turned off the hypervisorlaunchtype setting temporarily. Now that I remembered the issue, I tried switching it back and everything was back in working order.

To view the relevant settings, open a command prompt (as Administrator) and enter:

bcdedit

Under Windows Boot Loader you should see a value for hypervisorlaunchtype. For me, it was set to Off. To turn this back on, run the following command:

bcdedit /set hypervisorlaunchtype auto

I restarted my machine, and now was successfully able to start my Hyper-V VM.

About the Author:

TopLine Strategies delivers the complete integration and development of sales, marketing and customer service technologies that enable corporate clientele to improve revenue streams and strengthen customer interactions. Our project management and consulting is designed to achieve timely delivery, 100 percent user adoption of the technologies we implement and deliver measurable returns on investments for our clients.

Comments (0)