VMware Communities
cilldara
Contributor
Contributor

Installer detected the host has hyper-v or device/credential guard enabled. Installin Workstation 16

Hello,

I have an issue with VMware Workstation which seems to have started after recent bios and windows updates were applied. Unfortunately both updates were applied after multiple reboots.. one straight after the other so cannot say if it was the windows update or the bios update that caused, the issue.. 

I was running ESXi installed in a VM running on WorkStation 16. After the bios/windows update VMs with virtualize VT-x/EPT or AMD-V/RVI enabled would not power.  I thought the bios had reset reset intel virtualization but the feature is enable in the bios (i am running intel 11th series iCore processor) and I can see in the bios it is enabled. I can also see on task manager that the CPU has virtualization enabled.  Disabling Virtualise intel VT allows the VMs to power on but then cannot run VMs on the next ESXi hosts.. 

Workstation was on 16.2.1 and there was a pending update so I decided to update... During the update the installer detected that hyper-v or  Device/Credential Guard was enabled.. I have checked the features on my PC and I do not have them enabled..  This is confirmed in the logs :-

2022-01-14T08:25:13.479Z| inst-build-18811642| E1: WMI_GetWindowsOptFeatureList: Receive feature Microsoft-Hyper-V installstate is: 2.
2022-01-14T08:25:13.479Z| inst-build-18811642| E1: WMI_GetWindowsOptFeatureList: Receive feature Microsoft-Hyper-V-Tools-All installstate is: 2.
2022-01-14T08:25:13.479Z| inst-build-18811642| E1: WMI_GetWindowsOptFeatureList: Receive feature Microsoft-Hyper-V-Management-PowerShell installstate is: 2.
2022-01-14T08:25:13.479Z| inst-build-18811642| E1: WMI_GetWindowsOptFeatureList: Receive feature Microsoft-Hyper-V-Hypervisor installstate is: 2.
2022-01-14T08:25:13.479Z| inst-build-18811642| E1: WMI_GetWindowsOptFeatureList: Receive feature Microsoft-Hyper-V-Services installstate is: 2.
2022-01-14T08:25:13.479Z| inst-build-18811642| E1: WMI_GetWindowsOptFeatureList: Receive feature Microsoft-Hyper-V-Management-Clients installstate is: 2.
2022-01-14T08:25:13.479Z| inst-build-18811642| E1: WMI_GetWindowsOptFeatureList: Receive feature DirectoryServices-ADAM-Client installstate is: 2.
2022-01-14T08:25:13.479Z| inst-build-18811642| E1: WMI_GetWindowsOptFeatureList: Receive feature Windows-Defender-ApplicationGuard installstate is: 2.
2022-01-14T08:25:13.479Z| inst-build-18811642| E1: WMI_GetWindowsOptFeatureList: Receive feature Containers installstate is: 2.
2022-01-14T08:25:13.479Z| inst-build-18811642| E1: WMI_GetWindowsOptFeatureList: enumerate feature objects done.
2022-01-14T08:25:13.480Z| inst-build-18811642| I0: Host running in HyperV, but hyperV feature is disabled, maybe the host have feature enabled which depends on hyperV
2022-01-14T08:25:13.480Z| inst-build-18811642| I1: MsiUtil_GetPropertyString: Getting Property WHP_SUPPORT_BUILDNO = 19041
2022-01-14T08:25:13.480Z| inst-build-18811642| I1: MsiUtil_GetPropertyString: Getting Property VersionNT64 = 1000

I have checked all there services and processes but do not see anything related to hyper-v..

So despite not having hyperv or any of its related features enable the installer thinks I am running hyperv ..  I am not yet sure if this is related to the other issue with virtualise intel VT i had before trying to upgrade workstation.. 

For now I want to understand why and where the installer is getting this information.  I am wondering could this also be causing the issue with the intel VT setting for VMs. 

Any ideas of what else I can check.. 

Cheers.. 

6 Replies
Geraldcr91
Contributor
Contributor

Same issue here. 

Were you able to find a solution ? 

Tags (1)
fa1rid
Contributor
Contributor

I have the same issue. Hyper-v is not enabled but vmware thinks it's enabled. Strange..

Tisa9
Contributor
Contributor

Same Issue too.
Everything about Hyper-V is disabled or uninstalled. But Workstation keeps saying "Installer detected the host has hyper-V or device/credential guard enabled".

Windows 11
Workstation 16.2.5

TanquenETG
Enthusiast
Enthusiast

Same here with new Win11 laptop and Workstation Player 17 Player.

When I first installed Workstation 15 Pro, there was no message.

0 Kudos
TanquenETG
Enthusiast
Enthusiast

 

My fix only for this error on my new Win11 laptop was to disable DMA protection in the BIOS but it also disables the Intel Virtualization.

Only then was Virtualization-based security set to Not enabled in MSInfo.

Now I no longer get the message when trying to install Workstation Player 17 but I'm sure it can't run without the Intel Virtualization options on in the BIOS.

TanquenETG_1-1680645869342.png

TanquenETG_0-1680659246321.png

 

 

 

0 Kudos
F1Ben
Contributor
Contributor

@TanquenETGThanks for pointing me toward this BIOS setting.  This message during setup is misleading.  I was able to eliminate this message by disabling "Intel Virtualization Technology" in the UEFI settings.  On my Lenovo laptop, Kernel DMA Protection remained enabled.

F1Ben_0-1709837088541.png