最近更新到 Windows 10 后，VMWare Workstation 无法在 Windows 10 上运行
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/50374506/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
VMWare Workstation cannot run on Windows 10 after recent update to Windows 10
提问by Weishan Yang
I've Windows 10 Pro system, and use Hyper-V on that system. Due to the needs of device redirection doesn't works well with Hyper-V, I've installed VMWare Workstation 14.
我有 Windows 10 Pro 系统，并在该系统上使用 Hyper-V。由于设备重定向的需要不适用于 Hyper-V，我安装了 VMWare Workstation 14。
I have to disable Hyper-V to make VMWare Workstation work, at beginning. It worked until last weekend , seems because of the QFE update. I just verified, it was not QFE but Feature update to Windows 10, version 1803 that triggered the problem with VMWare Workstation again.
一开始，我必须禁用 Hyper-V 才能使 VMWare Workstation 正常工作。它一直工作到上周末，似乎是因为 QFE 更新。我刚刚确认，不是 QFE 而是 Windows 10 版本 1803 的功能更新再次引发了 VMWare Workstation 的问题。
- After Windows update completed (after reboot), I tried to start a VM in VMWare. I get the error dialog complaining about Device/Credential Guard.
- Windows 更新完成后（重新启动后），我尝试在 VMWare 中启动 VM。我收到错误对话框，抱怨 Device/Credential Guard。
- Following the instruction in this link: https://kb.vmware.com/s/article/2146361, and after the reboot, I get another complaint about incompatibility with Hyper-V.
- 按照此链接中的说明进行操作：https: //kb.vmware.com/s/article/2146361，在重新启动后，我收到另一个关于与 Hyper-V 不兼容的投诉。
- After reset the Hyper-V selection in Windows Feature or confirm that HyperV is not already removed, and reboot, the first error came back.
- 在 Windows 功能中重置 Hyper-V 选择或确认 HyperV 尚未删除后，重新启动，第一个错误又回来了。
It gets in a loop of error complaining about Device Guard and complaining about Hyper-V for VMWare.
它陷入了一个错误循环，抱怨 Device Guard 和抱怨 VMWare 的 Hyper-V。
回答by Weishan Yang
Ok, thanks to the answer from communities of VMWare: https://communities.vmware.com/thread/588526
好的，感谢来自 VMWare 社区的回答：https: //communities.vmware.com/thread/588526
The issue is now gone, by applying the following change:
通过应用以下更改，问题现已消失：
Disable credential guard by using readiness tool from Microsoft: https://www.microsoft.com/en-us/download/details.aspx?id=53337, with this command: DG_Readiness_Tool_v3.2.ps1 -disable
Disable Hyper-V by using PowerShell command: Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
Reboot and accept to boot without CG/DG.
使用 Microsoft 的就绪工具禁用凭证保护：https://www.microsoft.com/en-us/download/details.aspx?id=53337，使用以下命令：DG_Readiness_Tool_v3.2.ps1 -disable
使用 PowerShell 命令禁用 Hyper-V：Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
重新启动并接受在没有 CG/DG 的情况下启动。
Although I don't like that VMWare cannot work together with device guard from system, I get my VM working for the moment.
虽然我不喜欢 VMWare 不能与系统中的设备保护一起工作，但我暂时让我的 VM 工作。
回答by jellad.tarek
1- run cmd as admin
1-以管理员身份运行cmd
2- run : bcdedit /set hypervisorlaunchtype off
2-运行：bcdedit /set hypervisorlaunchtype off
3- reboot
3-重启
let me knew if it works please
请让我知道它是否有效
good luck
祝你好运
回答by Justin Ron
here are the few steps for you to solve this issue:
以下是您解决此问题的几个步骤：
- Disable the HvHost service (and any other services with prefix Hyper-V if needed) from windows TaskManager(Ctrl+Alt+Del)
- use the tool from the official website
- Uncompress the downloaded zip file to your own directory, take C:\DG_Readiness_Tool_v3.5here for instance.
Run Windows PowerShell as admin, type the following two commands:
cd C:\DG_Readiness_Tool_v3.5.\DG_Readiness_Tool_v3.5.ps1 -DisableReboot
- 从 Windows 任务管理器（Ctrl+Alt+Del）禁用 HvHost 服务（以及任何其他带有 Hyper-V 前缀的服务，如果需要）
- 使用官方网站上的工具
- 将下载的zip文件解压到自己的目录下，这里以C:\DG_Readiness_Tool_v3.5为例。
以管理员身份运行 Windows PowerShell，键入以下两个命令：
cd C:\DG_Readiness_Tool_v3.5.\DG_Readiness_Tool_v3.5.ps1 -Disable重启
回答by kalscode
Adrian at https://answers.microsoft.com/en-us/windows/forum/windows_10-security/cannot-disable-memory-integrity-core-isolation-in/29ac5ce4-30d2-47d1-ab17-734980fd287bsays "I think it's a bug that this cannot be disabled via UI but fortunately it's possible through the registry by setting the following key to 0:"
阿德里安在https://answers.microsoft.com/en-us/windows/forum/windows_10-security/cannot-disable-memory-integrity-core-isolation-in/29ac5ce4-30d2-47d1-ab17-734980fd287b说“我认为这是一个无法通过 UI 禁用的错误，但幸运的是，可以通过将以下项设置为 0 来通过注册表：”
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity\Enabled
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity\Enabled
This worked for me as well [Windows 10 Pro Version 1803(OS Build 17134.112, VMWare Workstation 14 Pro Version 14.1.2]
这对我也有效 [Windows 10 Pro Version 1803(OS Build 17134.112, VMWare Workstation 14 Pro Version 14.1.2]
