Hi Creighton,
Strange! I've been using the Vagrant box on Windows machines as long as we have been offering our Vagrant box, and I've never seen this. When you ran the original commands, were you using cmd on your computer, or the Windows PowerShell? If the latter, I might suggest starting over with the default command terminal - PowerShell adds all kinds of extra layers of abstraction on top that could be interfering. However, I'm assuming the former.
In light of that, I did a quick search for this issue online, and came up with the following - seems that Windows 7 and certain versions of Vagrant have a known issue:
Scrolling through the comments, it looks like there are at least 3 possible workarounds:
- Downgrade your Vagrant version - sounds like v1.9.6 worked for people. However, I don't think this is a great solution.
- Upgrade your PowerShell version - sounds like once people were running PowerShell 5, this ceased to be an issue
- Use the task manager to kill powershell.exe twice in a row - apparently this allowed Vagrant to continue.
I didn't read closely, just scanned - you may want to do some more digging and close reading and link following on your own.
I don't think it's related to this issue, but while I'm here I thought I'd mention this in case it helps at some point: one thing to check as a Windows user - make sure that the Virtualbox NDIS6 Bridged Networking Driver option is enabled in your network adapter settings. I've posted tips on how to check this in the forum previously, here:
Good luck! Let us know if you get it working.
Cheers,