I am running VMware Workstation v14.1.2 build-8497320 on Windows 10 Enterprise on a Lenovo P50.
Today after a Windows 10 update, and installing Docker for Windows, none of my VMware Workstation VMs would open: CentOS, Ubuntu, Windows7.
I received the following message:
The link provided in the above error message states: “VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard”.
The link went on to describe how Device/Credential Guard may be disabled by running gpedit.msc.
When I attempted to run this command, as administrator, I get the following error:
This likely because corporate security restricts what I can change on my laptop.
Another solution that I found was that Device/Credential Guard may be disabled by running the Device Guard and Credential Guard hardware readiness tool. I tried running this from the Powershell, as admin, and got the message that running scripts is not permitted. This is also likely a restriction imposed by corporate security.
What worked for me
After traveling down the above two “rabbit holes”, it occurred to me that perhaps neither Device/Credential Guard nor Windows update were the culprits but rather the Docker for Windows install I just did. Specifically, Docker for Windows had enabled Hyper-V.
As soon as I turned off this feature and rebooted, my VMs worked again!
I posted this solution on our corporate Windows 10 support site and was told the following by our support person:
"VMware is UNSUPPORTED on Win10. Hyper-V is the only supported VM. I suspect you will have additional pain when we the security team gets around to fully enabling Device-Guard."
This made the prospects for VMware Workstation on Windows 10 appear to be grim.
Will I have to switch to a Linux desktop to continue using VMware Workstation?
