Hi Jonathan, You mentioned: > but not on the latest version of VirtualBox which is also broken in the same way.
Does it means you are not able to use VirtualBox at all even without using Vagrant as wrapper? If this is the case it is most probably an issue with VirtualBox (or Windows) itself rather than with Vagrant. Can you check if there is any machine in VirtualBox left in an incorrect state? Also, according to the Vagrant output, the vagrant up operation failed on the execution of the following command: VBoxManage.exe startvm 2fb0ece3-53ed-4a06-b08d-530e9e0bd327 --type headless You should check: - Is the machine listed in VBoxManage.exe list vms - If so, does executing the startvm command above works? If the command does not work from the commandline, then the issue is not related to Vagrant and you should open a ticket with VirtualBox support/community. Daniele -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/79604d6b-7f93-420a-966b-0ebd19614761%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
