Fixing VBoxManage E_FAIL after Windows 10 Upgrade
August 21, 2015 8:35 pm Leave your thoughts
One of the most annoying issues that happened to all of my machines after upgrading to Windows 10 is that I started getting VirtualBox errors as soon as I started to a virtual machine via Vagrant. This is an issue since most of my projects are developed using Vagrant. After all, Vagrant is really the thing that makes cross platform development easier.
The actual error messages were:
|
1 2 3 4 |
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 __cdec1 handleCreate(struct HandlerArg *,int,int *)" at line 66 of file VBoxManageHostonly.cpp |
When I look at the above, that wasn’t very useful at first glance. However I know it’s something to do with host only networking. So I opened up the virtual box GUI and went to file->preferences->network and chose Host-only networking. I then proceed to add a new network adapter. Unfortunately I was then greeted by the error below:
|
1 2 3 |
Failed to create the host network interface Result Code: E_FAIL (0x80004005) |
Since trying to add the network doesn’t work, I then tried looking into my device manager and it was evident that under Network adapters the VirtualBox adapters are missing.
The Solution
In order to save you all the time diagnosing this issue, there are only 2 things that you have to do:
- Uninstall VirtualBox completely then install the latest VirtualBox. That seems to completely re-install the network adapters.
- Upgrade / re-install Vagrant with the latest version.
After doing the two things above, I was able to vagrant up as normal and brought up the virtual machine.
That’s it! Hopefully this saves you countless hours troubleshooting this vague issue.
Categorised in: General article, Software Development