Just recently after upgrading Windows 10 , I found there is an incompatibility issue between VMware Workstation and Device / Credential. Device/Credential Guard is a Hyper-V based Virtual VMware Workstation and Windows features like WSL, Device Guard and Credential Guard.
 
 

Vmware workstation 14 device/credential guard free

I do not wan’t to mess around to much since I wan’t to be able to restore all settings to their previous values later. What are these VMWare instructions actually doing? Disabling device guard and removing EFI variables. Though this is a workaround, an answer to this question is posted in a VMWare article, which solved the problem for me:. In brief, this mechanism exists on Windows to prevent the execution of malicious code. You can find more details about it here:. The workaround involves disabling this mechanism in effect solving the problem , however do so with caution, as this may entail a potential security risk while executing future code.

This requires system reboot, unfortunately. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Start collaborating and sharing organizational knowledge. Create a free Team Why Teams? Learn more about Teams. Asked 5 years, 10 months ago. Modified 4 years, 1 month ago. Viewed 24k times. Improve this question.

Community Bot 1. Ogglas Ogglas 1, 5 5 gold badges 16 16 silver badges 31 31 bronze badges. If there were a better known workaround, then VMware probably would suggest using that instead. Since VMware doesn’t, there probably isn’t. Add a comment. Sorted by: Reset to default.

Highest score default Date modified newest first Date created oldest first. Improve this answer. The second variable: 0 means that it’s configured to run in protect mode. This variable should always be 0. Using cached copy status: 0x0. Unsealing cached copy status: 0x1. New key generation status: 0x1.

Sealing status: 0x1. You can use Windows PowerShell to determine whether credential guard is running on a client computer. On the computer in question, open an elevated PowerShell window and run the following command:.

Windows Defender Credential Guard can be disabled via several methods explained below, depending on how the feature was enabled. For devices that had Windows Defender Credential Guard automatically enabled in the 22H2 update and didn’t have it enabled prior to the update, it’s sufficient to disable via Group Policy. Otherwise, Windows Defender Credential Guard can be disabled by changing registry keys.

Windows Defender Credential Guard running in a virtual machine can be disabled by the host. In the “Credential Guard Configuration” section, set the dropdown value to “Disabled”:. Deleting these registry settings may not disable Windows Defender Credential Guard.

They must be set to a value of 0. This scenario will require physical presence at the machine to press a function key to accept the change. In the “Credential Guard Configuration” section, set the dropdown value to “Disabled”.

From an elevated command prompt, type the following commands:. Restart the PC. This prompt must be confirmed for the changes to persist. This step requires physical access to the machine. Disabling Virtualization-Based Security may have unintended side effects. If you manually remove these registry settings, make sure to delete them all. If you don’t remove them all, the device might go into BitLocker recovery. From an elevated command prompt, run the following bcdedit commands after turning off all Virtualization-Based Security Group Policy and registry settings as described in steps 1 and 2 above:.

Skip to main content. This browser is no longer supported. Table of contents Exit focus mode. Table of contents. Tip You can also configure Credential Guard by using an account protection profile in endpoint security.

Note In Windows 10, version and later, the Isolated User Mode feature has been integrated into the core operating system. This is a known issue. Note For client machines that are running Windows 10 , LsaIso.

Important If you manually remove these registry settings, make sure to delete them all.