我已经安装了Docker，当我运行GUI时，我得到这个错误:
硬件辅助虚拟化和数据执行保护必须 在BIOS中启用
似乎是一个bug，因为Docker在命令行中工作得很好，但我想知道是否有人知道为什么会发生这种情况?
在你问之前，是的，我已经在BIOS中启用了虚拟化，并且英特尔处理器识别实用程序确认它已被激活。Docker, Docker -machine和Docker -compose都可以在命令行中工作，Virtualbox可以，在Debian或Ubuntu虚拟机中运行Docker也可以。
GUI有个奇怪的问题。
我的规格:
Windows 10 Pro x64周年纪念版 英特尔酷睿i5-6300HQ @ 2.30GHz
当前回答
遵循以下步骤:
进入:windows设置=>更新和安全=>恢复=>高级启动，然后单击:立即重新启动。 故障排除=> Advanced Option => UEFI Firmware =>重启。 进入“Bios => configuration => Virtualization technology =>”。 保存更改，它就会工作。
其他回答
如果启用了所描述的特性，则问题在于Hyper-V被禁用或Hypervisor代理未运行。
解决方案A(如果Hyper-V完全禁用或未安装)
以管理员身份打开PowerShell 启用Hyper-V dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All
解决方案B(如果Hyper-V功能已经启用但不工作)
使用
bcdedit /set hypervisorlaunchtype auto
现在重新启动系统并重试。
解决方案C
如果问题仍然存在，可能是系统上的Hyper-V损坏了，所以
进入控制面板->[程序]-> [Windows功能]，完全取消选中所有Hyper-V相关组件。重新启动系统。 再次启用Hyper-V。重新启动。
注1:
Hyper-V needs hardware virtualization as prerequisite. Make sure your PC supports it, if yes and still won't work, there is the possibility your BIOS is not configured correctly and this feature is disabled. In this case, check, enable it and try again. The virtualization features could be reported under different names according the platform used (e.g if you don't see any option that uses virtualization label explicitly, on AMD you have to check SVM feature state, on Intel the VT-x feature state).
注2:
Hyper-V只能安装某些版本，例如:
Windows 10企业版;Windows 10 Professional;Windows 10教育。
Hyper-V不能安装在便宜的或移动的Windows版本上，例如:
Windows 10家庭版;Windows 10 Mobile;Windows 10移动企业。
我尝试了这里的许多建议，但都没能让它运行起来。最后对我有用的是直接进入BIOS激活它。下面的文章很有帮助: https://www.nextofwindows.com/how-to-enable-configure-and-use-hyper-v-on-windows-10
遵循以下步骤:
进入:windows设置=>更新和安全=>恢复=>高级启动，然后单击:立即重新启动。 故障排除=> Advanced Option => UEFI Firmware =>重启。 进入“Bios => configuration => Virtualization technology =>”。 保存更改，它就会工作。
对我来说，我所要做的就是卸载VMware。
Docker现在正在运行
I don't know how this works, and I don't even know what these commands do, I don't know what is hypervisor or what it does that it interferes with Docker, and I don't know what the nx means in the second command which it is apparently turning it off. I had these commands saved on my computer as "Turn VT-x off" (yet another thing that I don't know what it is, I think it's related to Virtualization Technology which I don't know what that does/is either). But nothing else worked for me (including the accepted answer (which I tested all of it's solutions) and other upvoted answers, although I didn't read all of them), except running both of these. It is completely up to you to test these, I do not guarantee any fixes to you, but it worked for me, I put it in here because I thought it might be helpful for someone else like me who also didn't find other answers to be that helpful:
bcdedit /set hypervisorlaunchtype auto
bcdedit /set nx AlwaysOff
shutdown /s
