Failed to open/create the internal network 'VirtualBox Host-Only Ethernet Adapter'
Matthew Barrera 
Newbie here. I'm trying to use bridged network on VM Virtualbox using VirtualBox Host-Only Ethernet Adapter. When I start the virtual program, it outputs the following error message. '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).'
In order to debug the error, I've ticked off and re-ticked VirtualBox NDIS6 Bridged Networking Driver box on network adapter setting from the control panel. I've also removed the VM Virtual box and reinstalled the most recent one (6.0.4). Finally, I've added the VirtualBox Host-Only Ethernet Adapter on Host network manager setting on VM Virtual box. But nothing really fixed the error, and I'm stuck for hours now. Can anyone help me out from this endless pit?
42 Answers
Host-Only Ethernet not working seems to be a common failure with recent Windows 10 updates.
Toggling VirtualBox NDIS6 Bridged Networking Driver off then back on in the adapter's properties is a good start, but it seems that we also have to disable and reenable the entire Host-Only adapter.
That worked for me with VirtualBox 6.0.10 on Windows 10 Update 1809.
Ref:
22021 Update.
- Press Windows key
- Type "View Network connections"
- Open the link
- Find the adapter
- Right-click adapter->Properties.
- Disable the NDIS6 virtualbox by unticking.
- Apply & Close the dialog.
- Right-click adapter->disable.
- Right-click adapter->Properties.
- Enable the NDIS6 virtualbox by ticking.
- Apply & Close the dialog.
- Right-click adapter->enable.
After this Docker toolbox works again. Sadly, this is also required for every vagrant box started this process needs to be repeated...
Hard to believe this bug was first reported back in 2015
1
