Aug 11, 2019 VMware Workstation and Hyper-V are not compatible To work around this error, you will have to follow these instructions on Windows 10: Open Windows Features panel. I've Windows 10 Pro system, and use Hyper-V on that system. Due to the needs of device redirection doesn't works well with Hyper-V, I've installed VMWare Workstation 14. I have to disable Hyper-V to make VMWare Workstation work, at beginning. It worked until last weekend, seems because of the QFE update. I just verified, it was not QFE but.
I've Windows 10 Pro system, and use Hyper-V on that system. Due to the needs of device redirection doesn't works well with Hyper-V, I've installed VMWare Workstation 14.
I have to disable Hyper-V to make VMWare Workstation work, at beginning. It worked until last weekend , seems because of the QFE update. I just verified, it was not QFE but Feature update to Windows 10, version 1803 that triggered the problem with VMWare Workstation again.
After Windows update completed (after reboot), I tried to start a VM in VMWare. I get the error dialog complaining about Device/Credential Guard.
Following the instruction in this link: https://kb.vmware.com/s/article/2146361, and after the reboot, I get another complaint about incompatibility with Hyper-V.
After reset the Hyper-V selection in Windows Feature or confirm that HyperV is not already removed, and reboot, the first error came back.
It gets in a loop of error complaining about Device Guard and complaining about Hyper-V for VMWare.
Ok, thanks to the answer from communities of VMWare: https://communities.vmware.com/thread/588526
The issue is now gone, by applying the following change:
Disable credential guard by using readiness tool from Microsoft: https://www.microsoft.com/en-us/download/details.aspx?id=53337, with this command: DG_Readiness_Tool_v3.2.ps1 -disable
Disable Hyper-V by using PowerShell command: Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
Reboot and accept to boot without CG/DG.
Although I don't like that VMWare cannot work together with device guard from system, I get my VM working for the moment.
here are the few steps for you to solve this issue:
Disable the HvHost service (and any other services with prefix Hyper-V if needed) from windows TaskManager(Ctrl+Alt+Del)
use the tool from the official website
Uncompress the downloaded zip file to your own directory, take C:DG_Readiness_Tool_v3.5 here for instance.
Run Windows PowerShell as admin, type the following two commands:
cd C:DG_Readiness_Tool_v3.5 .DG_Readiness_Tool_v3.5.ps1 -Disable
Reboot
Justin RonJustin Ron
Adrian at https://answers.microsoft.com/en-us/windows/forum/windows_10-security/cannot-disable-memory-integrity-core-isolation-in/29ac5ce4-30d2-47d1-ab17-734980fd287b says 'I think it's a bug that this cannot be disabled via UI but fortunately it's possible through the registry by setting the following key to 0:'
This worked for me as well [Windows 10 Pro Version 1803(OS Build 17134.112, VMWare Workstation 14 Pro Version 14.1.2]
kalscodekalscode
Vmware Workstation Windows 10 Compatibility Test
1- run cmd as admin
2- run : bcdedit /set hypervisorlaunchtype off
3- reboot
let me knew if it works please
good luck
jellad.tarekjellad.tarek
protected by Community♦Jul 1 at 6:55
Vmware Workstation 10 For Linux
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count). Would you like to answer one of these unanswered questions instead?
Not the answer you're looking for? Browse other questions tagged windowsvmwarehyper-v or ask your own question.
Posted by4 months ago
I decided to invest in VMW Workstation Pro 15 a few months back, based on the decision that VMW WSP 15 worked better than Hyper-V. I have 5 VMs that I run simultaneously some times. I have been using VMW products and the old Virtual PC since the late 90's.
Now along comes Win 10 1903 and it has has 2 features that I would like to try out: the Sandbox and WSL2, both as I understand , require that the Hyper-V feature set be installed on win10pro.
I had to do a little configuration(regedit and a Bcdboot command to turn the hypervisor off) to get my VM's to run on VMW WSP 15.
Is it possible to install the Hyper-V feature in win 1903 and have Hyper-V run/work as long as I don't have VMW WSP 15 running at the same time?
Will they co-exist with one another in that scenario?
I suppose I could create another BCD boot entry with hypervisor ON.....when I wanted to use Hyper-V?
I currently have VMW WSP 15 and Virtual Box both installed but I only run one or the other, never at the same time.
Can I do the same with Hyper-V and VMW WSP 15?
Has anybody heard if VMW is working on this issue ?
Any help or assistance will be greatly appreciated. TIA
Vmware Workstation 8 Compatibility With Windows 10