Information and announcements from Program Managers, Product Managers, Developers and Testers in the Microsoft Virtualization team.
This is a Hypervisor 101 case that keeps showing itself every so often the forums, mailing lists, etc: A message to the effect of “The Hypervisor is not running” when a user tries to launch a VM. Felipe Ayora, one of our awesome UA people, has created this video that steps through how to investigate such a failure and fix it
It really annoys me that this kind of thing is produced in a video.
Lots of enterprises block streaming media, so i'm stuck. What was wrong with KB articles? Grr.
I had the same problem, but a machine boot time go inside the setup hardware and the CPU item change the option Virtualization Enable and Ready.
I have the same issue :( VT and NX Bit are both on and it doesn't work. The hvboot driver and all services are running. I must say that it worked sometime ago and now stopped working for an unknown reason. What next?
ok, I fixed it. I missed the HyperV BCD entry. I copied the VHD with the natively booted Server 2008 R2 from my old Win7 x86 to my newer Win7 Sp1 x64. Please add a better error message that shows in detail what is missing to run HyperV.
I see Felipe Ayora in this specific video run a Dell Optiplex 745, to my knowledge a Optiplex 745 uses a LGA 775 Intel processor which is not a real server but a normal business desktop.
In my case I have a HP XW6600 Workstation with two Quad Cores Intel Xeon E5450. Yes I know they do not support SLAT yet neither does this Dell Optiplex 745.
The workaround I used is : social.technet.microsoft.com/.../7704.client-hyper-v-survival-guide.aspx
I posted my workaround here : h30434.www3.hp.com/.../1990875
So tell me more how to circumvent this issue.
I agree with Mike- that having a video is not as helpful to me as ALSO having a list of the info that the video offers, so that I can scan it and see "what I might be missing" if I don't watch it. So, for those who wonder what's in this video:
Basically, Mr Ayora just walks through starting a PC, getting into the BIOS, and ensuring that virtualization support and Data Execution Protection (DEP) are enabled.
Presuming that you know how to do that, then the only two other pieces of info that stood out to me were:
1. Some PCs require that you actually power them off, then on- NOT just restart- for changes to BIOS to take effect.
2. There's an article that Mr. Ayora says is a very good reference, "prescriptive and descriptive." The title is "Before You Begin: Select a Computer to Test Hyper-V" - and Mr. Ayora says that it should show as the first hit on Bing if you search with that title. Currently, the URL is:
Apart from the video, and the article he alludes to, there's one other ref that was very helpful to me. It's dense with info, and it also has great hyperlinks to other good items. It's a TechNet article:
Hyper-V: Troubleshooting Event ID 3112 "The virtual machine could not be started because the hypervisor is not running.
The URL for it is currently:
RE: what to do with BCDEDIT to make the hypervisor start:
Unfortunately, the article I referenced above, "Troubleshooting Event ID 3112 ...," has one unclear point. It just says that we should use BCDEDIT to update the "correct launch options as referenced in the error." However, the error message that I get has no info about what to do with BCDEDIT, even in the Details. (I'm running Server 2008, R2).
However, I believe what's needed is this:
BCDEDIT /set hypervisorlaunchtype auto
See, for example, this thread:
Ooops- URL above should be:
None of these options worked for me. Hyper-V was working then it just stopped with the Hypervisor not running error. My bios was fine, I tried the bcdedit command and they didn't work.
The way I fixed it was to remove the Hyper-V feature, reboot, turn it back on, reboot, no more error. The only issue I had was that I lost my virtual switch settings which prevented my VMs from restarting. Luckily I could recreate them from the documentation and everything worked fine.
you can always
- enable DEP
- disable USB 3.0
- set bcdedit hypervisor=auto
- enable/disable virtualization in bios using a cold boot
- change partitions
- install a ms kb hotfix for amd cpus
but PLEASE read about this post on HP forums blaming the Ralink Bluetooth Driver causing that virtualization issue !