Re: [vagrant-up] Vagrant update to 1.92 timeout after windows update

I have tried the latest, the 5.14 and the last stable build of 5.0. It's clearly not an issue with just having an old version because they all work the same way here. On Wednesday, March 22, 2017 at 3:40:08 PM UTC-4, Alvaro Miranda Aguilera wrote: > > ensure you are on latest virtualbox > > On

Re: [vagrant-up] Vagrant update to 1.92 timeout after windows update

ensure you are on latest virtualbox On Wed, Mar 22, 2017 at 3:35 AM, Mike Thomsen wrote: > For what it's worth, I just started having this problem as well. I try to > post that debug output tomorrow if no one beats me to it. Yay Microsoft > QA... > > On Thursday, March

Re: [vagrant-up] Vagrant update to 1.92 timeout after windows update

For what it's worth, I just started having this problem as well. I try to post that debug output tomorrow if no one beats me to it. Yay Microsoft QA... On Thursday, March 16, 2017 at 3:47:18 PM UTC-4, Alvaro Miranda Aguilera wrote: > > hello > > try this > > vagrant halt > > then go to

Re: [vagrant-up] Vagrant update to 1.92 timeout after windows update

hello try this vagrant halt then go to virtualbox gui, and try to start the vm from there it may help as will give you more information >From vagrant side try this vagrant version vagrant plugin list mkdir precise64 cd precise64 vagrant init -m hashicorp/precise64 set VAGRANT_LOG=debug

[vagrant-up] Vagrant update to 1.92 timeout after windows update

Hello, I recently updated my windows 10, vagrant and virtualbox and my vagrant won't boot anymore. The warning I get is: "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"