Virtualbox throwing errors on Windows 10 TP on vagrant up

Question

The VM I was trying to run was running perfectly on a Windows 7 machine. I had upgraded to Windows 10 and tried out the same machine (with all the same configs and vagrant boxes), uninstalled and reinstalled virtualbox several times, but it still doesn't work.

Tried making a brand new VM - that didn't work too.

Here's the error

Some people who had similar 'hostonly' errors have suggested to restart the VirtualBox service from terminal, but I don't know the Windows equivalent of that command.

Anybody had this error before? How do I solve this?

Answer 1

A test build is available at https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-101902-Win.exe . This should fix the host-only interface creation problem by introducing a 5-second timeout when querying the registry key. We would appreciate feedback (i.e. does it fix the host-only interface creation errors or not, is the timeout long enough). https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-101902-Win.exe

See https://www.virtualbox.org/ticket/14040#trac-change-55

Uninstalling the current VirtualBox and installing the testbuild worked for me

Answer 2

I have the same error and it seems to be a problem with changed network security in Windows and still no updated for it in Virtualbox.

Answer 3

Not pretty but a working solution (tested under Win10 build10130). This is what I did to get homestead up and working

1. Uninstall Vagrant and VirtualBox (restart if necessary)
2. Install notepad+ or other notepad replacement that handles linux line-endings
3. Download Vagrant v1.7.2, VirtualBox 5.0RC1, VirtualBox v4.3.6
4. Enable built-in administrator account. net user administrator /active:yes
5. switch to Administrator account
6. Install Vagrant v1.7.2 (restart if necessary, log back into Administrator)
7. Install VirtualBox v5.0RC1
8. Install VirtualBox v4.3.6
9. Update VBox Host-Only adaptor driver (device manager,Search Automatically)
10. Edit VagrantFile file (where ever you vagrant up from) and change all ~/ to C:/Users/username/
11. Edit Homestead.yaml (Where ever you had it, likely C:\Users\username\.homestead) and change all ~/ to C:/Users/username/
12. Open VirtualBox
13. Run vagrant up
14. switch back to your usual user (do not sign out of Adminstrator)

hey presto, you have a working homestead

Each time after to manage vagrant (start, halt, whatever) switch to Administrator, manage, and switch back to your usual user. Do not sign out of the Administrator account when switching if you have a box up