Vboxmanage exe error failed to create the host only adapter

I am getting this exact error on two machines with Windows 10 + virtualbox 4.x/5.0 + vagrant 1.7.

@bhouston you installed this patch? it worked? if so, how can I install it?

[too many questions 😆]

Edit.

Actually, I saw that everybody in the ticket have the same problem to install. Damn! I lost a work day because I didn’t knew this issue on Windows 10.

I’ll have to find a way to get back to work properly.

I understand applying the patch is difficult because it requires modification of a cert signed driver. I’m not going to try that for the first time today. I think the key is to exert pressure on VirtualBox to prioritize this fix — I’ve tweeted at them about it today and I’ve posted on that bug (I’m doing that right now), I encourage you to also pressure them in some way as well — we all need this fixed ASAP.

I tweeted them twice since yesterday but no response at all. It frustrates me that the VB issue was submitted 4 months ago, so it shouldn’t be a surprise to them.

However, I’ve found this workaround on multiple places:

1. remove the line setting the private network in the vagrant file
2. remove the line b.use ClearNetworkInterfaces in Vagrantembeddedgemsgemsvagrant-1.7.4pluginsprovidersvirtualbox (it’s on line 64 in 1.7.4 at least)
3. vagrant up
4. vagrant halt
5. in VB’s general settings, edit the host-only adapter manually and set the preferred IP
6. make sure this host-only adapter applies to the current machine
7. vagrant up

This worked for me, however I can’t get samba to work. I hope this will be fixed by the same VB release otherwise I’m still screwed

@dvh you use a third party box or your own? I use Scotch Box and don’t know if it would break the box and bring me more problems. 😔

About VirtualBox on Twitter, I didn’t get any response, but I tweeted about 30 minutes ago.

I use my own. But I quit it also because I can’t work without a working samba share

The same problem: Windows 10 RTM + Vagrant 1.7.4 + Virtual Box 5.0

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: «enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)» at line 70 of file VBoxManageHostonly.cpp

The same from my side:

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 in
fo not available)
VBoxManage.exe: error: Context: «int __cdecl handleCreate(struct HandlerArg *,in
t,int *)» at line 66 of file VBoxManageHostonly.cpp

Can’t start genymotion! Same prombleb! Fix this shit please bro

Same problem here, but seems this bug is not a priority for the VirtualBox team…

Appending to @dvh’s temporary solution, I had to comment out also the next line. In my case commenting following in file c:Program Files (x86)Vagrantembeddedgemsgemsvagrant-1.7.4pluginsprovidersvirtualboxaction.rb helped:

b.use PrepareNFSSettings
#b.use ClearNetworkInterfaces
#b.use Network
b.use ForwardPorts

However bear in mind, that this is only temporary solution and will probably force you set up the network adapters manually via VirtualBox GUI if they weren’t set up correctly before.

@rootpd, your workaround outlined in this comment is the first one that worked for me: #6059 (comment) Thank you so much!

@rootpd, it worked! Nice temporary fix!

Coz private_network doesnt work (temporary) i needed to modify my Vagrantfile to forward some ports to see my website:
config.vm.network :forwarded_port, guest: 80, host: 8080

And in Windows access with: http://127.0.0.1:8080

Thanks @lewins — that port forwarding edit above has got me up and running. Vagrant up gave me a load of «default: Warning: Remote connection disconnect. Retrying…» notices but it booted in the end

After @rootpd and @lewins changes, I keep receiving «Warning: Authentication failure. Retrying…» errors and it eventually times out. This configuration is from https://puphpet.com/. Any help would be appreciated. Thanks!

Im not using puphet but i think your ssh auth keys are not set properly. check ur ~/.ssh/ folder

@lewins — It’s supposed to use the puphpetfilesdotssh keys. At least that’s how it normally works with a Puphpet install. Not sure what’s happening now…

Another solution is to manually create a Host-Only Adapter from VirtualBox GUI (or using VirtualBoxManage). You will get error even when manually add it (because of the same VirtualBox bug) but the adapter will be created properly.

Then specify the IP and the adapter name in your Vagrantfile

config.vm.network "private_network", ip: "169.254.46.99", name: "VirtualBox Host-Only Ethernet Adapter"

The trick is that specifying name will skip creating of virtual adapters along with this error.
Don’t comment in vagrant source files, you skip a ton of other important things.

@venimus Thanks. I tried that but I’m still getting the same error «default: Warning: Authentication failure. Retrying…»

