Vagrant: Command: ["hostonlyif", "create"] error with windows 10

[erdemece]

I have virtualbox 5.0 + vagrant 1.7 + phpuppet I'm having this problem. Could it be vagrant related? Because other virtual machines like ubuntu, macos, windows are working fine. Only vagrant machines have problem.

Every time I do vagrant up windows asks me to allow virtualbox then I receive following error on my console.

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

[bhouston]

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

[bhouston]

Appears to be a problem with VirtualBox + Windows 10 and they say there is a patch available but no new official version of VirtualBox yet:

https://www.virtualbox.org/ticket/14040

[guilhermemarconi]

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

[too many questions :laughing:]

---

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.

[bhouston]

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.

[dvh]

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 \Vagrant\embedded\gems\gems\vagrant-1.7.4\plugins\providers\virtualbox (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 :(

[guilhermemarconi]

@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. :pensive:

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

[dvh]

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

[dmdnkv]

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

[stremann]

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

[antonsivogrivov]

The same!

[shadowzoom]

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

[hectorgimenez]

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

[rootpd]

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)\Vagrant\embedded\gems\gems\vagrant-1.7.4\plugins\providers\virtualbox\action.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.

[bhouston]

@rootpd, your workaround outlined in this comment is the first one that worked for me: https://github.com/mitchellh/vagrant/issues/6059#issuecomment-126655918 Thank you so much!

[ghost]

@rootpd, it worked! Nice temporary fix!

[ghost]

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

[hypertexture]

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 :)

[aaronsturm]

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!

[ghost]

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

[guilhermemarconi]

VirtualBox answered my tweet. Look: https://twitter.com/virtualbox/status/627187142238838784

After all that, I found a way to work without depend of Vagrant and VirtualBox with BrowserSync and it's working perfectly.

I hope that this VirtualBox issue is solved ASAP for you guys get back to work soon! :facepunch:

[aaronsturm]

@lewins - It's supposed to use the \puphpet\files\dot\ssh keys. At least that's how it normally works with a Puphpet install. Not sure what's happening now...

[venimus]

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.

[aaronsturm]

@venimus Thanks. I tried that but I'm still getting the same error "default: Warning: Authentication failure. Retrying..."

[venimus]

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

[dvh]

There is a fix available! I've tested it and it works with VB 5 and Vagrant 1.7.4: https://www.virtualbox.org/ticket/14040

[venimus]

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.

[antonsivogrivov]

With this .exe fix after vagrant up I have another error message:

There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "ipconfig", "VirtualBox Host-Only Ethernet Adapter #7", "--ip", "192.168.56.1", "--netmask", "255.255.255.0"]

Stderr: VBoxManage.exe: error: The host network interface with the given name could not be found
VBoxManage.exe: error: Details: code E_INVALIDARG (0x80070057), component Host, interface IHost, callee IUnknown
VBoxManage.exe: error: Context: "FindHostNetworkInterfaceByName(name.raw(), hif.asOutParam())" at line 218 of file VBoxManageHostonly.cpp
VBoxManage.exe: error: Could not find interface 'VirtualBox Host-Only Ethernet Adapter #7'

[ghost]

@tonygriv same here ))):

[erdemece]

Hi, thanks everyone.

My solution is here;
From Virtualbox you can't create host-only network because it gives you same error ""E_FAIL (0x80004005)"" but when you do vagrant up from your console it creates host-only networks but with different (random) IP without DHCP Server. You can edit one of those host-only network and attach to your virtual machine that you use with vagrant.

my ip in my vagrant file is 192.168.56.102 and these are my settings.

[antonsivogrivov]

I don't see any host-only networks :(

[jaminday]

With the fix at https://www.virtualbox.org/ticket/14040 I get the same error as @tonygriv when running vagrant up.

@erdemece your solution didn't work for me. If I create a new host-only adapter through Virtualbox GUI, as soon as I close the preferences window Virtualbox forgets about it (even though the adapter is still present in Device Manager). I can't attach it to the VM as it's no longer recognized.

