windows 10.0.10586: Failed to open the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter'

[jamesr]

I'm trying to solve a problem that I haven't found a proper solution for on the internet. Problem is I'm trying to install laravel homestead virtual machine in virtual box in windows 10.0.10586. I currently use virtual box 5.0.10.

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

What I have tried to according to searches on google:

Enable Virtual technology and Intel VT-d feature in BIOS
Updating VirtualBox Host-Only Ethernet Adapter
Installing virtual box, while running in Administrator mode
Installing homestead in commando prompt, while running in Administrator mode
Added Virtualbox as an exception in AVG anti virus FREE 2015.
activate/deactivate Host-Only Ethernet Adapter

[jamesr]

Enabling virtualization

[jamesr]

installing-homestead

[jamesr]

virtual-box-error

[jamesr]

updating-drivers

[jamesr]

homestad-cant-start-up

[jamesr]

Vbox hardening log on homestead

[jamesr]

Vbox.log

[jamesr]

vbox log in txt format

[jamesr]

problem description

[Frank Mehnert]

VERR_INTNET_FLT_IF_NOT_FOUND often means that the installation of the network filter driver was not successful. This is most likely a problem when you install VirtualBox on your host. You might want to enable the logging of the installer, see here.

[jamesr]

Replying to frank:

VERR_INTNET_FLT_IF_NOT_FOUND often means that the installation of the network filter driver was not successful. This is most likely a problem when you install VirtualBox on your host. You might want to enable the logging of the installer, see here.

Hi Thank you for answering. I now attached VboxInstallLog.txt to this ticket, which should be the log from when I installed virtualbox.

[jamesr]

It's creating 2 virtualbox host-only network adapters. Is that normal?

VirtualBox Host-Only Network

VirtualBox Host-Only Network #2

[Aleksey Ilyushin]

Please follow these steps:

1. Uninstall existing version of VirtualBox (it is needed to remove all existing host-only adapters);
2. Download and install ​DebugView;
3. Download and install build 104375; no additional driver tweaking please, use defaults;
4. Provide the output of VBoxManage list hostonlyifs;
5. Start DebugView, make sure 'Capture Kernel' and 'Enable Verbose Kernel Output' are checked, you should see some messages being captured;
6. Start VM that fails with VERR_INTNET_FLT_IF_NOT_FOUND, reproduce the issue;
7. Stop capture, find captured lines that start with 'vboxNetFltOsInitInstance:' and copy them here.

[jamesr]

I followed the instructions and install build 104375.

1. I tried running the command VBoxManage list hostonlyifs. Unfortunately, it returned 0 result. please see hostonlyifs.jpg.
   

2. I started DebugView and made sure Capture Kernel and Enable Verbose Kernel Output was checked. please see whatiscaptured.jpg
   

3. From commando prompt I run "homestead up", which tried to open connection to virtual machine homestead. This made an error - "VirtualBox Host-only Ether Adapter 3 could not be found". To be honest, I tried this some times and it created a new host only adapter every time. Please see plentyofhost-only-networks
   

4. Then I tried to manually and start homestead virtual machine from Virtual box GUI, and that worked. Eventhough that works it still doesn't solve problem with host-only adapter.
   

5. I'm not sure I used DebugView properly, but I couldn't find vboxNetFltOsInitInstance. Please see

couldnotfindvboxNetFltOSInitInstance.jpg

[jamesr]

Could not find vboxNetFltOSInitInstance

[jamesr]

hostonlyifs

[jamesr]

what is captured

[jamesr]

plenty of host only network created

[jamesr]

anothererror

[jamesr]

Replying to jamesr:

I followed the instructions and install build 104375.

1. I tried running the command VBoxManage list hostonlyifs. Unfortunately, it returned 0 result. please see hostonlyifs.jpg.
   

2. I started DebugView and made sure Capture Kernel and Enable Verbose Kernel Output was checked. please see whatiscaptured.jpg
   

3. From commando prompt I run "homestead up", which tried to open connection to virtual machine homestead. This made an error - "VirtualBox Host-only Ether Adapter 3 could not be found". To be honest, I tried this several times and it created a new host only adapter every time. Please see plentyofhost-only-networks
   

4. Then I tried to manually and start homestead virtual machine from Virtual box GUI, and that worked. Eventhough that works it still doesn't solve problem with host-only adapter.
   

5. I'm not sure I used DebugView properly, but I couldn't find vboxNetFltOsInitInstance. Please see

couldnotfindvboxNetFltOSInitInstance.jpg

[jamesr]

Replying to jamesr:

Replying to jamesr:

I followed the instructions and install build 104375.

1. I tried running the command VBoxManage list hostonlyifs. Unfortunately, it returned 0 result. please see hostonlyifs.jpg.
   

