VERR_SUPDRV_COMPONENT_NOT_FOUND

[jonh001]

I have a Dell Latitude D630 running Windows 7.
I'm running VirtualBox 3.1.6 and I cannot get the Bridged Adapter working for any guest OS using any adapter.
I have tried it using XP and Ubuntu guest OS's and both wireless and wired network adapters.
I always get the same VERR_SUPDRV_COMPONENT_NOT_FOUND error.

Any ideas?

[Perryg]

Reboot the host and try again.

[jonh001]

Tried that. Rebooted countless times.
Tired uninstalling and re-installing VirtualBox.
My guess is that it's a Windows 7 issue.
Have another laptop (ThinkPad T61) running XP and it works fine.

[online]

Hi,
I have a similar issue, but I use WinXP as Host and Win7 or WinXP as Guest.
The issue occurs on both VM if I try to use bridging instead of NAT.

Any ideas?

Best regards,
Florian

[online]

sry. I forgot to tell that i also use a dell latitude d830 with VBox 3.1.6
perhaps the error only occurs with a "special" dell software/driver?

But it does not depend on the network card. I get the same error-message for Broadcom or 3-Com network card.

[frank]

Such an error usually means that the host network driver component was not properly installed. I suggest you to uninstall VBox completely, reboot the host and install it again. Make sure to NOT unselect VirtualBox Bridged Networking during the installation.

[jorgensen]

It might be this problem: http://forums.virtualbox.org/viewtopic.php?f=6&t=29365

[online]

Hi,
the problem is solved in 3.1.8.

regards,
Florian

[Mahi]

Hi,
Even I am facing the same issue. I am using Window 7 OS and HP ProBook 6460b machine

I am trying to load a Linux VM file through Virtual box.
Steps followed are:

1. Loaded the VM file using tab Machine->Add
2. Selected the network setting
Enabled network adapter
Selected Bridge Adapter under Attached to field.
3. After starting the VM, it is throwing up the same error as mentioned above in the post and unable to load the VM xml file and cannot create the VM with the same xml VM file
The same steps works fine on other machine ( Elite Book of HP) but it is failing on HP Probook 6460b only.

I have re installed Virtual box but the behavior is same.
Kindly help me in order to resolve the issue.

[chisels]

A coworker of mine had the same problem. We solved by going into Windows network adapter settings, finding the adapter used for the VirtualBox network, and performing an 'Update Driver' action from the properties menu. We didn't give a specific driver, and instead let windows automatically search. Windows gave us a 'adapter successfully updated' message, and then we could launch our VMs again, with full access. I'm thinking that probably doing a driver update automatically clears out the registry and whatever other settings are causing this problem. We also didn't need to uninstall or restart the machine or anything like that.

[mpack]

I think that this 9 year old topic (last post 6 years ago) should be laid to rest.