VMware Player and Device/Credential Guard are not compatible

I have this error with vmware w. player 15.5, is this a bug and, if possible, what does it means?

Thanks!

BTW this happens if I enable "core isolation", I understand core isolation is necessary to avoid hardware bugs in intel cpu.

"Feature" of Defender.
To disable device & credential guard:

https://www.microsoft.com/en-us/down....aspx?id=53337
- download & extract to C:\dgreadiness_v3.6
- run powershell as admin:

Code:

cd C:\dgreadiness_v3.6
Set-ExecutionPolicy AllSigned
.\DG_Readiness_Tool_v3.6.ps1 -Disable

- reboot

Hi, more simply I found that disabling core isolation and with this cmd:

bcdedit /set hypervisorlaunchtype off

vmware will work again, I wonder how severe is the risk of disabling core isolation... (is this feature even present in win 81) I mean is this a very unusual risk, is it remotely exploitable or only locally ) is it ok to leave core isolation off so I can use vmware?

thanks.

roy111 said:

I have this error with vmware w. player 15.5, is this a bug and, if possible, what does it means?

Thanks!

BTW this happens if I enable "core isolation", I understand core isolation is necessary to avoid hardware bugs in intel cpu.

Hi there
VMWare are working on a few things -- for instance enabling VMWare products to run concurrently with HYPER-V so this problem will be solved in the next release (estimated Q1 2020).

Cheers
jimbo

roy111: defender features use hyperv components so results of both methods are similar. To utilize processor vulnerabilities you need your own process running at proc so no direct remote exploit; of course it can be combined with others.

Definitely it is your decision.

Given your answers i think it's clear to me what's goin on and the problem will be fixed in 2020 hopefully, thanks all!