Vagrant 流浪汉'；等待机器启动时超时'；在windows 10中

我最近更新了windows10并尝试运行虚拟机，但它让我重复了相同的错误次数“等待机器启动时超时”，我尝试了所有可能的方法，启用gui，增加超时值，甚至更新了vagrant和virtual box

C:\Users\tmsfi\fullstack-nanodegree-vm\vagrant>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'bento/ubuntu-16.04-i386' is up to date...
==> default: There was a problem while downloading the metadata for your box
==> default: to check for updates. This is not an error, since it is usually 
due
==> default: to temporary network problems. This is just a warning. The 
problem
==> default: encountered was:
==> default:
==> default: Could not resolve host: vagrantcloud.com
==> default:
==> default: If you want to check for box updates, verify your network 
connection
==> default: is valid and try again.
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 8000 (guest) => 8000 (host) (adapter 1)
default: 8080 (guest) => 8080 (host) (adapter 1)
default: 5000 (guest) => 5000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

C:\Users\tmsfi\fullstack-nanodegree-vm\vagrant>vagrant ssh
ssh_exchange_identification: read: Connection reset by peer 

请帮我解决这个问题，提前谢谢

---

Meghana

我已经解决了这个问题，我们将面临这个问题，因为我们的系统中禁用了虚拟化。要检查虚拟化是启用还是禁用，请转到您的

Taskmanager-->Performance

检查是否启用或禁用了虚拟化，如果禁用，则启用它当我们的windows更新到最新版本时会发生这种情况我们需要在BIOS设置中启用虚拟化，要执行此操作，请转到

setting-->Update&Security-->Recovery-->Advance startup-->click(restart now)

重新启动后，它提供了一些选项，然后单击

Troubleshoot-->Advanced options-->Select UEFI Firmware Settings-->Click 
Restart.

您的系统将重新启动并进入BIOS。现在启用“英特尔虚拟技术”，保存并重新启动系统

---

请参阅此

可能重复的感谢@Danielsmirnovalso，请确保HyperV已关闭，我在文档中忽略了此项，并浪费了2天时间修复此项：