2. I started DebugView and made sure Capture Kernel and Enable Verbose Kernel Output was checked. please see whatiscaptured.jpg
   

3. From commando prompt I run "homestead up", which tried to open connection to virtual machine homestead. This made an error - "VirtualBox Host-only Ether Adapter 3 could not be found". To be honest, I tried this several times and it created a new host only adapter every time. Please see plentyofhost-only-networks.jpg
   

4. Then I tried to manually start homestead virtual machine from Virtual box GUI, and that actually worked. Eventhough that works it still doesn't solve problem with host-only adapter.
   

5. I'm not sure I used DebugView properly, but I couldn't find vboxNetFltOsInitInstance. Please see

couldnotfindvboxNetFltOSInitInstance.jpg

[jamesr]

Replying to jamesr:

Replying to jamesr:

Replying to jamesr:

I followed the instructions and install build 104375.

1. I tried running the command VBoxManage list hostonlyifs. Unfortunately, it returned 0 result. please see hostonlyifs.jpg.
   

2. I started DebugView and made sure Capture Kernel and Enable Verbose Kernel Output was checked. please see whatiscaptured.jpg
   

3. From commando prompt I run "homestead up", which tried to open connection to virtual machine homestead. This made an error - "VirtualBox Host-only Ether Adapter 3 could not be found". To be honest, I tried this several times and it created a new host only adapter every time. Please see plentyofhost-only-networks.jpg
   

4. Then I tried to manually start homestead virtual machine from Virtual box GUI, and that actually worked. Eventhough that works it still doesn't solve problem with host-only adapter.
   

5. I'm not sure I used DebugView properly, but I couldn't find vboxNetFltOsInitInstance. Please see couldnotfindvboxNetFltOSInitInstance.jpg

[Aleksey Ilyushin]

Could you check the properties of host-only connections if they have "VirtualBox NDIS6 Bridged Networking Driver" enabled? Your problem definitely looks like bridging filter is not bound to host-only adapters.

[jamesr]

Replying to aleksey:

Could you check the properties of host-only connections if they have "VirtualBox NDIS6 Bridged Networking Driver" enabled? Your problem definitely looks like bridging filter is not bound to host-only adapters.

Of course! Seems like VirtualBox NDIS6 Bridged Networking Driver hasn't been enabled! Should I enable? - see NDIS6notenabled.jpg

[jamesr]

NDIS 6 not enabled

[Valery Ushakov]

#14832

[jamesr]

Replying to vushakov:

#14832

Why are you setting this as closed? this hasn't been solved yet. Why are you refering to this as a "duplicate" ?

your link solution doesn't solve my problem. I tried enabling it, but it doesnt solve the problem on my machine.

[jamesr]

Replying to jamesr:

I'm trying to solve a problem that I haven't found a proper solution for on the internet. Problem is I'm trying to install laravel homestead virtual machine in virtual box in windows 10.0.10586. I currently use virtual box 5.0.10.

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

What I have tried to according to searches on google:

Enable Virtual technology and Intel VT-d feature in BIOS
Updating VirtualBox Host-Only Ethernet Adapter
Installing virtual box, while running in Administrator mode
Installing homestead in commando prompt, while running in Administrator mode
Added Virtualbox as an exception in AVG anti virus FREE 2015.
activate/deactivate Host-Only Ethernet Adapter

NB! Vushakov closed this ticket without any explation. Problem hasn't been solved yet. I got no >explanation why its a duplicate.

[Valery Ushakov]

Replying to jamesr:

Replying to vushakov:

#14832

Why are you setting this as closed? this hasn't been solved yet. Why are you refering to this as a "duplicate"?

Because it is a duplicate?

your link solution doesn't solve my problem. I tried enabling it, but it doesn't solve the problem on my machine.

Please, use the bug #14832 for further discussion.

[jamesr]

Replying to vushakov:

Replying to jamesr:

Replying to vushakov:

#14832

Why are you setting this as closed? this hasn't been solved yet. Why are you refering to this as a "duplicate"?

Because it is a duplicate?

your link solution doesn't solve my problem. I tried enabling it, but it doesn't solve the problem on my machine.

Please, use the bug #14832 for further discussion.

Well, I disagree. bug 14832 solution didn't solve my problem at all. I don't like people closing tickets, when they can't even elaborate their choice of closing something not solved.

[Aleksey Ilyushin]

So, did you try to enable 'VirtualBox NDIS6 Bridged Networking Driver' for all host-only adapters? Note that it is essential to enable them for each adapter, as each adapter has individual bindings.

[Aleksey Ilyushin]

Please try build 104592. It should solve the issue.