[jaminday]

Update: Downgraded Virtualbox from 5.0 to 4.3 and now it works using the fix mentioned above (Windows 10/Vagrant 1.7.4).

[antonsivogrivov]

I have VB 4.3 and it's still not working :(

[negativefix]

I am also getting the same error with VB 4.3.

[ghost]

For anyone still having issues with existing machines:
My Setup:
Windows 10 Home (upgraded from 8.1)
VB 4.3.24
Vagrant 1.74
Ubuntu 14.0.4

I added the following line on my Vagrantfile

config.vm.network "forwarded_port", guest: 80, host: 8080
config.vm.network "private_network", ip: "55.55.55.5", name: "VirtualBox Host-Only Ethernet Adapter #4"
config.vm.network "public_network", ip: "192.168.0.45"

Additionally on the VB GUI
File>Preferences>Network
Made sure there was an adapter matching the name on the Vagrantfile for the private_network

On the VB machine enabled Adapter 2
Attached to: Host-only Adapter
Name: VirtualBox Host-Only Ethernet Adapter #4

Ran fix https://www.virtualbox.org/ticket/14040
executed Vagrant up

once the machine was up. I closed the fix. END

[slipnox]

Hi guys,

I am Windows 10 Pro was fighting with the issue too and solved this way, download the mentioned fix here https://www.virtualbox.org/ticket/14040 and follow this steps:

• Install latest VB 5.0
• Install latest Vagrant 1.7.4
• Restart the System
• Run the fix
• Vagrant up

Hope helps.

[sirolei]

@slipnox Thanks! It works very well.

[lokothodida]

@gonzd2 & @slipnox : when I run the fix I get a message from Windows (in a Metro modal dialog) saying

This app can't run on your PC
To find a version for your PC, check with the software publisher.

This is whether I run it normally or as an administrator. My setup is:

• Windows 10 Home (also upgraded from 8.1)
• Vagrant 1.7.4
• VirtualBox 5.0

[BinaryKitten]

btw the "fix" executable created by "Yirkha" listed on https://www.virtualbox.org/ticket/14040 - is an executable that adds a delay to an executing thread, it's not a patch against VirtualBox or a thing that will fix the issue, just acts as an intermediary and temporary workaround solution.

[BinaryKitten]

As a Heads up, https://www.virtualbox.org/ticket/14040 now has a Test build reported to correct the issue: VirtualBox-5.0.1-101902-Win.exe. It's reported by michaln on https://www.virtualbox.org/ticket/14040#comment:55

Please do go test and report back to them on your success.

[lokothodida]

@BinaryKitten: thanks for the links. michaln's new build and Yirkha's 32-bit workaround both seem to get around this specific issue for me (so vagrant up gets past the "Preparing network interfaces based on cconfiguration" section), but both solutions lead into this error when the VM tries to boot. I've tried setting up the same VMs on an Ubuntu host and they work fine there, so it is an issue in Windows 10.

[jaminday]

FWIW the test build VirtualBox-5.0.1-101902-Win.exe only worked for me when I set Virtualbox to run in Windows 8 compatibility mode.

Here are the steps I followed:

1. Uninstalled any leftover VBox Host-Only Network adapters through Device Manager
2. Set config.vm.network "private_network", ip: "192.168.50.4", name: "VirtualBox Host-Only Ethernet Adapter" in my Vagrantfile
3. Enabled Win8 compatibility mode for VirtualBox
4. Created a new Host-Only Network via VBox GUI, set the IP address manually to 192.168.50.4 (matching my private network config in Vagrantfile). Basically adapt settings in @erdemece's screenshots above for your IP.
   Note: Win8 compatibility mode seems necessary for the new adapter to 'stick'. Otherwise VirtualBox forgets it as soon as the window is closed (for me at least).
5. vagrant up --provision

Note that the first time I ran vagrant up I received the following error
The specified host network could not be found: 'VirtualBox Host-Only Ethernet Adapter.' If the name specification is removed, Vagrant will create a new host only network for you. Alternatively, please create the specified network manually.

