Failed to open/create the internal network Vagrant on Windows10

vagrant virtualbox windows-10

236,516

Solution 1

I found a solution

Open Windows Network Connections
Right click on VirtualBox Host only adapter that created
Choose properties
Check "VirtualBox NDIS6 Bridged Networking driver"
disable and Enable the adapter

Solution 2

There is a known issue with the new NDIS6 driver, you can install it to use the NDIS5 driver

Try reinstalling it with a parameter (Run as administrator)

> VirtualBox-5.0.11-104101-Win.exe -msiparams NETWORKTYPE=NDIS5

This worked for me.

Update: Newer versions made it easier to pick the NDIS driver from within the installation wizard - just pick NDIS5 when asked.

ref: https://www.virtualbox.org/manual/ch02.html#install-win-performing

Solution 3

Open Network and Sharing Center and go to the Change adapter settings in the sidebar.
Right-click on the host-only adapter in the list of adapters and then Configure button -> Driver tab -> Update driver button.
Select Browse my computer ... and in the next dialog select Let me pick .... You should see the list with just host-only driver in it.
Select it and click next. After the driver is updated, please try using host-only network in a VM again.

Solution 4

I tried the above options, but in vain. Eventually I uninstalled docker-toolbox (1.11.x) and virtualbox(5.16.x) and CHECKED the following option in the docker-toolbox installer GUI (by default the NDIS5 option was unchecked)

Also the virtualadapter in network connections had "Bridge Networking Driver" option UNCHECKED and that worked fine for me

Solution 5

The same error occurred when I updated Windows. Tried everything. Nothing worked.

Finally, went to Device Manager-> Network Adapters Disabled and enabled the Virtualbox Host only Adapter

And it worked!

View more solutions

236,516

callmemath

Updated on July 08, 2022

Comments

callmemath almost 2 years

I upgraded my Windows 10 to the last update yesterday and now, when I launch vagrant up command, I get this error :

==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
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.

When I try with GUI I have this error :

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).
Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

I have re-installed VirtualBox 5.0.10 and the extension pack, reconfigured Host-Only Ethernet Adapter, but always the same error...

Any ideas?

pravingaikwad07 over 3 years

This helped me : virtualbox.org/ticket/14832#comment:20

StalkAlex over 8 years

In my case it was just disabled.
Andreas Reiff over 8 years

I cannot believe it - was searching for this for hours. Was disabled for me, too. (Now, Genymotion as well as Xamarin Android Player can correctly create the interface. Somehow this broke during an update, and reinstalling VBox did not fix it.) Many thanks!
Rav over 8 years

I've tried everything in this post and the only thing that worked for me was to downgrade VirtualBox to 4.2.22. Even 4.2.36 didn't work. S**t, lost a lot of time to this issue.
Joel Skrepnek over 8 years

After following these steps, I received the error "Nonexistant host networking interface, name 'VirtualBox NDIS 6.0 Miniport Driver'. I needed to then manually remove the associated Network adapters.
venimus over 8 years

I bet you get a gold badge, for having not accepted answer :) However, you might not use Bridged adapter at all and this solution is not so universal. +1 for not needing reinstall.
Thomas Hagström over 8 years

This did the trick for me too. Was having issues with Xamarin Android Player, which installs VM Ware for you
Yevgeniy Afanasyev about 8 years

It did not help me, moreover, it broke my chrome. To get Chrome working I updated the VirtualBox and rebooted computer. Chrome is working now again as it was, Edge - is not working.
Yevgeniy Afanasyev about 8 years

I installed update to 5.0.16 instead of 5.0.6 - it did not help, but it did not do worse either.
jjz about 8 years

This is the real solution. I burned 4 hours of my time for this issue. I can eat my snacks now. Thank you!
mastazi about 8 years

It is amazing that 5 months later this issue still keeps coming back after every Virtualbox update. You would think that by now they worked out a solution...
GenEric35 about 8 years

Works, Thanks a lot, I too have encountered this problem when trying to run Docker tools. Maybe it should be tagged as docker as well?
Ashoka K almost 8 years

Thanks much :) I struggled for last 2 days to bring it back. I Have network adapter NDIS6. This was not at all working. So reinstalled VBox manually with option NDIS5 and it started working. My question is, even though my network device shown as NDIS6, I use NDIS5 during install. Does it cause any problems ?
spronkey almost 8 years

I had to do a couple of things before I was able to select this - first, manually install the VBox network driver .infs (browse to <vbox install dir>\Drivers\network, and install all the infs in the subfolders), and then second, I had to click the 'Install' button in the above dialog to manually add the VirtualBox (...) Networking Driver service (this is Windows 10).
Zhaidarbek almost 8 years

I had the same issue when trying to get started with fabric8. Only this solution helped me with VirtualBox-5.0.22-108108-Win on Windows 8.1.
paulus almost 8 years

helped me to solve the issue with 5.0.24r108355 on Win8
gadamiak almost 8 years

Worked for me with VirtualBox 5.1.2 on Windows 7. Thanks a lot, dude!
code4kix over 7 years

