Shulou(Shulou.com)06/02 Report--

In the latest version of WIN10, Microsoft introduced a security mechanism based on a virtualization container, which simply means that the system kernel is run in an isolated container, which is made of Hyper-V, which causes Hyper-V to seize the virtualization resources of VMware.

The solution can be https://kb.vmware.com/s/article/2146361?lang=zh_CN according to the vmware official solution.

Step 1: disable Device Guard Group Policy configuration

Run gpedit.msc to find Device Guard

Double-click to open virtualization-based security, select disabled, and make sure

Step 2: turn on "enable or disable windows function", uncheck Hyper-V, and do not restart after confirmation.

Step 3: run cmd as an administrator and run the following command to delete the relevant EFI variables:

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

For mountvol X: / d in the last sentence, please select your own non-system installation disk letter, preferably an unused disk drive.

Step 4: restart the system and follow the on-screen prompts after booting

The above is the whole content of this article, I hope it will be helpful to your study, and I also hope that you will support it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.