Windows 7 64 bit
Virtual Box 4.1.20
Lenovo T420
New install not had a VM working on this machine.
Bridged networking selected.
Get the following error:-
"Failed to open a session for the virtual machine Bitnami Linux.
Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) 82579LM Gigabit Network Connection' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}"
More detail:-
00:00:01.763 IntNet#0: szNetwork={HostInterfaceNetworking-Intel(R) 82579LM Gigabit Network Connection} enmTrunkType=3 szTrunk={\DEVICE\{F27C6ACF-F3D6-408D-8B3A-257539CF2548}} fFlags=0x14000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:01.763 VMSetError: D:\tinderbox\win-4.1\src\VBox\Devices\Network\DrvIntNet.cpp(1694) drvR3IntNetConstruct; rc=VERR_SUPDRV_COMPONENT_NOT_FOUND
00:00:01.763 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) 82579LM Gigabit Network Connection'
00:00:01.763 VMSetError: D:\tinderbox\win-4.1\src\VBox\Devices\Network\DevE1000.cpp(6030) e1kConstruct; rc=VERR_SUPDRV_COMPONENT_NOT_FOUND
00:00:01.763 VMSetError: Failed to attach the network LUN
00:00:01.763 PDM: Failed to construct 'e1000'/0! VERR_SUPDRV_COMPONENT_NOT_FOUND (-3700) - The component factory was not found.
00:00:01.903 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) 82579LM Gigabit Network Connection' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
00:00:01.903 Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND)}, preserve=false
Tried the advice in this thread 47841
1) Modifying value of reg key to 20 - no effect
2) Deleting control regkey - no effect
3) Various uninstalls and reboots as per the above
4) Delete of infcache.1 - no effect
Did notice event log entries occur multiple times with each install - could be related.
Log Name: Application
Source: Microsoft-Windows-CertificateServicesClient-AutoEnrollment
Date: 21/08/2012 22:49:03
Event ID: 6
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Automatic certificate enrollment for set failed (0x8007003a) The specified server cannot perform the requested operation.
.
Suggestions anyone? Im wondering whether this is security related as this is work PC and may have a setup that is interfering with proper function.
Simon
Bridged Adapter Issues causing VM to error on boot
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Bridged Adapter Issues causing VM to error on boot
Does it work with VBox NAT? If so then I would ask your IT department what needs to be done.
Re: Bridged Adapter Issues causing VM to error on boot
It boots up with NAT but then doesnt get a NAT IP but this might be down to the config of the guest.
I did refer it to IT but they dont seem to know much!
I troubleshot this myself - looking in the setupapi.log I saw a number of the following messages:-
sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
! 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: 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: 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: 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.
So i spent time installing the certs from the .exe. No difference.
Also ensure the group policy allowed me to install the certs. no difference.
Then spent time using Orca to expand the MSI as per viewtopic.php?f=6&t=45536&start=15.
Still had driver issues.
Then installed the Windows 7 dpinst package to install the drivers as pnputil wasnt working.
Drivers installed but it made no difference to virtualbox.
So ive been round the houses and am back at the same place.
Any suggestions?
Simon
I did refer it to IT but they dont seem to know much!
I troubleshot this myself - looking in the setupapi.log I saw a number of the following messages:-
sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
! 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: 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: 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: 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.
So i spent time installing the certs from the .exe. No difference.
Also ensure the group policy allowed me to install the certs. no difference.
Then spent time using Orca to expand the MSI as per viewtopic.php?f=6&t=45536&start=15.
Still had driver issues.
Then installed the Windows 7 dpinst package to install the drivers as pnputil wasnt working.
Drivers installed but it made no difference to virtualbox.
So ive been round the houses and am back at the same place.
Any suggestions?
Simon
- Attachments
-
setupapi.app.log- windows/inf/setupapi.log
- (20.57 KiB) Downloaded 124 times
Re: Bridged Adapter Issues causing VM to error on boot
I am facing exactly the same issue. I am running 64-bit windows 7 on my W510 lenevo laptop, and I get VERR_SUPDRV_COMPONENT_NOT_FOUND error when I try to boot my ubuntu virtual machine. My network card is Intel 82577LM G. I tried various suggestion (same as listes by Simon) without any success. Recently released version Virtualbox 4.2 does not resolve the issue.
Thx!
Thx!
Re: Bridged Adapter Issues causing VM to error on boot
Same issue here: Windows 7 Professional SP1 64 bit host, Windows XP SP3 guest. It just happened after upgrading Virtualbox from 4.2.0 to 4.2.2 (see also thread nr 52252.)
Moreover I have no more Virtualbox host-only adapter: gone!!
Moreover I have no more Virtualbox host-only adapter: gone!!
Re: Bridged Adapter Issues causing VM to error on boot
Same issue here when I updated my Vbox.
Windows 7 Ultimate SP1 64 bit, host.
Windows XP SP3 Guest.
Virtual Box 4.2.4-81684
NAT network works, but Bridge not work.
Windows 7 Ultimate SP1 64 bit, host.
Windows XP SP3 Guest.
Virtual Box 4.2.4-81684
NAT network works, but Bridge not work.
Re: Bridged Adapter Issues causing VM to error on boot
I'm back here to relate my solution.
I just reinstall the "VirtualBox Bridged Networking Driver" and now everything is working.
Thanks.
I just reinstall the "VirtualBox Bridged Networking Driver" and now everything is working.
Thanks.
-
ilie
- Posts: 5
- Joined: 23. Nov 2012, 03:51
- Primary OS: MS Windows 7
- VBox Version: OSE other
- Guest OSses: w7,linux
Re: Bridged Adapter Issues causing VM to error on boot
hi
how did u re install the
"VirtualBox Bridged Networking Driver" ?
thanks
IN
how did u re install the
"VirtualBox Bridged Networking Driver" ?
thanks
IN