When troubleshooting this particular issue, you should start this troubleshooting guide by disabling Hyper-V conventionally. You can do this either by disabling it via CMD or by relying on the GUI interface. Another potential problem that might end up causing this issue is a local group policy called Virtualization Based Security that ends up blocking certain virtualization technologies. In this case, you can either use the Local Group Policy Editor to disable this policy or you can rely on Registry Editor to enforce this change. However, if you’re encountering this issue on Windows 10, it’s likely that the problem is caused by inconsistency with the Boot Configuration Data. If this scenario is applicable, you can fix this problem by modifying the BCD file to eliminate any reference of Hyper-V. In the event that you’re using Windows Defender, keep in mind that this WMware error can also occur due to a security feature called Core isolation. In this case, you can fix the issue by disabling Core Isolation from the Settings app or you can do it using Registry Editor.
Method 1: Disabling Hyper-V
According to various user reports, one of the most common causes that will trigger the “VMware and DeviceCredential Guard are not Compatible” error is a conflict between Hyper-V (Microsoft’s proprietary virtualization technology) and VMware. Keep in mind that both VMware and VirtualBox will pick their own virtualization technologies by default. However, there is one Windows Update (KB4515871) that is known to force certain 3rd party applications to use Hyper-V – in VMware, this will end up producing the “VMware and DeviceCredential Guard are not Compatible” error. If this scenario is applicable and you recently installed a Windows update that you think might be responsible for the newly appeared error, follow one of the guides below to disable Hyper-V in order to clear the way for VMware to use its own virtualization technology.
A. Disabling Hyper-V via CMD
B. Disabling Hyper-V via Powershell
There is also another way to enable or disable Hyper-V in Windows 10. To do it, please run PowerShell as administrator and then type the following commands:
C. Disabling Hyper-V via GUI
If you still end up seeing the “VMware and DeviceCredential Guard are not Compatible” error when launching WMware Player / WMware Workshatiaon or when trying to mount a virtual machine, move down to the next potential fix below.
Method 2: Disabling Virtualization Based Security
If you followed the instructions above and you already confirmed that you’re not actually dealing with a conflict between Hyper-V and Vmware, it’s possible that you’re seeing the “VMware and DeviceCredential Guard are not Compatible” error due to the fact that your machine is enforced with Virtualization Based Security -This is required with certain virtual machine types. This Virtualization Based Security is enforced through a policy via the Local Group Policy Editor. But keep in mind that by default, this utility is only available for Windows 10 PRO and older PRO equivalents. Note: If you have a Home version, you can manually install the gpedit utility on Windows 10 home. If the Local Group Policy Editor (gpedit) is available on your Windows version and you want to deploy this potential fix, follow the instructions below (sub guide A) to disable Virtualization Based security on via it’s dedicated policy. In case you’re using a Home version and you don’t want to side-load the Local Group Policy Editor, follow the second guide (sub guide B) to disable Virtualization Based Security via Registry Editor.
A. Disable Virtualization Based Security via Gpedit
B. Disable Virtualization Based Security via Registry Editor
In case you’re still encountering the same problem even after you’ve enabled virtualization-based security, move down to the next potential fix below.
Method 3: Modifying the BCD File
As it turns out, this particular issue can also be caused by inconsistency with the BCD (Boot Configuration Data) that ends up interfering with the 3rd party virtualization technology. Several affected users that were having the same problem have reported that the issue was suddenly resolved after they ran a couple of commands in an elevated command prompt. These commands will ensure that the remnant of Hyper-V is not conflicting with the virtualization technology that VMware uses. Here’s what you need to do: In case you’re still seeing the same “VMware and DeviceCredential Guard are not Compatible” error, move down to the final fix below.
Method 4: Disabling Core Isolation
If none of the fixes above have worked for you, there is one final potential culprit that we haven’t taken care of until now. If you’re using Windows Defender, it’s possible that a security feature called Core Isolation is actually triggering the “VMware and DeviceCredential Guard are not Compatible” error. Core isolation is essentially an extra layer of security that Windows Defender deploys in order to protect against sophisticated malware attacks that operate at a Kernel level. Several affected users that followed through with the disablement of this security feature have confirmed that the problem went away entirely. But there is a disadvantage – you will be leaving your system exposed to some security exploits. If you want to give this method a try, follow the first guide below (sub guide A) to disable Core isolation from the settings menu of Windows Security. If the Core isolation entry is greyed out, you can also do this via Registry Editor (sub guide B).
A. Disabling Core Isolation via GUI
B. Disabling Core Isolation via Registry Editor
Fix: VMware Workstation Unrecoverable Error (vcpu-0)VMware Workstation Pro Can’t Run on Windows? Try these fixesMicrosoft Windows Defender System Guard Will Now Protect System Integrity At The…Fix: Boot Guard Verified Failed
