I’m running VMware Workstation for virtualization, and as you all know,
VMware and Hyper-V are sworn enemies.
After the last Windows update, Hyper-V was enabled again, but it was easy to just disable, so it worked that one time. Now I have Hyper-V disabled and I still get a warning when trying to open VMware:
Other threads have suggested that that there are other applications/services that use Hyper-V.
I do not have anything called Device Guard on my Windows 10-computer.
(Although I have BitDefender.)
To keep it short: How can I run VMware again?
Best Answer
Just to add a solution that worked for me:
If you are using the basic Window 10 HOME updated to the latest 2018 build level, VMware will not function, because some elements of Hyper-V are included, although they cannot be controlled.
In addition, many of the functions available in bcdedit and Powershell are not available with Windows 10 Home. For example, in Powershell, none of the vm cmdlts are available. Credential Guard/Device Guard are also not available. The Microsoft site solutions will not work. Even the so-called "Hypervisor readiness" do not run.
In "Programs" "Windows Functions" there are no selections for Hyper-V. There is only a generic tickbox for "Windows Hypervisor Platform".
However this sequence works:
untick "Windows Hypervisor Platform"
run bcdedit /set hypervisorlaunchtype off
reboot
steps 1-3 are not enough ! You must also deactivate the "Core Isolation" function in the Windows Defender Security Center.
Reboot again.
VMware will then function.
It is strange but interesting that "Core Isolation" also has an effect on some system drivers. With Core Isolation activated, my laptop CD/DVD drive was dead, Windows would not recognise its own native driver cdrom.sys. But everything returns to normal when Core Isolation is deactivated.