virtualbox.org

You could also try to manually add the filter. Go into the properties of the connection, where you have IPv4 & IPv6 config items, and click on Install or Add. Then you could add the Bridge Driver

There is very weird behaviour happening with the filter. First of all, it was already there. So I tried to uninstall and reinstall it. OK. Well, it is installed (so it seems, it's in the list, at least) but it gives major problems with the network card: while Windows reports a stable connection to "Network" in the windows bar, and the the "Internet" in the Centre is there and on, if you go in the menu for seeing network cards, the proper network card is there but is "disabled". You can try to enable it but it won't work, or, at least, appear as enabled. The card in fact is working, internet is ok. Giving another look at the network and sharing center shows the connection to the Internet but the part "Connections:" is then empty Device manager shows the card there on and working. If I try to disable it from there and enable it again, it appears as not working:

Windows can't load the necessary driver. The device is not working properly. (Code 31)

{Operation failed}
The requested operation was not successful.

(translated by me)
If I uninstall the network card driver from device manager, it is re-installed and everything gets back to ok (network and share center, card settings in the n&s centre, device manager, filter is there).
Anyway, VirtualBox throws either the VERR_INTNET_FLT_IF_NOT_FOUND or the VERR_SUPDRV_COMPONENT_NOT_FOUND error, or some times it even does not start at all with:

Calling RC :
CO_E_SERVER_EXEC_FAILURE (0x80080005)

(translated)

Out of ideas, really...

p.s. how to install the filter driver manually apart from using the card settings? I tried by device manager and it lets me select the inf file but the list of devices is just empty.
p.s.s. I also noticed sometimes (ie after first install) the filter driver is listed in the device manager (when showing hidden devices), sometimes it is not (even after uninstall and reinstall). It seems the latter case is the one when VB throws VERR_SUPDRV_COMPONENT_NOT_FOUND.

I would like to update the issue and post a solution. In fact, here VB was not at all working since months for this issue.
I found out ad advice of resetting the registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Config
Being a bit skeptical, I did a backup, removed VB, remove the Config key, reboot (a new Config key was generated by Windows), reinstall VB and voilà, everything is working again.

But, what an headache for getting here....

I know this thread has been marked as solved but i just want to add my experience today.
A client has been running a windows 7 host with 2 Windows XP guests for about 2 months now without a hickup and all of a sudden this morning the host developed the same issue as OP. The guests would not boot with networking in bridge mode as VBox did not detect the host network card. In NAT mode the guests booted but then RDP doesn't work.

It turned out that Kaspersky internet security was the culprit. Disabling Kaspersky, adding VBox to whitelist or uninstalling Kaspersky did not fix it. I then tried to uninstall and reload the NIC driver and vbox, i could only get rid of the driver in safe mode but trying to reinstall the driver would return a "access denied" error. I had to run system restore then use a Kaspersky scrubber immediately afterward to get rid of the broken installation left by system restore. Repairing or uninstalling the broken Kasperksy installation via control panel would just bring the issue back and no drivers can be loaded, not even a thumb drive would install successfuly.

I suspect MS updates triggered it as it was the last system change that happened right before the guests were booted for the new day. I'm not sure though, i didn't have much time to troubleshoot as the client wanted their POS system back up. OP mentioned he uses Kaspersky too so i'm fairly certain the solution posted above will work for me but i don't want to take the chance of this happening again.

Edit: The host mentioned in this post also has a Marvel NIC, same as OP.

TLDR: VBOX and Kaspersky Internet security are not friends.

Thanks ODTech for more insights.

I also want to add something, because my problem is not really solved, it reappears each reboot or hibernation. I wrote scripts that automatically restore the connection on the event there is not the possibility of contacting a dns server (event IDs), by uninstalling nic and vbox drivers and reinstalling them, but they are not trustable: they sometimes just fail doing their duties.
So I must say that, even if deleting that Config value in the registry solves the problem, it is not fixing it definitively. If I have the Vbox bridge driver and filter installed and active, my network receives/sends nothing. If I toggle the Vbox filter, it does work again! That's definitively blocking its operations. It is worth adding that, as ODTech underlines, the Kaspersky filter is installed and active too, but disabling it doesn't help at all.
So, I tried various combinations of filters/drivers removal/activations and found out that, apart from the fact that disabling the vbox bridge filter makes the connection instantly working again without reinstalling or uninstalling drivers, there is only another filter that seems to be blocking it: the Microsoft's LLDP protocol driver/filter. Disabling it makes the connection work again instantly, too! So I am now going to try leaving it off.
But, what is its use, actually? I found some articles about the lldp protocol but still got my ideas confused. What is it useful for?

Thanks.

windows 8.1 pro 64-bit / virtualbox 4.3.18 / karpersky internet security 2015 / same error with bridge networking

this is what fixed it for me: http://superuser.com/questions/376152/v ... ows-7-host

To satisfy the curiosity of future readers for whom Gtirloni's above link might well be broken, the solution being referenced is the MAX_NUM_FILTERS one which has been discussed elsewhere on this site.