just ran into this myself. thank you for this post, undoubtedly saved me a substantial amount of time and frustration. Darn shame, woulda liked to use it. Its pretty darned quick and convenient but not at the expense of losing all my vms.
As per the article you linked cosmic, it seems that the easiest way to disable credential guard is to download the Download Device Guard and Credential Guard hardware readiness tool and then run
DG_Readiness_Tool_v3.6.ps1 -Disable -AutoReboot
That seems to have done the trick for me. Make sure on reboot you only choose to disable the credential guard (at the first prompt) and not virtualization based security (the second).
My PC running VMware Workstation got the May 2019 update and I enabled Windows Sandbox and tried it.
Afterward I couldn't launch VMs under VMware Workstation.
Running DG_Readiness_Tool_v3.6.ps1 -Disable -AutoReboot repaired it.
This is a hoot, because the W10 Preview VM (now up to build 18898) under VMware Workstation still throws up an error message and won't run.
I guess it doesn't matter if Windows Sandbox runs inside the VM, when I can run it as needed on the host.
1 person found this helpful
I just started seeing this error today, but according to the page(s) referenced by the error message, I do not have Credential Guard enabled:
Notice that System Information shows that no Virtualization-based security services are configured. Also, the setting specifically mentioned by this article is off:
I *did* install Windows Sandbox last week in order to test something, so that is probably what has killed VMware, but nothing here seems to match the articles I am finding. I uninstalled Windows Sandbox and the Core Isolation setting didn't change (it was off when Sandbox was installed and remained off after I removed it.)
I would not have wanted to use the sandbox if it were just as easy to spontaneously generate a complete, clean Windows 10 environment for a single test usage in VMware -- but that takes time and effort (including booting the image weekly to ensure it stays up to date, etc.)
OTOH, I am extremely upset with Microsoft for not warning me about the products that would be broken by installing their tool, too. Hopefully VMware can put their big brains to work and find a way to fix this. Until then, I cannot perform my job because the VMs were my code and tools exist will no longer run. Great.
FOLLOW UP: On my system (Win 10 Pro x64 version 1903 build 18362.175) both settings in (1) and (2) were already set as recommended before and after (3) uninstalling hyper-v and sandbox. The first command in (4) failed, but the others appeared to work and after rebooting, VMware is now starting my VMs again.
SO... while much of this solution doesn't match today's version of windows, some of the "secret" codes given at the end still helped. Thanks.
This worked for me when other solutions (including the ones VMware links to at Microsoft) didn't.
Despite having already turned off Windows Sandbox and Hyper-V features, and having used the DG_Readiness_tool_v3.6.ps1 tool, I was unable to use VMware Workstation 12 until following this guide.
I believe it may have been "bcdedit /set hypervisorlaunchtype off" that finally forced whatever components that were left to turn off.
Kudos to cosmic665
Hit the windows key+s for "Search"
I feel I should mention, you don't have to press Win+S for search. You can just press Win and start typing.
Hit the windows key+r for "Run" and type "gpedit.msc"
You also don't have to do Run for that. You can just press Win, type "gpedit.msc" and hit enter. It has the same effect. But to each his own
I just joined this community because I'm having this exact problem.
Thank you for posting your experience, nurbles.
Going to try your stated solutions and hopefully everything will be back to normal for me.
I have 2 virtual machines and the latest Windows Update broke both. Have tried the same, exact troubleshooting steps.