May 3, 2017 - It says that the Hyper-v is not running and virtualization infrastructure driver (VID) is not running. So I did a fix and run “bcdedit /set hypervisorlaunchtype auto” as Administrator. But it did not fix the problem. So I tried going to BIOS and check if the Intel Virtualization is Enable. And yes it is enabled.
Hyper-V is the Microsoft Windows hypervisor starting in Windows Server 2008 R2 and also running on Hyper-V Server 2008, Hyper-V Server 2012, Windows Server 2012, and as an optional component of Windows 8.
The Hyper-V role lets you create and manage virtualized computing environments. Hyper-V is built into recent Windows operating systems as an optional feature and includes two independent components:
- The management components for managing Hyper-V hosts.
Management tools include Hyper-V Manager for virtual machine management, Virtual Machine Connection for interactive connections to the virtual machine UI, and Hyper-V-specific cmdlets for Windows PowerShell. - The virtualization platform for running virtual machines.
Platform tools include the hypervisor, WMI provider, and other necessary virtualization components such as the virtual machine bus (VMbus), virtualization service provider (VSP) and virtual infrastructure driver (VID).
If you want to run and manage virtual machines on your machine you will need to enable both the platform and management tools. Very few people enable one without the other.
If you use Server Manager to install the Hyper-V role, the management tools are included unless you specifically exclude them. If you use Windows PowerShell to install the Hyper-V role, the management tools are not included by default. To install the tools, use the parameter –IncludeManagementTools. For instructions about installing the Hyper-V role, see Install Hyper-V and Configure a Virtual Machine.
Hyper-V Documentation:
-->
Applies To: Windows Server 2016
Property | Details |
---|---|
Operating System | Windows Server 2016 |
Product/Feature | Hyper-V |
Severity | Warning |
Category | Prerequisites |
In the following sections, italics indicates UI text that appears in the Best Practices Analyzer tool for this issue.
Issue
Windows hypervisor is not running.
![Virtualization Infrastructure Driver (Vid) Is Not Running Virtualization Infrastructure Driver (Vid) Is Not Running](http://apprize.info/microsoft/hyper-v_1/hyper-v_1.files/image024.jpg)
Impact
Virtual machines cannot be started until Windows hypervisor is running.
Resolution
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.
To check the catalog, see Windows Server catalog (https://go.microsoft.com/fwlink/?LinkId=111228).
Caution
![Server virtualization infrastructure Server virtualization infrastructure](/uploads/1/2/6/2/126242114/730631477.jpg)
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 under 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 the security or memory settings.
- Look for parameter names that include 'execution', 'execute', or 'prevention'.
- 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 finish.ImportantWe 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.'
See Also
For details about using Hyper-V on Windows 10, including how to check that your computer can run Hyper-V, see Windows 10 Hyper-V System Requirements.