Vagrant up after upgrade to Windows 10
Solution 1
This is how I got my Vagrant to finally work on Windows10:
- Uninstall both VirtualBox and Vagrant (backup the old vagrantmachines)
- Download and install VirtualBox and the latest Vagrant
Solution 2
There is a released fix for virtual box on https://www.virtualbox.org/ticket/14040
For those using homestead a solution can be found on https://laracasts.com/discuss/channels/general-discussion/windows-10-vagrant-virtualbox-homestead
Solution 3
For some reason the VirtualBox Host-Only Ethernet Adapter
was removed once the upgrade to Windows 10 was completed. Removing, rebooting and installing VirtualBox resulted in the installation of the removed Ethernet adapters again and the issue has been solved.
Solution 4
Another fix is to add name: "VirtualBox Host-Only Ethernet Adapter"
after config.vm.network in your Vagrant file. In my case:
config.vm.network "private_network", ip: "192.168.33.10", name: "VirtualBox Host-Only Ethernet Adapter"
Vagrant, Virtual Box 4.3
Chris
Updated on June 30, 2022Comments
-
Chris almost 2 years
I am trying to vagrant up after my recent upgrade to windows 10, and I get an error:
==> default: Clearing any previously set network interfaces... There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below. Command: ["hostonlyif", "create"] Stderr: 0%... Progress state: E_FAIL VBoxManage.exe: error: Failed to create the host-only adapter VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available) VBoxManage.exe: error: Context: "int __cdecl handleCreate(struct HandlerArg *,int,int *)" at line 66 of file VBoxManageHostonly.cpp
Before the upgrade it worked fine, has anyone figured out how to fix this?