Bridged adapter is broken in both 4.3.18 and 4.3.20

[zerkms]

20 minutes ago I've had 4.3.18 installed on Windows 7 x64 host which worked perfectly.

Then I noticed there is an update available and decided to update to 4.3.20 (and violated "it works - don't touch it" rule).

So, now I'm in the situation when under newly installed 4.3.20 I cannot run any VM that has a bridged network interface. The error on start is:

Code: Select all

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

Result Code: 
E_FAIL (0x80004005)
Component: 
Console
Interface: 
IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

And relevant lines from the log:

Code: Select all

00:00:03.041240 IntNet#0: szNetwork={HostInterfaceNetworking-Realtek PCIe GBE Family Controller} enmTrunkType=3 szTrunk={\DEVICE\{57CC0D36-4D32-4BC6-8AA5-A262A008E07F}} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:03.041292 VMSetError: F:\tinderbox\win-4.3\src\VBox\Devices\Network\DrvIntNet.cpp(1752) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:03.041490 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller'
00:00:03.041535 VMSetError: F:\tinderbox\win-4.3\src\VBox\Devices\Network\DevE1000.cpp(7693) int __cdecl e1kR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:03.041537 VMSetError: Failed to attach the network LUN
00:00:03.041546 PDM: Failed to construct 'e1000'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.

I tried reinstalling with rebooting million times with the same result. The 4.3.18 works exactly the same.

So seems like some last windows 7 updates prevent virtualbox from installing correctly.

Now I'm in stuck - I cannot get the new version working, I cannot get the old version that has been working for weeks working again.

Any known solution for this?

UPD: tried 4.3.16 which I used some time before and it worked successfully. Now it does not with the very same exception.

[mpack]

You don't have the bridging driver installed. Always using "Run as administrator" when installing VirtualBox on a Win64 host.

[zerkms]

You don't have the bridging driver installed. Always using "Run as administrator" when installing VirtualBox on a Win64 host.

1. I did do that explicitly after I found people recommend doing that. It changes nothing
2. Under windows 7 with enabled UAC it's not possible to install software under non-privileged account, so using "Run as administrator" technically changes nothing (but I still followed this instruction with no luck)

Any other ideas? I'm sure anyone with win7 x64 and all the latest upgrades installed might reproduce it easily.

The host-only adapter is installed though and is listed among network interfaces.

UPD: I just realized that I checked the VB bridge adapter in a wrong place which is in fact is just a filter. But anyway, the installation seems to become broken at least on my machine. I restored it from backup to get VB working again, since I could not get even older versions of VB working. Which may point to the fact that it's win7 x64 updates that interfere with VB installer now.

[Andak]

Same goes with me...anyone can help?

[BillG]

There are two possibilities. Either the bridge filter driver is not enabled or not installed.

Go to the properties on the NIC in the host OS. Look for an entry for VirtualBox Bridged Networking Driver. If it is present but not checked, check it. If it is not present, the quickest fix is usually to uninstall then reinstall VirtualBox.

[zerkms]

the quickest fix is usually to uninstall then reinstall VirtualBox.

It does not help. I had to recover my windows instance from a backup to get VBox working back.

[chf]

I'm seeing the same behavior. I was running 4.3.20 with no problem until I applied the latest update to Win 7 64bit. Now none of my VMs will start. I even tried switching one to a NAT network to no avail. All my guests are Linux Getting following errors:

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}


Any help would be hugely accepted!!

[socratis]

@chf
You do not have the same problem as the original poster (OP). What you seem to have is a case of the hardening security issues with VirtualBox > 4.3.12. See the "Windows 4.3.20 specifically for errors due to security" sticky at the top of the forum.

[zerkms]

So, I installed 4.3.26 and it's still the same.

Guys, are you going to fix it one day?

[BillG]

Well since you ask, no we are not. There are several reasons for that. The first is that you have not given enough information to pinpoint the problem. The second is that we can't because we are not part of the dev team. We are just users, like you.

[zerkms]

Well since you ask, no we are not. There are several reasons for that. The first is that you have not given enough information to pinpoint the problem. The second is that we can't because we are not part of the dev team. We are just users, like you.

Not sure what else I need to provide. I provided the relevant part of the log.

[socratis]

So, I installed 4.3.26 and it's still the same.
Guys, are you going to fix it one day?

and a few minutes later, in another thread, titled Fail to start bridged guest vm:

any chance you have kaspersky products running? Seems like I have found the solution for my problem (which looks suspiciously similarly)

and then again later in this thread:

Not sure what else I need to provide. I provided the relevant part of the log.

So, what's going on zerkms? Have you or have you not found the solution? I was about to suggest Kaspersky, since it's been known to cause similar problems with bridged adapters. If that doesn't work, then look for a possible solution to try at the third thread you posted about your problem, Can't start any VM with bridge configuration. Other users there have reported success with some step-by-step instructions provided by MartinŠ.

[zerkms]

For my problem I found that it helps to disable kaspersky NDIS filter. Then restart interface. Then run VM. Then enable Kaspersky.

[BillG]

Indeed it will. When you enable bridged networking, you insert a filter driver which interacts with the NIC driver to allow the virtual machine to share the NIC. The vm NIC is essentially getting a piggyback on the physical NIC. Any respectable NDIS filter will pick this up. For the same reason, bridged networking fails with a lot of wireless NIC configs.

[zerkms]

Indeed it will. When you enable bridged networking, you insert a filter driver which interacts with the NIC driver to allow the virtual machine to share the NIC. The vm NIC is essentially getting a piggyback on the physical NIC. Any respectable NDIS filter will pick this up. For the same reason, bridged networking fails with a lot of wireless NIC configs.

What is not explainable - is why it *requires* disabling-enabling Kaskersky NDIS.

I would understand if it was a consistent behaviour - that it alway does not work with Kaspersky enabled, but the fact that it works after enabling it back makes me thinking that it's some state that VBox team could take into account.