VMware Workstation Device/Credential Guard are not compatible

When using VMware Workstation 15 Pro with on Windows 10 with the Hyper-V role enabled I’ve got the following error when trying to install or start Windows 10 in VMware Workstation:

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.

In 2013 I did a post about using VMware Workstation and Hyper-V together on Windows 8, link. The bottom line that the Hyper-V role conflicts with  VMware Workstation.  It looks like this is still the case. The same  solution can be used to  disable the Hyper-V role in Windows 10.

To disable Hyper-V from starting the following command can be used:

bcdedit /set hypervisorlaunchtype off

A reboot of Windows 10 is necessary. After the reboot I was able to boot the Windows 10 VM.





To enable the Hyper-V role again use the following command:

bcdedit /set hypervisorlaunchtype auto

A reboot of of the Windows 10 is necessary.


VMware/Microsoft has a KB article how to disable Windows Defender Credential Guard, link and link. I did not try this because the solution in this worked for me.

23 thoughts on “VMware Workstation Device/Credential Guard are not compatible”

  1. im getting access is denied. i should be in which directory to run this command?

  2. as above, am running VMWare 15 with Win10 Home, but getting the error “VMWare Player and Device/Credential Guard are not compatible”. Have turned off Hyper-V support as suggested above (and re-booted) to no avail. Why does VMWare claim to run on Win10 Home when it clearly doesn’t (or not without a lot of undocumented effort / tinkering)

  3. Try running it in Oracle VirtualBox. That’s what I did with mine and it ran fine without screwing around with any of this garbage. The one thing that did work for VMWare was the elevated CMD window command of ‘bcdedit /set hypervisorlaunchtype off’. But this breaks WIndows 10 v1903 Sandbox capability.

    VMWare doesn’t seem to be able to Dev their way out of this hole… Kick them to the curb and go Oracle.

  4. Thanks. I was getting an error trying to run a Windows 10 VM as guest in both Oracle VM VirtualBox and VMWare Workstation after uptdating to Win 10 1903 as host. Running bcdedit /set hypervisorlaunchtype off worked for me too. For anyone who tries it, you have to open CMD as an administrator to run this command. True, Windows Sanbox no longer works now. But Sandbox is a buggy program so far, so that’s no great loss.

  5. This worked for me. Got this error after uninstalling Docker Community Edition.
    Disabled Device/credential guard in policy to no avail.

    Thanks so much.

  6. Thanks! It worked for me. I was trying to google all the possible ways using the provided link by VMware, but was not getting a solution. This simple turn off command worked like a charm.

  7. Finally! After mucking around in the Group Policy, and registry settings, to no avail, someone has posted a fix action that actually fixes my problem. Thank you so much.

  8. After finding several useless pages from googling the issue, this is the only thing that worked for me that allowed me to use VMWare with kali. Thank you for the post!

  9. One more comment: I noticed that after a windows update — at least if you’re part of the Windows Insider Program, that you will lose many of your personalized settings — including this /hypervisorlaunchtype fix. you will have to launch another CMD prompt as Administrator and run this again. Thank you original poster!

  10. Worked perfectly, thank you!

    If you get this error:
    “The boot configuration data store could not be opened.
    Access is denied.”

    You should run CMD as administrator.

  11. This worked fine.
    But this throws another issue with other software like Doker that needs Hyper-V.
    I am not to sure if VM-Ware is aware of this issue.

  12. Now (2020-05-31) there should be new
    “`VMware Workstation 15.5.5 Player | 28 May 2020 | Build 16285975“`
    which supposedly runs even with Hyper-V enabled.
    That in theory should take care of the coexistence of Docker and VMW w/o rebooting.
    However, I am still getting the same complaints from VMW. The message is the same old “VMware Player and Device/Credential Guard are not compatible” and I spent some time poking into registry but didn’t succeed. But there should be a way.

  13. This makes no sense where a I to type this in to “bcdedit /set hypervisorlaunchtype off”

  14. Thank you, I followed the instruction and could solve the issue by running the ” bcdedit /set hypervisorlaunchtype off”
    it worked!!

  15. Worked great! as someone who needs VMware for some VMs and Hyper-V support for Docker, its nice to have an easy way to turn this on and off…


    Fixed error in VMware Workstation on Windows 10 host Transport (VMDB) error -14: Pipe connection has been broken.

    Today we will be fixing VMWare error on a windows 10 computer.

    In RUN box type “gpedit” then Goto [ERROR SEE POINT 3]
    1- Computer Configuration 2- Administrative Templates 3- System – Device Guard : IF NO DEVICE GUARD : (DOWNLOAD https://www.microsoft.com/en-us/download/100591 install this “c:\Program Files (x86)\Microsoft Group Policy\Windows 10 November 2019 Update (1909)\PolicyDefinitions” copy to c:\windows\PolicyDefinitions ) 4- Turn on Virtualization Based Security. Now Double click that and “Disable”

    Open Command Prompt as Administrator and type the following gpupdate /force [DONT DO IF YOU DONT HAVE DEVICE GUARD ELSE IT WILL GO AGAIN]

    Open Registry Editor, now Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\DeviceGuard. Add a new DWORD value named EnableVirtualizationBasedSecurity and set it to 0 to disable it. Next Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA. Add a new DWORD value named LsaCfgFlags and set it to 0 to disable it.

    In RUN box, type Turn Windows features on or off, now uncheck Hyper-V and restart system.

    Open command prompt as a administrator and type the following commands

    bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d “DebugTool” /application osloader

    bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path “\EFI\Microsoft\Boot\SecConfig.efi”

    bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}

    bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS

    bcdedit /set hypervisorlaunchtype off
    Now, Restart your system

Leave a Comment