windows 10 vmware workstation pro 12 conflict

A forceful shutdown will be needed, but will loose the current state. These virtual machines have the Virtualization engine options greyed out. There are many virtual machines that are suspended. Technically, from what I have read, uncheck the top two and the Virtualize IOMMU (IO memory management unit) may be checked.Īfter removing those features, I was able to start the virtual machine. To resolve this problem, ensure that the following items are unchecked in the Virtualization engine section under the Virtual Machine Settings. Something that used to work in older versions of VMware Workstation no longer works.

VMware Workstation does not support nested virtualization on this host. According to VMware, an update to 15.5.7 should resolve everything.Īfter updating to the latest free update 15.5.7 an attempt to launch the same virtual machine revealed a new error. Since the introduction of Hyper-V, including Credential Guard and Device Guard, enabling any of these features prevented VMware Workstation from launching virtual machines.

Your host does not meet minimum requirements to run VMware workstation with Hyper-V or Device/Credential Guard enabled. The first thought, why not try to launch a virtual machine in the existing VMware Workstation 15. A sneaky suspicion that this would break VMware Workstation 15 and it did. After an update to a Windows 10 system to the 20H2 build, it was quickly noted that the device manager added virtual ethernet ports to support Hyper-V.

Windows 10 vmware workstation pro 12 conflict