Bridged Adapter Issues causing VM to error on boot

[ilie]

hello
i m running 4.2.4 on w7 and i get the following error on boot

Failed to open a session for the virtual machine xp.

Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) Centrino(R) Advanced-N 6205' (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 {db7ab4ca-2a3f-4183-9243-c1208da92392}

In NAT mode it works
I ve tried reinstalling the bridge adapter re install the Vbox no success
Thank you!
IN

[mpack]

Reinstalling the bridged adaptor? That should not be necessary.

The error message is that the NIC you are trying to bridge to does not exist on that host. Is the error message wrong?

[ilie]

yes the adapter exists!
in the
Control Panel\Network and Internet\Network Connections
i see same device name
Intel(R) Centrino(R) Advanced-N 6205
thank you!
IN

[terribille]

I have same issue on my laptop (WiFi network interface), after upgrading from 4.1.8 to 4.2.4. Also I can't install host-only interface getting error "Failed to create the host-only network interface."

It is strange that on my office machine that is connected trough wired interface everything works perfectly.

[mpack]

Same issue? "Host Only" and Bridged networking (the OPs subject) are entirely different modes. Anyway I suspect you neglected to install the Host Only driver when you upgraded VirtualBox. Talk of the hosts wireless (or any other) physical NICs is not relevant when discussing Host Only mode, which is entirely virtual.

[Perryg]

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

[ilie]

hello,
i ve tried the suggestion on your post - same result

Failed to open a session for the virtual machine mint.

Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) Centrino(R) Advanced-N 6205' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

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

thanks !
IN

[terribille]

Same issue? "Host Only" and Bridged networking (the OPs subject) are entirely different modes. Anyway I suspect you neglected to install the Host Only driver when you upgraded VirtualBox. Talk of the hosts wireless (or any other) physical NICs is not relevant when discussing Host Only mode, which is entirely virtual.

I've meant same issue with bridged networking, but also have issues with host only ... And I've certainly had Host Only driver checked on. Sorry for confusion I've made.