virtualbox.org

When I see this error I only have 1 solution: uninstalling Virtual Box and installing it back, which is a little pain.

Have anyone found a different solution to this error VERR_INTNET_FLT_IF_NOT_FOUND?

Google "VERR_INTNET_FLT_IF_NOT_FOUND site:forums.virtualbox.org" to see what has been done about this in the past.

The next time this error appears, it will be in a Virtualbox error window with a Copy button. Copy & paste the error message verbatim to the forum post. Don't change anything in the error message, it's all essential.

We will also need to see how the guest causing this issue is networked. Please zip and post the guest's .vbox file, found in the guest's folder, using the forum's Upload Attachment tab.

This is the most classic error I've found ever by using VBox in the last years. Never found a mechanism to solve it, other than reinstalling:

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).
Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

My suspicion is the answer given here: "Certainly the host OS seems to have renamed the ethernet adapter for some reason."
Which doesn't offer a comprehensive solution

By the way, the solution is always the same:
viewtopic.php?f=6&t=94277#p455065
viewtopic.php?f=6&t=85910#p409261

Still find a little obnoxious that this is the only solution

According to socratis

I really can't tell, but that #2 and #n for subsequent installations is getting more and more prominent in the Windows world, with no quick and easy solution unfortunately...

viewtopic.php?f=6&t=85910#p409263

So maybe this is the only solution due to Windows hindrances

Thanks for the error info. Looks like you're attempting to connect with Host-Only, and Virtualbox can't find the Host-Only adapter it thinks is there. There's a couple reasons for this:

When Windows goes through a particular sort of update it can re-attach Virtualbox's Host-Only adapter. Since there was already a Host-Only adapter, Windows increments a number on the Host-Only adapter's name, as in:
VirtualBox Host-Only Network >
VirtualBox Host-Only Network #2 >
VirtualBox Host-Only Network #3 etc.

When the name changes Virtualbox can't find it. In the guest Settings, you'd change the "Name:" dropdown for the Host-Only network to the existing Host-Only # found in Control Panel > Network & Sharing Center > Change Adapter settings.

Another possibility is that the "Virtualbox NDIS6 Bridged Networking Driver" binding that is used on the Host-Only virtual adapter is unchecked:

If it's unchecked, check it, then try again. I don't know if a disconnect/reconnect of the Host-Only "cable" to the guest, or a disable/enable cycle on the host's Host-Only adapter may be necessary. Hopefully not a host log-off, reboot, etc.

Nothing of the two options solve the issue:

Check this

A) NDIS
B) Network options:

Also, please zip and post your guest's .vbox file, in the guest folder, using the forum's Upload Attachment tab.

I think I have found the root of the issue

In that guest file I see this

<Network>
  <Adapter slot="0" enabled="true" MACAddress="080027BE5AFB" cable="true" type="virtio">
    <DisabledModes>
      <InternalNetwork name="intnet"/>
      <HostOnlyInterface name="VirtualBox Host-Only Ethernet Adapter"/>
      <NATNetwork name="NatNetwork"/>
    </DisabledModes>
    <BridgedInterface name="VirtualBox Host-Only Ethernet Adapter"/>
  </Adapter>
  <Adapter slot="1" MACAddress="080027ECE0F7" cable="true" type="virtio">
    <DisabledModes>
      <BridgedInterface name="Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller"/>
      <InternalNetwork name="intnet"/>
      <NATNetwork name="NatNetwork"/>
    </DisabledModes>
  </Adapter>
  <Adapter slot="2" cable="true" type="Am79C973"/>
  <Adapter slot="3" cable="true" type="Am79C973"/>
  <Adapter slot="4" cable="true" type="Am79C973"/>
  <Adapter slot="5" cable="true" type="Am79C973"/>
  <Adapter slot="6" cable="true" type="Am79C973"/>
  <Adapter slot="7" cable="true" type="Am79C973"/>
</Network>

