VMware asks to disable Device Guard in Windows 10

When I opened the virtual machine today, the following error suddenly appeared. There are many tutorials on the Internet, basically disabling Device Guard and closing Hyper-v. The blogger operates according to his method, and the following error still occurs. After unremitting efforts, I finally found a solution, which I will share here.

Go to the link in the tips.

The content obtained by visiting the URL in the diagram is directly given below (the translation is attached later).

---

Purpose：

This article provides steps to disable Credential Guard or Device Guard for a Windows 10 Enterprise host.

 

Cause

This issue occurs because Device Guard or Credential Guard is incompatible with Workstation.

 

Resolution

To disable Device Guard or Credential Guard:

1. Disable the group policy setting that was used to enable Credential Guard.
   • On the host operating system, click Start > Run, type gpedit.msc, and click Ok. The Local group Policy Editor opens.
   • Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security.
   • Select Disabled.
2. Go to Control Panel > Uninstall a Program > Turn Windows features on or off to turn off Hyper-V.
3. Select Do not restart.
4. Delete the related EFI variables by launching a command prompt on the host machine using an Administrator account and run these commands:
   

   mountvol X: /s
   copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y
   bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
   bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
   bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
   bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS
   bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
   mountvol X: /d

   Note: Ensure X is an unused drive, else change to another drive.
5. Restart the host.
6. Accept the prompt on the boot screen to disable Device Guard or Credential Guard.

---

 

Translation:

---

 

Purpose

This article provides steps to disable Credential Guard or Device Guard for Windows 10 Enterprise hosts.

 

reason

This problem occurs because Device Guard or Credential Guard is not compatible with Workstation.

 

solution

To disable Device Guard or Credential Guard:

1. Disable the Group Policy setting for enabling Credential Guard.
   • On the host operating system, click Start  >  Run , type gpedit.msc, and click OK. The Local Group Policy Editor opens.
   • Go to Local Computer Policy  >  Computer Configuration  >  Administrative Templates > System  >  Device Protection  >  Turn on Virtualization Based Security .
   • Select Disable .
2. Go to Control Panel  >  Uninstall a Program  >  Turn Windows features on or off to turn off Hyper-V .
3. Choose not to reboot .
4. Remove the relevant EFI variables by launching a command prompt on the host with an administrator account and running the following commands:
   

   mountvol X：/ s 
   copy％WINDIR％\ System32 \ SecConfig.efi X：\ EFI \ Microsoft \ Boot \ SecConfig.efi / Y 
   bcdedit / create {0cb3b571-2f2e-4343-a879-d86a476d7215} / d“DebugTool”/ application osloader 
   bcdedit / set {0cb3b571-2f2e-4343-a879-d86a476d7215} path“\ EFI \ Microsoft \ Boot \ SecConfig.efi “ 
   bcdedit / set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215} 
   bcdedit / set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO，DISABLE-VBS 
   bcdedit /set {0cb3b571-2f2e- 4343 -a879-d86a476d7215}devicepartition= X:
   mountvol X：/ d 

   Note : Make sure  X  is an unused drive, otherwise change to another drive.
5. Reboot the host.
6. Accept the prompts on the splash screen to disable Device Guard or Credential Guard.

According to the above method, the blogger successfully solved the problem.

 

 

Author: Xinxin Xin, published in   Blog Park

Please indicate the source when reprinting. Email communication is welcome: [email protected]