Can I run VMware Workstation Pro 16 and Hyper-V and docker (linux images) on Windows Server 2022 ?

[natocccp]

Hi, I have VMware Workstation Pro 16 on Windows Server 2022. I am getting an error that I can't run VMware with Device Guard/Credential Guard.

Device Guard/Credential Guard are disabled in Local Security Policy.

I have installed Mirantis docker that is working with Hyper-V.

When I try to run Windows Server 2019 as guest OS on VMware Workstation I get error:

VMware Workstation and Device/Credential Guard are not compatible. VMware Workstaion can be run after disabling Device/Credential Guard. Visit http://www,vmware,com/go/turnof_CG_DG for more details.

As mentioned I have disabled DG/CG with Local Security Policy.

I need both docker and VMware on Windows Server 2022.

Any directions how to resolve the issue?

Regards

A

[Canfoderiskii]

same issue here.

Windows Server 2022 seems to be based on Win 10 21H2 ( at least 20H1), according to this post: https://meterpreter.org/windows-server-2022-is-built-on-windows-10-21h1/

And I tried VMware Workstation on another Hyper-V enabled Windows 10 20H1 PC, during which the virtual machines can start up normally.

So I guess technically Server 2022 with Hyper-V can be compatible with VMware Workstation, but Server 2022 is not in VMware Workstation's compatible list, therefore the checking failure occurs.

Maybe VMware will fix this later, I hope.

[Smudge67]

Hi,

Did you ever manage to get anywhere with this?

I have a similar post in the VMware Workstation Player community, but it has received no responses.

https://communities.vmware.com/t5/VMware-Workstation-Player/Compatibility-with-Hyper-V-on-Windows-Se...

VMware Workstation Pro/Player v17 is listed as supported on Windows Server 2022 on the following page :-

https://kb.vmware.com/s/article/80807

I have even tried a later release (v17.0.1) and it still complains about Hyper-V during install.

Thanks.

[Smudge67]

I have now also tried the later release v17.0.2 and the error is still the same.

Hopefully VMware will find a way to fix this.

[devdavinci]

We run into same issue with 17.0.2 on Windows Server 2019 today

We have tried lots of solutions I could found, like disable Device/Credential Guard, disable Hyper-V, turn off Core Isolation ...

Also found a post similar to the problem and we tried the script provided in the solution comment.

https://communities.vmware.com/t5/VMware-Workstation-Pro/Device-Credential-Guard-are-not-Compatible/...

but none of them work for us.

Did anyone have idea?

Thanks a lot.