What to do with VERR_INTNET_FLT_IF_NOT_FOUND error in VirtualBox when setting up a network bridge?

Question

virtual box

The network type does not work for the "Network Bridge" virtual machine.
When starting the virtual machine, it crashes with the following error:

Не удалось открыть сессию для виртуальной машины FreeNas.

Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller #2' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Код ошибки: E_FAIL (0x80004005)
Компонент: Console
Интерфейс: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

How to deal with it?)

Answer 1

In the network connection properties, uncheck (OK) and check (OK) the checkbox for VirtualBox NDIS6 Bridged Networking Driver. You don't need to uninstall/reload/install anything.

Answer 2

In a piggy bank. The advice from Google helped me
then something like this
Go to Device Manager --> Network adapters --> Uninstall network adapter (on which setting Bridged adapter is not working) --> Click on Scan for harware changes --> Restart PC --> after restart go to Device Manager --> Network adapters --> uninstalled network adapter will be marked with "!", again uninstall this network adapter --> Click on Scan for harware changes - now network adapter will be installed and restart will not be required

Answer 3

Necropost but can be useful to someone.
When installing pure Genymotion without VirtualBox, this infection wipes out all virtual host adapters every time it starts. So unchecking/checking the network adapters does not help. The output is primitive - download Genymotion from Virtualbox and everything works out of the box.
Believe me, I killed a lot of time to get everything working after I updated virtualbox.

Answer 4

I had a problem when updating the network card drivers on the host. Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.20) network card. The drivers were new for 2013. I rolled back to the drivers for 2010. And everything worked.
How I rolled back: I deleted the device in the device manager (ticked the delete drivers checkbox), then I clicked on update the configuration, an unidentified device appeared, update the drivers, indicated the path to the folder where the drivers were old for 2010.

Answer 5

This helped ram.kossboss.com/virtualbox-host-only-adapter-erro...

Answer 6

I had 2 network on (Win764RuSp1), on one it started normally, on the second it didn't.
deleting with firewood / without network cards and unchecking / checking the boxes did not help.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Network\{4d36e974-e325-11ce-bfc1-08002be10318} somewhere here I found the remains of Casper, after removing the entire GUID everything worked without rebooting