VirtualBox

Ticket #13713 (new defect)

Opened 5 years ago

Last modified 5 years ago

VirtualBox fails to create bridged or host-only network adapter on some Win7 desktops - Error FAIL (0x80004005)

Reported by: mkorning Owned by:
Component: installer Version: VirtualBox 4.3.20
Keywords: 0x80004005 Cc:
Guest type: all Host type: Windows

Description

Detected in: VirtualBox-4.3.20-96997-Win.exe

On some of our Win7 desktops with Broadcomm gigabit 57xx ethernet adapter, When installing or configuring VirtualBox, it returns error FAIL x8004005 and fails to create the virtual "host-only" and/or bridged network adapter. Switching to NAT also fails with a similar network-related error (cannot find network adapter for PXE boot or similar).

This error is occurring only on some (~10%) of our Qa desktops, but all have identical hardware and configurations running similar recent Win 7 builds.

Note that this error was also occurring also under Vbox 3.18 and VBox 3.16, for these same desktops, and is similar to many open defects already logged with oracle.

We have tried install/uninstall numerous versions of Virtual Box, as local and domain Admin, with AVG antivirus disabled, as well as uninstall + manual registry and driver-file cleaning as per FAQs, + system restores, and nothing fixes it. For these affected desktops, Vbox is unable to work.

Note that this error is very similar to open issue logged with Oracle, on which there is no resolution, but it seems very suspicious that it's working for most of QA and RnD, except for those recent windows builds.

Scenario 1:


On install, or subsequently from :

==> Vbox/File/Preferences/Network/Host-Only/ ==> try to create a new "host-only" adapter:

Result Code: E_FAIL (0x80004005)

  • In Device manager, every time this is attempted, we get a new "unknown" network device.
  • Manual device driver update fails (see attached screenshot)

Scenario 2:


On any guest image ==> Settingas/Network==> select "Bridged" network adapter ==> save and start guest VM: Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

Similar issues logged @ Virtual Box:


See attached vbox "setupapi" log files and screenshots


Attachments

setupapi.dev.log Download (71.6 KB) - added by mkorning 5 years ago.
setupapi.app.log Download (150.4 KB) - added by mkorning 5 years ago.
VBox Setup Issues - Error 0x80004005 creating host-only or virtual bridged network adapter.png Download (289.5 KB) - added by mkorning 5 years ago.
VBox Setup Issues - Unknown device added in DeviceManager instead of host-only or virtual bridged network adapter.png Download (490.6 KB) - added by mkorning 5 years ago.
VBox.log.3 Download (31.9 KB) - added by mkorning 5 years ago.
VBox.log with failed to create host-only adapter error
VBox.log Download (32.1 KB) - added by mkorning 5 years ago.
latest Vbox log from VirtualBox-4.3.26-98988-Win.exe
VBoxStartup.log Download (329.9 KB) - added by mkorning 5 years ago.
latest VboxStartup.log from VirtualBox-4.3.26-98988-Win.exe

Change History

Changed 5 years ago by mkorning

Changed 5 years ago by mkorning

comment:1 Changed 5 years ago by mkorning

(please ignore the "seems very suspicious + QA/RnD bit - this is not relevant to oracle and was copy/paste from our internal ticket logged with our own internal IT staff.)

comment:2 Changed 5 years ago by mkorning

  • Windows version: Windows 7 Ultimate 64-bit, Service Pack 1 [Version 6.1.7601]
  • Network Adapter: Broadcomm NetXtreme 57xx Gigabit Controller
    • Driver Date: 2009/04/26
    • Driver Version 10.100.4.0
  • AntiVirus: AVG Business Edition version 3495 (last update 2014-12-23)

comment:3 Changed 5 years ago by mkorning

Can we get some re-prioritization / escalation / or feedback on this issue? Issue has been confirmed to exist on all our Win 7 desktops (Win 7 SP1 - Version 6.1.7601), and is a blocker. If we cannot get this resolved we have to drop VBox, and use something else.

Last edited 5 years ago by mkorning (previous) (diff)

comment:4 Changed 5 years ago by frank

First, in the original report you were talking about 10% of your boxes, now you say that all boxes are affected. Did something change?

Also: There might be problems with bridged / host-only but what about NAT? I would like to see the exact problem you have with NAT networking, including a VBox.log file of a VM session were you configured NAT.

comment:5 Changed 5 years ago by klaus

In the bridged case the error message hints that the bridging support wasn't installed. Are you really sure that VirtualBox was installed completely? One can deselect the networking components during the install, and the expected behavior in this case would be this error message.

comment:6 follow-up: ↓ 7 Changed 5 years ago by frank

Looking at the log files you provided it looks like some signature verification problem. Looks like problems as described  here are similar.

comment:7 in reply to: ↑ 6 Changed 5 years ago by frank

Replying to frank:

Looking at the log files you provided it looks like some signature verification problem. Looks like problems as described  here are similar.

Actually I don't think that's not the problem. We see similar content in local setups so the signature stuff seems to be harmless.

Again, what we need are VBox.log files from VM sessions where you used bridged/host-only networking and another VBox.log from VM sessions where you used NAT networking.

comment:8 Changed 5 years ago by mkorning

Thanks - In Nov 2014 for compliance reasons with Quebec language laws, our IT department switched to deploying Windows7 ultimate with a default french (Canadian French) OS and display language. The problem appears to have started then, and every subsequent new dektop built at our shop now has the issue. This may or may not be the underlying issue as their may have been other config or policy changes deployed with that desktop build... We are continuing investigations on our side and will provide the log files shortly. Are there known issues with vbox installer on Win7 ultimate with other languages than US-english?

Changed 5 years ago by mkorning

VBox.log with failed to create host-only adapter error

comment:9 Changed 5 years ago by VVP

I uploaded 4.3 release for testing. Try it. I'll expect feedback with any results. Please, don't forget to save and upload installation log too.

https://www.virtualbox.org/download/testcase/VirtualBox-4.3.23-98273-Win.exe .

Last edited 5 years ago by VVP (previous) (diff)

Changed 5 years ago by mkorning

latest Vbox log from VirtualBox-4.3.26-98988-Win.exe

Changed 5 years ago by mkorning

latest VboxStartup.log from VirtualBox-4.3.26-98988-Win.exe

comment:10 Changed 5 years ago by mkorning

Got the same problem on VirtualBox-4.3.26-98988:

Failed to open/create the internal network 'HostInterfacenetworking-Broadcom NetXtreme 57xx Gigabit Controller' (VERR_SUPDRV_COMPONENT_NOT_FOUND). Failed to attach to the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).

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

-- attached (replaced) vBox.log and VboxStartup.log above...

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use