VMware and Device / Credential Guard is not compatible, solutions and experiences

Baidu case you want to cancel the Hyper-V feature, but I use docker, as well as some related posts are invalid

https://blog.csdn.net/u013667796/article/details/85843151

Own research solutions, according to official documents,

https://kb.vmware.com/s/article/2146361

We need to close the DG / CG, and then link all of Microsoft's documentation

https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-manage

Directly to Disable method

To edit Group Policy and delete registry. Not a good feeling to provoke, to continue to scroll down to see

Surprise, there are tools to solve step

https://www.microsoft.com/en-us/download/details.aspx?id=53337

Unzip download

Inside the script is this ps1 file suffix, according to official documents, non-English systems should script

$OSArch = $(gwmi win32_operatingsystem).OSArchitecture

Changed

$OSAch = $((gwmi win32_operatingsystem).OSArchitecture).tolower()

Storage

ps1 use powershell open, the administrator starts! Administrators start! Administrators start!

Locate the folder location, I was in the download folder,

Then run

DG_Readiness_Tool_v3.6.ps1 -Disable -AutoReboot

You may encounter problems as shown below, not encountered on the computer will automatically restart 30s, you can skip the following paragraph

Then I added in front of the recommendation. \ Run

There are still problems, according to Web site

https://docs.microsoft.com/zh-cn/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-6

Full-page read roughly swept aside, talking about the rights issue powershell scripts run

Enter the first in powershell

Get-ExecutionPolicy

可以看到我们先在是处于受限状态,不能运行脚本

然后更改权限为RemoteSigned

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

更改成功!

重新运行

.\DG_Readiness_Tool_v3.6.ps1 -Disable -AutoReboot

会有一张类似下面这张图的(我已经修改过一遍了,可能有点不一样)

中间会说系统不到指定表是正常的,这些原本就是要被删除的,找不到也无所谓

 然后就是重启,回进入到下面这个画面

这就是最早官方文档要我们Disable的东西,F3确认,

下一个是要我们是否disabe虚拟化的基础安全的东西,我也F3确认了,

然后开机,打开VMWare,继续学习鸟哥的linux课程了。

最后,如果需要重新enable的话可以根据上面的微软官方文档中的信息重新启用组策略

https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-manage

最后的最后,附上随手找到的一个关于这个Decive guard的介绍

https://docs.microsoft.com/zh-cn/previous-versions//dn986865(v=vs.85)

 

 

后续,打开后Docker无法打开

报“Hardware assisted virtualization and data execution protection must be enabled”

查询了一下,发现vmware和docker不兼容,参考

https://blog.csdn.net/u012588542/article/details/85378508

https://blog.csdn.net/W_C_X/article/details/89474587

但是没有这么复杂的解决办法,用docker就启用守护进程,重启,用vmware就关闭守护进程,重启

1,如果用docker,
在cmd,以管理员身份运行:
bcdedit /set hypervisorlaunchtype auto
重启
2,开启虚拟机linux
在cmd中,以管理员身份运行:
bcdedit /set hypervisorlaunchtype off
重启

现在知道了,最开始那个csdn的帖子的那一行命令的用处了,自己当时还不知道要用管理员运行那一行命令。。。

绕了好大一圈才解决

 

Guess you like

Origin www.cnblogs.com/powerzzjcode/p/11110542.html