LKBEN11735: How to check Hyper-V possibilities on your windows system.

Symptom

You need to enable a hypervisor on your system and need to check the cpu possibilities first.

Cause

Solution

You can open a powershell and enter the following command:

Get-ComputerInfo -property "Hyper*"

This should show you information about your hypervisor. A possible output is the following:

HyperVisorPresent                                 : False
HyperVRequirementDataExecutionPreventionAvailable : True
HyperVRequirementSecondLevelAddressTranslation    : True
HyperVRequirementVirtualizationFirmwareEnabled    : False
HyperVRequirementVMMonitorModeExtensions          : True

Please note the HyperVRequirementVirtualizationFirmwareEnabled setting is False.

To change this, you need to enable it in your BIOS.

This is the output from the same system after I enabled virtualisiation in the BIOS:

HyperVisorPresent                                 : False
HyperVRequirementDataExecutionPreventionAvailable : True
HyperVRequirementSecondLevelAddressTranslation    : True
HyperVRequirementVirtualizationFirmwareEnabled    : True
HyperVRequirementVMMonitorModeExtensions          : True

You can see the HyperVRequirementVirtualizationFirmwareEnabled setting is now True. This can be helpfull if you need to install WSL (Windows subsystem for Linux) in the version 2 which needs virtualisation to be active.

After you installed a HyperVisor (e.g. WSL version 2) the readout will show the following:

HyperVisorPresent                                 : True
HyperVRequirementDataExecutionPreventionAvailable :
HyperVRequirementSecondLevelAddressTranslation    :
HyperVRequirementVirtualizationFirmwareEnabled    :
HyperVRequirementVMMonitorModeExtensions          :

You can only run one Hypervisor at the time. Examples of Hypervisors are VirtualBox or Hyper-V.

Hope this helps.

Disclaimer:

The information provided in this document is intended for your information only. Lubby makes no claims to the validity of this information. Use of this information is at own risk!

About the Author

Author: Wim Peeters - Keskon GmbH & Co. KG

Wim Peeters is electronics engineer with an additional master in IT and over 30 years of experience, including time spent in support, development, consulting, training and database administration. Wim has worked with SQL Server since version 6.5. He has developed in C/C++, Java and C# on Windows and Linux. He writes knowledge base articles to solve IT problems and publishes them on the Lubby Knowledge Platform.

Latest update: 25-07-2024