Win10不识别VT-x虚拟化

Joe

July 31, 2019

936 views

No comments

3484 words

Windows

在使用安卓模拟器的时候发现了这个问题,同样virtualbox也无法工作.

bios中虚拟化开关已开启
win10任务管理器中虚拟化显示已开启
Hyper-v及其相关服务保活sandbox已关闭
在双系统Ubuntu16.04中可以正常使用虚拟机

20200114更新:在新买的电脑上遇到同样的问题,除了关闭hyper-v和sandbox,出现此问题的原因是Device Guard或Credential Guard与Workstation不兼容,不要随意执行带更改bcd引导属性的命令
先关闭windows defender-设备安全性-内核隔离,然后尝试启动虚拟机,如果不可以则
禁用用于启用Credential Guard的组策略设置。
在主机操作系统上，右键单击“开始” > “运行”，键入gpedit.msc，然后单击“ 确定”。本地组策略编辑器打开。
转至本地计算机策略 > 计算机配置 > 管理模板>系统 >Device Guard（或者是：设备防护） > 启用基于虚拟化的安全性。
选择已禁用。

这说明问题出在win10系统上,并不是主板的问题,国内的回答都无效,google到下面最有效的答案
https://superuser.com/questions/1153470/vt-x-is-not-available-but-is-enabled-in-bios
我用的方法:
As mentioned in another answer, Core isolation, Application Guard, Credential Guard and Device Guard utilize the Hyper-V feature. If you don't need that level of security you can disable them by running

DG_Readiness_Tool_v3.5.ps1 -Enable -AutoReboot

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:
bcdedit /set hypervisorlaunchtype off
mountvol X: /d

More detailed information about those commands can be found on Manage Windows Defender Credential Guard

However on Windows 10 Build 18305 and up, beside the guard features, Windows Sandbox will also enable Hyper-V, because it's also a thin layer of virtualization

If you want to use the sandbox feature then unfortunately you can't disable Hyper-V like in other answers. There are 2 solutions for this

Use Hyper-V instead. If you have VMs running in other hypervisors like VirtualBox then just migrate them to Hyper-V
Enable nested paging so that you can run other hypervisors inside Hyper-V. Simply run the below command to enable that feature

Set-VMProcessor -VMName -ExposeVirtualizationExtensions $true

For more information read