vmware workstation12 installation centos prompts VMware Player and Device/Credential Guard are incompatible, reasons and solutions

In the latest version of WIN10, Microsoft introduced a security mechanism based on virtualization containers. Simply put, it puts the system kernel into an isolated container to run it to improve security. This isolated container is made with Hyper-V, which causes Hyper-V to seize VMware's virtualization resources.

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

Step 1: Disable Device Guard Group Policy Configuration

Run gpedit.msc and find Device Guard

Double-click to open virtualization-based security, select Disabled, and confirm

Step 2: Open "Enable or disable Windows features", uncheck Hyper-V, and do not restart after confirming;

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

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

Step 4: Restart the system and follow the on-screen instructions after booting up

The above is the full content of this article. I hope it will be helpful for everyone’s study. I also hope that everyone will support 123WORDPRESS.COM.