Bridged network fails after driver update

[rconway]

Having updated the network drivers on my WinXP host I now receive the following error when attempted to start my virtual machine...

Failed to open/create the internal network 'HostInterfaceNetworking-Broadcom NetXtreme 57xx Gigabit Controller' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Details...
Result Code: E_FAIL (0x80004005)

I have tried to uninstall / re-install VirtualBox (3.0.6) but the problem remains.

I even created a new virtual machine with the same bridged network configured - but this receives the same error.

Any suggestions as to how to resolve this issue?

Cheers.

[Perryg]

Have you tried a power cycle on the host? (complete shut down restart)

[rconway]

Yes. I power-cycled platform after uninstall of VirtualBox and before reinstall. I think I've even rebooted again since reinstall (just to be sure!).

[Perryg]

What happens if you roll back the driver in the device manager? It might be a conflict I guess.

[rconway]

Had the same thought myself. However, the attempted driver rollback indicates that no driver files have been backed-up. I might try to manually 'roll-back' to an older driver - if I can get hold of one.

[Perryg]

System restore should retain the driver if it has not been that long ago.

[rconway]

Never used System Restore before. Is it reliable? I can see the restore points that relate to my driver updates, so I might give this a try. Slightly nervous about totally stuffing up the platform though!

[Perryg]

Well nothing is perfect in this world. I know it has saved my beacon at various times and I have not had a problem using it, but one never knows.

[rconway]

I'll give it a try. Thanks for the suggestion.