For some reason, the problem doesn't seem to be in the Host-Only but probably in the Bridged Adapter that has 6 slots for some strange reason

By the way adapters, 2, 3 and 4 So is strange that the vbox file saves all that info in slots 1 to 7

You have a total of 8 possible network adapters for the "chipset" of the guest. They start counting at Adapter #1 in the guest settings, which refers to 'slot="0" ' in the .vbox file. You had the second adapter running once but not now, the last 6 aren't used yet. That's OK.

The second adapter 'slot="1" ' is not connected to anything, notice nothing between the closing </DisabledModes> tag and the closing </Adapter> tag.

Your first adapter 'slot="0" ' is set to Bridged, and is pointing at the Host-Only adapter. Your screenshot above showes "adaptador puente", which Google Translate says means "bridge adapter". The "Name:" or "Nombre:" dropdown is showing both physical and virtual adapters. Here is your problem.

On my host, when I set "Attached to:" or "Conectado a:" to "Bridged Adapter", the "Name:" dropdown only shows physical network devices. When I set "Attached to:" to "Host-Only Adapter", the "Name:" dropdown only shows Host-Only adapters. Your Virtualbox, or the host OS, is messed up and is crossing the boundaries between physical and virtual on your host network adapters.

You would only Bridge to real devices, and would Host-Only only to Host-Only devices. You could try setting "Conectado a:" to Host-Only, then choose the correct Host-Only adapter.

Otherwise I'd suggest:
1. Get rid of the Host-Only adapters you have (see main Virtualbox window, File Menu, Host Network Manager)
2. uninstall Virtualbox one more time
3. delete from the host's "Network Connections" any Host-Only adapters that remain over from the uninstall
4. Reinstall Virtualbox using right-click Run As Administrator
5. Make a new Host-Only Network.
6. Attach your guest "Conectado a:" to Host-Only, then choose the correct Host-Only adapter.

Here is the "host-only" connected to

2. uninstall Virtualbox one more time

This is what I commented in the first post... this is why I called this error the Error of death, because it forces reinstall which is obnoxious for any kind of software

SirLouen wrote:This is what I commented in the first post...

Noted. Thus the "one more time".
Life is full of troubles.

By the way, I've found a solution from pure "luck".

The trick was performed essentially disabling and re-enabling the Windows interface.

PS: Worked twice! Can't believe it

So here is the solution (in case I have to check this in 6 months)

1. Start the process (from any of the software that likes to play with Host-Only interfaces like Flywheel or Genymotion)
2. It will create a new interface and end with the VERR_INTNET_FLT_IF_NOT_FOUND error
3. Stop the process
4. Go to Windows Network Interface list
5. Disable the Host-Only interface
6. Reenable the Host-Only interface
7. Re-run the process

And voila! it works flawlessly

In case it fails, just by removing all Host-Only interfaces in the Vbox Host-Only interface list (Ctrl+H) and in the Windows Network interface list
And then forcing recreation with each 3rd-party process.

Things to check
A) The Host-Only adapter in the VBox VM setting exists also in the Windows Interface List with the same device name (not name)
B) Check in the VBox Host-Only interface list that the interface has DHCP is ON (not sure if this is mandatory but currently all are on and working)

Good, glad it was that easy!

SirLouen wrote:So here is the solution (in case I have to check this in 6 months)

[...]

3. Stop the process
4. Go to Windows Network Interface list
5. Disable the Host-Only interface
6. Reenable the Host-Only interface
7. Re-run the process

I would like to mention that for Windows 10 I couldn't find a "Network Interface list".
I think it's the same as Device Manager > Network adapters. And it worked!

Thank you very much @SirLouen for sharing this.

Woaw....
FANTASTIC !!! This saved my day or rather my entire week !!

I just made the same: disable then re-enable the Virtualbox host-only interface with the Windows 10 GUI and it fixed everything.
(in my case I have two Virtualbox sessions that need to communicate with each other through the local host-only network)

Thanks a lot for posting this simplistic and totally efficient trick !!