On a whim I tried disabling TCP/IPv6 for the VirtualBox Host-Only Ethernet Adapter and then it worked, but I've since re-enabled IPv6 and multiple vagrant halt, vagrant up [--provision] attempts have been fine. So not sure if it was necessary.

[festum]

@jaminday After the steps I meet crash when open vbox gui every times. I destroy VM and tried again got

The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

Boot manually got:

Unable to load R3 module C:\Program Files\Oracle\VirtualBox/VBoxDD.DLL (VBoxDD):     GetLastError=1790 (VERR_UNRESOLVED_ERROR).

E_FAIL (0x80004005)
ConsoleWrap
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

[erdemece]

test build fixed for me

https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-101902-Win.exe

[jaminday]

@Festum have you tried reinstalling Virtualbox?

[antonsivogrivov]

@erdemece, VB shows an error renaming the environment, because this name is already exists.

[BinaryKitten]

Hi Everyone,

If you're having issues with VirtualBox and you've not changed Vagrant - surely the best place to report the problems is to VirtualBox.
Stating here crashes in VirtualBox won't get them resolved as @mitchellh can't fix them. (unless i'm missing something)

If we want VirtualBox to get this fixed, lets report our experiences of the "fix" etc to them

[ZackWard]

Confirming the work-around posted by @venimus worked for me. I changed the private network config in the Vagrantfile to read

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

and then made sure that in the VirtualBox GUI, that adapter was set to IP 192.168.10.9. This is working for me. It seems that the major issue was Vagrant attempting to rename a network connection, and failing out. Thank you for the suggestion @venimus

Windows 10 Home
VirtualBox 5.0.1
Vagrant 1.7.4

[venimus]

If you are tracking Vagrantfile you could temporary change it, then use vagrant suspend instead of halt (or other way to stop it). Than you can discard the changes.

[antonybudianto]

Mine doesn't work too

Windows 10 Pro x86 (32bit)
Virtual Box 5.0.1 (test build)
Vagrant 1.7.4

still stucks at the very same Festum's error message
maybe the x86 is the problem since many x64 users succeed.

[saraf]

5.0.1 r101957 and Vagrant 1.7.4 still does not fix the problem for me. in my Vagrantfile I have config.vm.network "private_network", ip: "192.168.56.102" (ubuntu trusty box guest, windows 10 host) everytime I try to do a vagrant up, an error message pops up saying "Cannot rename connection. A connection with the name you specified already exists. Please specify a different name." After clicking OK it creates a new Ethernet adapter with an incremented #number and the box does not boot up - What should be done?

[saraf]

The workaround by venimus works for preventing the creation of spurious Ethernet adapters. (The trick is that specifying name will skip creating of virtual adapters along with this error.) Is this specification required behavior henceforth?

[venimus]

There is a check for provided option.name that skips creation of adapters.

[andyburton]

Finally working here with

Windows 10 Pro x64
VirtualBox 5.0.1r101902
Vagrant 1.7.4

[ZackWard]

I found a solution that doesn't involve any file modifications here:

https://laracasts.com/discuss/channels/general-discussion/windows-10-vagrant-virtualbox-homestead/?page=5

Credit to pdcmoreira of the Laracast community for this solution.

Go to the C:\Program Files\Oracle\VirtualBox folder, right click on VirtualBox.exe, go to compatibility tab, check the "Run in compatibility mode" checkbox and choose Windows 7. Click OK to close the window.
Repeat for VBoxManage.exe and VBoxHeadless.exe

I set to Windows 8 compatibility, and was able to get my VM up and running without any file modifications. No spurious adapters were created.

[kshamsuddin]

Hi,
Finally it's working partially but when I type the ip for example: 55.55.55.5 to chrome I got the following error:

This web page is not available
ERR_CONNECTION_REFUSED

I can ping that private ip 55.55.55.5 from terminal with 0% loss. I edited the host file as below:
55.55.55.5 example.dev

And tried to use that in chrome + firefox "example.dev" but no luck. Can't browse that from any browser.

Thanks for any advice.

[riebling]

The latest versions of VirtualBox and Vagrant, combined, seem to still not fix the problem for me.
Changing the compatibility mode of the VirtualBox executables to Windows 7 did not help, either.
I'm jealous of those here who got it to work!

EDIT: If I use the specific VirtualBox version mentioned above (VirtualBox-5.0.1-101902-Win.exe), it got past the creating host-only network interface error, but still failed to boot the box the whole way. So it appears that the bleeding edge version of VirtualBox (VirtualBox 5.0.1r101957) is actually a regression to the original Host-only Network Interface error

EDIT: the fail to boot was because I forgot to install VirtualBox Extensions (why don't they just include them!!) ... ANYWAY after learning how to delete spurious network adapters (not from Network Connections, even though there is a Delete capability there, it simply doesn't let you no matter what, so instead you Uninstall from Device Manager -> Network Adapters) - after deleting all the spurious VirtualBox host only network adapters, managed to get "the error" again, even with supposedly-good version 5.0.1r101902 of Virtualbox)