@aaronstum May be it is a configuration issue. Check if both IPs are the same in Vagrantfile and VirtualBox adapter.

I probably was not clear. The IP in Vagrantfile should be in the same network as the hostonly adapter but should not be the same.

@alexsouza Just upgraded to Windows 10 and followed the solution on the lezgro blog, worked a treat! Many thanks!

venimus stumbled on the answer Specifiy as shown below in the Vagrantfile Leaving the line without a name causes the issue.

config.vm.network «private_network», ip: «169.254.46.99», name: «VirtualBox Host-Only Ethernet Adapter»

For what it’s worth, I was encountering the same problem with at freshly generated vagrant file from puphpet, and running Windows 7.

I was able to get it to work:

• updated vagrant to 1.7.4
• updated virtualbox from 4.3.30 to 4.3.32 (http://download.virtualbox.org/virtualbox/4.3.32/) — installed as administrator after Win said the initial installation may not have worked
• reboot
• start cmd as administrator
• cd …
• vagrant up

I can only presume that in those 2 minor VB versions something got patched. I don’t know if the couple of «run as administrator» notes make a difference.

Yeah this is an unfortunate VirtualBox issue. I think there is enough Google-juice here to guide users. And new users appear to be mostly unscathed so I think VirtualBox has fixed this in later versions. Sorry folks!

I modified the vagrantfile：
config.vm.network "private_network", ip: "192.168.33.10"
The console told me the following：

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

When I hide the configure,it works!
# config.vm.network "private_network", ip: "192.168.33.10"

Run the vmbox:
vagrant up

Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Clearing any previously set network interfaces…
==> default: Preparing network interfaces based on configuration…
default: Adapter 1: nat
==> default: Forwarding ports…
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM…
==> default: Waiting for machine to boot. This may take a few minutes…
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM…
==> default: Mounting shared folders…
default: /vagrant => E:/VirtualBox
default: /vagrant_data => E:/VirtualBox/app
==> default: Machine already provisioned. Run vagrant provision or use the --provision
==> default: flag to force provisioning. Provisioners marked to run always will still run.

Hope this can help you.

Just FYI as I came across this trying to solve the problem, I am having this issue on a fresh Windows 10 install with Vagrant 1.8.1 and VirtualBox 5.0.14. Tried many workarounds but no dice yet.

Following an update to my Windows 10 machine last night, I get this issue now where I wasn’t before.

Version 1511 (OS Build 10586.104)

The workaround from @engine-go worked for me — I already had the interface (along with several spurious ones which I deleted), and I have the executables (Virtualbox.exe, SVC, Manage and Headless) to run in Win8 compatibility mode, so the solution may require at least those steps.

I upgraded VirtualBox and this is no longer an issue

@engine-go your solution worked for me but how do you set the ip of the VM then? Through the Virtualbox gui?

I had the same problem so i fixed this issue when im installing of new version to VM. I think it´s very funy because i tried the solution 14040 and not working for me.

I got the same problem but I only restarted VirtualBox by restarting the whole machine and repeated the same process and it worked

FWIW, I had this issue, I tried uninstalling/re-installing VB, then had VB open when I did ‘vagrant up’ and it worked no problem. ¯_(ツ)_/¯

I had exact same error on my mac. I tried reinstalling virtualbox and that fixed the issue.

Following solution worked for me:

1. Goto C:Program FilesOracleVirtualBoxdriversnetwork
2. There are two folders, go inside both of them and right click on .inf and click Install
3. Head over to Control PanelNetwork and InternetNetwork Connections
4. Right click on Network Adapter and choose Properties
5. Click on Install => Service
6. Under Manufacturer choose Oracle Corporation and under Network Service, choose VirtualBox NDIS6 Bridged Networking driver
7. Ok and Close

Preview

Finally, run

Hope this helps you!
Kalpesh Panchal

same issue, I just ran the fix file and the error still shown, any help would be thankful.

@panchalkalpesh solution worked for me, but, I installed the service for both virtualbox network adapters.

@panchalkalpesh Someone give this man a medal. well as far as I understand the network adapter didn’t install automatically on my machine since kaspersky was on at the time I installed vbox, so.. if you can just reinstall vbox with kaspersky off, does the same.

@rootpd solution worked for me. Thank you, i almost lost 2 days

MI problema fue el Firewall , desinstale el firewall y actualice el virtual box

I’m going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.