Bridged adapter stops working after reboot / win10

[oucil]

This started with the 5.0.10 release, but I can install VirtualBox with bridged adapter, boot my VM's, everything is great. But then when I reboot windows, VirtualBox can start without problems, but when I bring up my VM's there is no connectivity, the bridged network adapter is gone. The only process I can follow to continue working is to literally uninstall and reinstall VirtualBox, no reboot required, then when I bring up my VM's everything is as it should be.

I can work with this because I rarely reboot, but with win 10 forcing reboots again, now this is becomming more of a pain in the ass. Any ideas?

Thanks,
Kevin.

[vanber]

hi

I'm french and i have exactly the same pb :
When I reboot the virtual machine the network does not always work.
I need to change the parameter of the network card by putting "no connection" then reselecting "bridged" and everything works again
I never had a problem before the latest version
The host server is Win 7-64 bit

[oucil]

I've tried disabling and re-enabling the bridged network adapter in the VM settings, but it didn't have any effect for me Only a complete uninstall/reinstall gets it back up again. But glad to know I'm not alone with this version not playing nice with the bridged adapter.

[socratis]

But glad to know I'm not alone with this version not playing nice with the bridged adapter.

Actually, if you had only searched for something like "virtualbox windows 10 bridged not working" you'd have seen that you're absolutely not alone. You might have also found a couple of workarounds and potentially a test build that might fix the problem...

[oucil]

Actually, if you had only searched for something like "virtualbox windows 10 bridged not working" you'd have seen that you're absolutely not alone

Actually, I did search, tried 20 different combinations of terms, but nothing hit that looked related. Some of those threads are 50 pages long and again didn't look related in the first few pages. Sorry but phpbb's search sucks, finding relevant comments is a pain, and solutions even harder. Thanks for pointing to a couple resources, I'll check those out and post a working solution from them here so others might be able to source it faster.

[oucil]

Actually, if you had only searched for something like "virtualbox windows 10 bridged not working" you'd have seen that you're absolutely not alone

Yeah, so thanks for the lmgtfy link, charming, but regardless of the inclusion of Windows 10, half the comments are about linux builds, and the other half are about windows 10 pre-release builds. You might understand why it was difficult to find appropriate answers.

You might have also found a couple of workarounds and potentially a test build that might fix the problem...

While in a development environment, I rely on this as my daily driver, so moving to pre-release builds of VB for a solution for one problem, often results in other things breaking. Again, thanks for the suggestion, but I can get by on uninstall/reinstall until a stable solution to the problem exists.... which is what I was looking for in the first place.

[loukingjr]

While in a development environment, I rely on this as my daily driver, so moving to pre-release builds of VB for a solution for one problem, often results in other things breaking. Again, thanks for the suggestion, but I can get by on uninstall/reinstall until a stable solution to the problem exists.... which is what I was looking for in the first place.

FWIW…

Test builds. If you want advance peeks at what has changed since the last stable release, or to help us catch little problems which may have sneaked in and which we failed to spot, we encourage you to regularly try out test builds. Doing this greatly helps our testing effort. We only add features and fixes to these builds that we think are ready for release, so the stability of these builds should be similar to that of official releases.

If it doesn't fix your problem you can always roll back to the stable version.

The majority of the problems with bridged seem to be related to Realtek networking drivers. I've had a Windows 10 host machine since it's release and have had no issues with the bridged adapter. My host however is using Intel networking drivers.

That being said, I don't know if the current test build addresses the Realtek issue because I don't have one.

[oucil]

Thanks @loukingjr, that inspires a little more confidence in the pre-release builds. I'll give that a shot.