If you get the message:
“Virtual machines cannot be started until Windows hypervisor is running.”
Check the Windows Server catalog to see if this server is qualified to run Hyper-V. Next, make sure the BIOS is enabled for hardware-assisted virtualization and hardware-enforced data execution prevention. Then, check the Hyper-V-Hypervisor event log.
Changing certain parameters in the system BIOS of a computer can cause that computer to stop loading the operating system, or it can make hardware devices, such as hard disk drives, unavailable. Always consult the user manual for the computer to determine the proper way to configure the system BIOS. Also, it is always a good idea to keep track of the parameters that you modify and their original value so that you can restore them later if needed. If you experience problems after changing parameters in the system BIOS, try to load the default settings (an option is usually available in the BIOS configuration utility), or contact the computer manufacturer for assistance.
To verify virtualization support in the BIOS or UEFI
- Restart the computer and access the BIOS or UEFI through the configuration tool. Access to this tool usually is available when the computer goes through a boot process. Immediately after you turn on most computers, a message appears for a few seconds that lists the key or combination of keys to press to open the configuration tool.
- Find the settings for virtualization and hardware-enforced Data Execution Prevention (DEP) and verify that they are on. Following are common menu locations for these settings in the configuration tool and examples of what they might be named:
- Virtualization support:
- Usually available in the settings for the main processor or performance. Sometimes it’s under the security settings.
- Look for parameter names that include “virtualization” or “virtualization technology”.
- Hardware-enforced DEP:
- Usually available under security or memory settings.
- Look for parameter names that include “execution”, “execute”, or “prevention”.
- Virtualization support:
- If necessary, turn on the settings by following the instructions in the configuration tool. Save the changes and exit.
- If you made any changes, turn the power off and then back on to the finish.
We recommend that you turn the power off and then back on (sometimes called a power cycle) because the changes aren’t applied on some computers until this happens.
Next, check the Hyper-V-Hypervisor event log. If there are problems, you’ll also check the System log.
To check the event logs
- Open Event Viewer. Click Start, click Administrative Tools, and then click Event Viewer.
- Open the Hyper-V-Hypervisor event log. In the navigation pane, expand Applications and Services Logs >> Microsoft >> Windows >> Hyper-V-Hypervisor, and then click operational.
- If Windows hypervisor is running, no further action is needed. If Windows hypervisor isn’t running, do this:
- Open the System log. (In the navigation pane, expand Windows Logs and then select System.)
- Use a filter to find Hyper-V-Hypervisor events:
- In the Actions pane, click Filter Current Log. For Event sources, specify “Hyper-V-Hypervisor”.
- Look for events that report problems. For example, event ID 41 indicates a problem with the BIOS configuration: “Hyper-V launch failed; Either VMX not present or not enabled in BIOS.”
Also, try to enter in elevated command prompt
“bcdedit /set hypervisorlaunchtype auto” as shown in the video