Thank you... I am on VirtualBox 5.1.6 on Windows 7. This works!
McGlothlin over 7 years

This worked in my case. I tried disabling/reenabling the NDIS6 driver as suggested above, but it didn't help. What I ended up doing was uninstall VBox, grab Docker Toolbox 1.11.2 from GitHub (since the current installer 1.12.1 removes the checkbox options from the setup), and reinstall VBox with the NDIS5 option checked. Thanks!
ymajoros over 7 years

Same problem here, installing Virtualbox 5.1.6 solved it for me.
Gajotres over 7 years

I did just this but it didn't help me; until I found out that I also need to delete previously created network adapters. Also, don't forget to uninstall both Docker Toolbox and VirtualBox. Removing Docker Toolbox will not also remove VirtualBox. +1
Kosmas over 7 years

Strange, when I installed 5.1.14, it is already disabled, and enabling it is the solutions.
Ashutosh about 7 years

I tried using Kitematic etc. none of these worked. Then I tried this .Thanks a ton!!
Ehsan Waris about 7 years

In my case it was Avast .. and I uninstalled it from that properties window.. now its fine and working
Iman Marashi about 7 years

Don't forget Run as administrator CMD
Winnemucca about 7 years

@ymajoros I am having this problem with 5.1.18. Is there a way to get down to your version?
Jason Joslin over 6 years

The only thing that worked for me was reinstall virtual box
Calcutta over 6 years

I simply updated VirtualBox to (current) version Version 5.2.4 r119785 and the problem went away ...
Wes almost 6 years

I don't know how you figured this out, but thanks! This solved my problem. 5.2.14
sashiksu about 5 years

In my laptop there is no built in Ethernet port. So after installing VM it won't adding host only adapter to adapter list. Then I tried it with my other laptop which having Ethernet port. It worked ! Because of this I couldn't run genemotion. If someone find solution for this let me know.
Arno van Oordt almost 5 years

Had this issue after a Windows 10 update. A simple reboot did the trick form me as well :)
Pavan_Obj over 4 years

Worked for me, just in case if others are in the same boat as I am. I had to perform the above steps in Hyper-V virtual Ethernet Adapter, and other adapters like VirualBox host-only network#3 and Ethernet 5 - VirtualBox Host-Only Ethernet Adapter(names might differ in your machine)... hope it helps.
Albert Iordache over 4 years

This also worked on VirtualBox 6.0.10 after upgrading Windows from 1803 to 1809
Darshana over 4 years

This is helpful. Worked with windows 10 and Oracle VM virtualbox 6.0.10 perfectly
Bassdrop Cumberwubwubwub over 4 years

This worked for me on VirtualBox 6.0.14 using minikube v1.3.1
hguser over 4 years

This works for me when I update my vbox from 5.x to 6.1. Thanks.
HarleyDavidson over 4 years

Worked for me (Windows 10 with VirtualBox 6.1.0 r135406).
AlexDumas over 4 years

Using Virtual Box 6.0.10 on Windows 10.0.19041.1 with the most recent updates, ran into this issue. After trying the all the other above options, this is the one which actually worked. Thank you !
Jie Zhang about 4 years

Thanks! This works for me, but don't understand why.
amrit almost 4 years

Apparently this also happens when you install virtualbox but don't restart and try to open a VM.
styshoo almost 4 years

It works, but it seems that we also have to disable and reenable the Host-Only adapter.
byzz almost 4 years

Thank you very much. Thanks to this solution, I was able to leave the office. Thank you again.
BadHorsie over 3 years

My VirtualBox adapters were both enabled already, but disabling and re-enabling them worked.
Lemmings19 over 3 years

I went into these settings via File>Host Network Manager, then I removed and recreated the problematic network. I just let it create with default settings.
Danniel Little over 3 years

You saved me a lot time too. Thanks
Serge S. over 3 years

Thank you for pointing to an antivirus! In my case it was Kaspersky Secure Connection tool installed (but disabled). After I uninstalled it, the problem was solved.
user7986267 over 3 years

Oh man@#$ I spent 3 hrs doing absalutely nothing because it was all set up correctly, just had to reboot. Thanks, you should would for customer service IT department XD
GreenLake4964 about 3 years

This worked for me after upgrade to Windows10 (19042.631) , with VirtualBox 6.1.6. Wondering how you figured this trick?
jjsantoso about 3 years

Thank you! Last image helped a lot. I was looking the adaptor in Windows networks settings but adapter#2 was hidden, so I cannot restart it. I found it in device manager, unable-enable it and worked!
Soumya Kanti almost 3 years

I faced the same problem after upgrading to Windows 10 21H2 and this helped me to overcome the problem. Thanks a lot!
y_159 over 2 years

This worked, glad i found this solution in first go.
Jader about 2 years

After I upgraded my win 10 to win 11 I got this error when I ran vagrant up. Your solution worked fine. tks
Alberto about 2 years

I have tried above solutions and this was the only that worked for me. Thanks!
Jay Elston almost 2 years

I had this problems after a windows update. For me, disabling, the enabling the adapter was all that I needed.