VMware Player and Device/Credential Guard are not compatible!

What is this?!

Well it turns out that by turning on all the SDK stuff for Windows 10, including the mobile dev, which includes the Windows phone emulator it naturally uses Hyper-V.

Hyper-V Hypervisor enabled

And naturally the two hypervisor’s wont play nice with each-other.  You could just disable it, and go back and forth re-enabling it when needed, or make a new boot selection without it!

I found this post here: Switch Easily Between VirtualBox And Hyper-V WithA BCD Edit Boot Entry In Windows 8.1

C:\>bcdedit /copy {current} /d "No Hyper-V" 
The entry was successfully copied to {ff-23-113-824e-5c5144ea}. 

C:\>bcdedit /set {ff-23-113-824e-5c5144ea} hypervisorlaunchtype off 
The operation completed successfully.

note: The ID generated from the first command is what you use in the second one. Don’t just run it verbatim.

When you restart, you’ll then just see a menu with two options…

  • Windows 10
  • No Hyper-V

Sounds easy enough, doesn’t it?

BCD Boot menu

And just like that on power up, I can switch between Hyper-v and no Hyper-V.

Author: neozeed

I live in SE Asia, doing generic work, enjoying my life & family

3 thoughts on “VMware Player and Device/Credential Guard are not compatible!”

    1. Too bad my processor is too old, so I’m stuck at 12.5.9

      Maybe I’ll get a new CPU board + processors for this machine, but I think it may cost more than I paid for it, and it’s really not worth it at that point.

    2. Only in VMs, not on the host. Credential Guard requires Hyper-V, and Hyper-V is incompatible with every other VM software on Windows (though Microsoft added support for 3rd party VM solutions to use the Hyper-V framework in 1803, but AFAIK so far only Qemu added support for that).

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.