I recently saw similar behavious under Windows 10 using Vagrant and VirtualBox. It turned out to be caused by VirtualBox not running as administrator. If this is the cause of the problem then right clicking (perhaps with shift held down) on the VirtualBox icon should give you the option to run as administrator.
-- 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/93ba8f4c-0ecf-4f14-b90d-fb2577cc5f69%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
