Device/Credential Guard error on Windows 10 Home

[Kiwitech62]

I recently upgraded to the latest version of VMware Workstation (14.1.1) and am now encountering the following problem when trying to launch VM's that worked fine previously.

"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."

Problem is that I'm running Windows 10 Home and the Device/Credential Guard is not a feature of that version - it's in Windows 10 Enterprise.

VMware Workstation version: 14.1.1 build 7528167

Windows 10 version:  Windows 10 Home - Version 1083 (build 17115.1)

As mentioned previously the VM's worked fine on the previous version of Workstation 14 on Windows 10 Home. The suggestions to turn off Device/Credential Guard for Windows 10 all relate to the Enterprise version and Hyper-V, which doesn't run on the Home version so the settings to change don't exist.

Appreciate any assistance or suggestions to resolve my problem.

[penguinjoe]

Same. Windows 10 1903 + VMWare Workstation  15.1.0. The updates says it is supposed to fix this issue but nope. I did all of the suggested instructions provided by Microsoft (registry edits + GPedit + BCDedit suggestions). No love. When can we expect VMWare to actually fix their hypervisor?

[mwaseemalvi]

https://www.ivobeerens.nl/2018/12/13/vmware-workstation-device-credential-guard-are-not-compatible/

[scott_griepentr]

I've put together this script that will trigger the bios F3 cancel of Credential Guard when run as administrator.  I have to do this after just about every windows update now, which is annoying.

VmwareFix.bat · GitHub

[Ruud_van_Strijp]

Just run cmd as Admin and type

bcdedit /set hypervisorlaunchtype off

and REBOOT

This was the solution for me. I installed Hyper-V, which conflicts with VMware Workstation because it enables the 'hypervisorlaunchtype' setting.

I removed Hyper-V and set this setting to off, and after the reboot VMware Workstation worked again.

[LPancakes]

I recently had this problem as well. I tried the things in this post and also followed the MSDN guidance to disable credential guard but no avail.

Anyway, I realized I had caused the problem myself by recently installing the PowerShell optional feature "Microsoft-Hyper-V".  If you did this too, you can undo/fix the problem by running:

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V

Some of the other posters have mentioned that Hyper V features may be causing the issue and to edit the registry directly, etc. But if you happened to do what I did (install the PS Module), you can just skip that and fix by uninstalling via PowerShell rather than editing keys directly.

[ITM2600]

bcdedit worked for me, thank you !

[emanresu]

You can use the pre-release from VMware Workstation Zealot - Official blog of VMware Workstation - VMware Blogs http://bit.ly/getworkstation-tp

Download

http://bit.ly/getworkstation-tp

Extract the installer with "/x" switch an directly install it from "%temp%"

[ThomasCP]

Hi all, I am reading a lot on how to disable the credentials guard on Win10.
What if the company policies don't allow to disable the credentials guard in Windows 10? Is there any fix from VM side?

Thanks

Thomas

[mharoutunian]

It just really annoying that even so many years later, and with VMware Workstation 16 Pro actually advertising it works with Hyper-V, Credential Guard etc, it still doesn't work without doing bogus stuff to disable settings via powershell since its locked by GPO.  Then they just get re-enabled by my company's GPO settings every time I restart the machine.