Bridged Adapter not working

[CraigBoyd]

Hello All,
I am getting the following error when I use a bridged adapter for VM:

Code: Select all

Failed to open a session for the virtual machine Oracle Developer Days.

Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) 82579LM Gigabit Network Connection' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

I am running Windows 7 pro 64-bit.
VirtualBox = 4.2.18
The guest is Linux (I have two or three different flavors and I get the same error on each one)

Any ideas what is going on or better yet, how to fix it?

Thanks,

Craig

[mpack]

It looks like you didn't install the bridged adapter filter driver. You can easily check this by checking the network adapter properties, see if "VirtualBox Bridged Networking Adapter" is one of the services attached to the card.

Windows 64bit hosts are sometimes configured to silently reject installation of what are in effect just non-Microsoft drivers. Google for "Driver Signature Enforcement", make sure your system is configured to at least prompt for permission.

Reinstall VirtualBox once you have fixed the host problems.

[CraigBoyd]

Thanks for the reply mpack,

I have tried uninstalling virtualbox and then:

Code: Select all

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS

bcdedit -set TESTSIGNING ON

No luck. So I uninstalled virtualbox again and tried:

Code: Select all

bcdedit /deletevalue loadoptions

bcdedit -set TESTSIGNING OFF

Still the same error.

I checked my BIOS settings (I have a Dell Precision laptop) and I did not see anything about Driver Signature Enforcement...I could have missed it, but I don't think so...

Any other suggestions on how to resolve this?

Thank you very much for your time.

Craig Boyd

[mpack]

I suggested that you Google for "Driver Signature Enforcement" - did you do so? Because you should have discovered that it's a Win64 feature, nothing at all to do with Dell. I'm afraid I can't expand on or endorse what a Google search will tell you, since I don't use Win64.

[CraigBoyd]

Hi mpack,

I apologize for my lack of clarity ~ I did Google "Driver Signature Enforcement" and the steps I listed in my previous post were the results.
I understand it is a function of Win64, but I read more than one post where that "feature" was enabled/disabled in the BIOS, hence my statement.

I have also since done the "F8, Disable Driver Signing" boot up option and that has not worked for me either.

I am beginning to think this may not be a driver signing issue. Is that possible? If it is not a driver signing issue any ideas what it might be and how to tell?

Surely I am not the first person to have this issue, especially as long as Windows 7 64 has been around.

Thanks,

Craig

[mpack]

The basic fact established by the error message is that driver has not been installed. This can be verified by checking the NIC properties as I suggested in my first message. Did you do that?

Once the basic fault is established we can only speculate on how it happened. The Driver Signature Enforcement cause is a common one on Win64 hosts, other common causes are: no admin rights, installing for the wrong user (e.g. installing for the "Admin" user instead of yourself, thinking that's how you get admin rights), or deselecting the relevant install options.

[Perryg]

Maybe http://www.virtualbox.org/manual/ch12.html#idp58424832

[mpack]

Ramshankar has also made passing mention of a network filter bug that will be fixed urgently. I'm trying to track down where this was discussed in more depth. This only applies to 4.3.0 as far as I know (not 4.2.18).

[CraigBoyd]

The basic fact established by the error message is that driver has not been installed. This can be verified by checking the NIC properties as I suggested in my first message. Did you do that?

Yes. When I look at the properties of the NIC I see: "VirtualBox Bridged networking Driver". Each time I have installed/uninstalled VirtualBox the presence/absence has been consistent with what I was doing. And if the driver was there it was also checked.

Once the basic fault is established we can only speculate on how it happened. The Driver Signature Enforcement cause is a common one on Win64 hosts, other common causes are: no admin rights, installing for the wrong user (e.g. installing for the "Admin" user instead of yourself, thinking that's how you get admin rights), or deselecting the relevant install options.

I have admin rights on the machine. I have not installed as "Admin". I have tried running as "Admin" and running it as myself. The error is exactly the same in each and every case.

Thanks,

Craig

[mpack]

Running as "Admin" is definitely incorrect, I mentioned it as a common error to avoid.

Ok, you seem to have established that the drivers are installed. Does the mentioned "Intel 82579LM Gigabit Network Connection" NIC exist?

[CraigBoyd]

Thanks Perryg ~ I increased the max value to 14 like it suggested, but no luck. (I did not reinstall for this change)

I am looking at the setupapi.dev.log and I see this error repeated:

Code: Select all

 Key      = VBoxNetFltM.inf
     sig:                          FilePath = C:\Windows\System32\DriverStore\Temp\{75be7ee1-5651-136e-6203-b63d9c73875a}\VBoxNetFltM.inf
     sig:                          Catalog  = C:\Windows\System32\DriverStore\Temp\{75be7ee1-5651-136e-6203-b63d9c73875a}\VBoxNetFlt.cat
!    sig:                          Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig:                          Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
     sig:                     {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 11:13:57.346

Not just for that inf file, but a LOT of the virtualbox inf files including the USB one. And then right below I see:

Code: Select all

{_VERIFY_FILE_SIGNATURE} 11:13:57.346
     sig:                          Key      = VBoxNetFltM.inf
     sig:                          FilePath = C:\Windows\System32\DriverStore\Temp\{75be7ee1-5651-136e-6203-b63d9c73875a}\VBoxNetFltM.inf
     sig:                          Catalog  = C:\Windows\System32\DriverStore\Temp\{75be7ee1-5651-136e-6203-b63d9c73875a}\VBoxNetFlt.cat
     sig:                          Success: File is signed in Authenticode(tm) catalog.
     sig:                          Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
     sig:                     {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 11:13:57.397

It is almost like it fails the first time and then gets it right the second time. Again, this pattern is frequently repeated...can't say it happens 100% of the time, but ...

Thanks,

Craig

[CraigBoyd]

Running as "Admin" is definitely incorrect, I mentioned it as a common error to avoid.

Ok, you seem to have established that the drivers are installed. Does the mentioned "Intel 82579LM Gigabit Network Connection" NIC exist?

Yes, the NIC is always present regardless of whether or not virtualbox is installed / not installed.

Thanks,

Craig

[mpack]

Well, given the error message you just mentioned, it seems we're back to Driver Signature Enforcement. If it rejected a driver then it should have warned you. The fact that it didn't implies that drivers are being rejected out of hand - and that's a Win64 host config issue (which, incidentally, is totally separate from admin privileges).

[CraigBoyd]

OK...so what are my options at this point?

Thanks,

Craig

[Perryg]

Did you read the second bullet "The INF cache is corrupt" ?