This is the error I am receiving:
VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard. Please visit http://www.vmware.com/go/turnoff_CG_DG for more details.
I have already tried the steps in the article below to disable device/credential guard:
Please advise.
I found the solution that fixed my issue.
Open cmd as an administrator, run below command:
bcdedit /set hypervisorlaunchtype off
After that restart your host.
---------------------------------------------------------------------------------------------------------
Was it helpful? Let us know by completing this short survey here.
Happened to me once after turning on windows sandbox after following the guide I had to do a system restore to known working date
I found the solution that fixed my issue.
Open cmd as an administrator, run below command:
bcdedit /set hypervisorlaunchtype off
After that restart your host.
---------------------------------------------------------------------------------------------------------
Was it helpful? Let us know by completing this short survey here.
You guys are the greatest. I had tried a dozen or more remedies recommended by geeky Web sites and none had worked. I going forward again using the VMware Player's newest version. And I learned some new things along the was such as how to use the Windows PowerShell as an administrator. My thanks.
Great post. Disabling is not enuff. The command was required, in an admin powershell
I would like to add that as long as the command [systeminfo] in a CMD console displays the following VMWare Workstation will complain about Device/Credential Guard
"A hypervisor has been detected. Features required for Hyper-V will not be displayed."
Device/Credential Guard is only one of many things that require Hyper-V, another is Windows Sandbox and perhaps even Windows Subsystem for Linux.
Perhaps [bcdedit /set hypervisorlaunchtype off] is enough to get ride of Hyper-V, but I had to restart the host twice in order to make the above message disappear.
Before setting hypervisorlaunchtype off I disabled the following items in [Windows Features]:
Now [systeminfo] shows:
confirming that Hyper-V is actually disabled.