Windows 10 Home (64 bit)
VirtualBox 5.0.1r101957 and sometimes 5.0.1r101902
Vagrant 1.7.4

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

[bart]

Same here. I did try a bunch of things like different virtualbox versions, the fix, compatibility, installing as admin - everytime different errors. I'm currently hanging on a problem where I can't install virtualbox (VirtualBox-5.0.1-101902-Win.exe) anymore getting "Setup Wizard ended prematurely". I disabled the bridge networking during setup.

I'm also using Kaspkersky. Maybe another possible root for errors?

[ghost]

Works for me with:

Windows 10 Pro x64
VirtualBox 5.0.1-102010
Vagrant 1.7.4

[riebling]

Confirming VB 5.0.1-102010 for the win

[jag1989]

Windows 10 Home
VirtualBox 5.0.1-102010
Vagrant 1.7.4

Confirmed as working

[antonybudianto]

Virtualbox 5.0.2 is available and it works well without modifying any files and hack the port, and it works on Windows 10 Pro x86

Note:
if it's still showing "invalid state", then revert all modified files and remove all host-only adapters on Virtualbox GUI preferences. And do homestead/vagrant halt and up.

[antonsivogrivov]

Still not working :(

[alexsouza]

Hey guys, this works for me : http://lezgro.com/blog/a-very-simple-fix-for-the-windows-10-and-vagrant-error/

[ljjackson]

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

[GuruVoodoo]

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"

[lightinthedark]

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.

[mitchellh]

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!

[engine-go]

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.

[Costanza]

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.

[mattKendon]

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)

[pgcd]

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.

[dany-fu]

I upgraded VirtualBox and this is no longer an issue

[seperman]

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

[shenqihui]

The key of the solution mention in https://www.virtualbox.org/ticket/14040 is to keep the fix program running when running vagrant up or vagrant reload.

Try it.

[LuisRamirezColin]

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.

[wallraks]

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

[jfitzsimmons2]

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. ¯_(ツ)_/¯

[manjunath-coachthem]

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

[panchalkalpesh]

Following solution worked for me:

1. Goto C:\Program Files\Oracle\VirtualBox\drivers\network\
2. There are two folders, go inside both of them and right click on .inf and click Install
3. Head over to Control Panel\Network and Internet\Network 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
vagrant up

Hope this helps you!
Kalpesh Panchal

[WangNingning1994]

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

[IshtiaqAhsan]

@panchalkalpesh this worked like a Magic!!! Thanks a Zillion 🥇

[ldmuniz]

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

[RafaelMLMacedo]

@panchalkalpesh solution worked great! Thanks

[naorzr]

@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.

[rukundofiston]

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

[Rodri9o]

@panchalkalpesh - your solution worked. Thank you very much!

[wcadena]

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

[hashibot[bot]]

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.