1

I have installed VMware workstation 16 on Hyper-V enabled host windows.

enter image description here enter image description here

The windows version is Win 10 2004 pro and hyper-v, wsl, sandbox are enabled to run docker. enter image description here enter image description here

Even though virtualization-based service is running, I could not power on VM and it's sending an error message of "VMware Workstation and Device/Credential Guard are not compatible"

enter image description here enter image description here

I have also enabled VBS support in guest VM, but still, it's not working.

enter image description here

Ramhound
  • 41,734
  • 35
  • 103
  • 130
Snoopy Dev
  • 21
  • 6
  • "Device/Credential Guard are not compatible" <-- That error has come up for me when try to run VMware Workstation and Sandbox at the same time. They are not compatible. Disable Sandbox and see if Workstation works withn Hyper-V enabled host. – John Oct 22 '20 at 01:24
  • Suspect this is an incompatibility with 20H2, if that’s the case, VMWare will release an update. [This](https://kb.vmware.com/s/article/2146361) article describes two registry keys, what are those values, provide those values as an edit to your question – Ramhound Oct 22 '20 at 02:09
  • Please provide the mksSandbox.log and vmware.log on something like pastebin – Ramhound Oct 22 '20 at 02:20
  • I was going to submit an answer that indicates you should disable Device/Credential Guard but I was able to confirm that Windows 10 2004 and VMWare Workstation 16 are compatible. This means your issue is a compatibility issue with Windows 10 20H2 – Ramhound Oct 22 '20 at 03:22
  • I have tested after disabling sandbox, but still it didn't work – Snoopy Dev Oct 22 '20 at 23:19
  • According to vmware site doc, workstation must detect hyper-v and operate in host vbs-mode, but it seems it's not detecting and operating in traditional mode. As I think, there is a problem in installed vbs, but not sure what the problem is – Snoopy Dev Oct 24 '20 at 00:07

1 Answers1

1

I have solved issue by disabling Credential Guard.

https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-manage#disable-windows-defender-credential-guard

Now both hyper-v and vmware can operate, though I can't use VT-x in guest vm.

It seems like VBS is different from credential guard.

Snoopy Dev
  • 21
  • 6