virtualbox.org

I've got a problem with the way VirtualBox handles bridged NICs on Windows 10 since v5.0.4. The scenario:

- 6 physical NICs on my workstation, only 2 of them show up in the pulldown list in VM settings. I run 4 different VMs on 4 bridged networks most of the time, and each of those bridged NICs has all protocols/services unbound except for the NDIS6 service and I've tried uninstalling/rebooting/reinstalling.

- Kaspersky Antivirus installed, but disabled during testing.

- NAT isn't an option for most of these networks.

- Reverting back to v5.0.2 solved the problem, until Windows 10 v1511 (build 10586) was rolled out. After that, v5.0.2 wouldn't start up (would fault with Exception Code 0xC0000005 in Application Event Log).

- Upgraded to VirtualBox v5.0.10. App now starts, but the Bridged NIC issue has returned (or likely, has been there ever since v5.0.4)

- I thought the issue might've been related to a Via-chipset 4-port card, so swapped that out for a brand new Intel Quad Port Adapter, but the problem is still there.

- I've noticed that after I changed to the Intel Quad Port adapter I could then see some (presumably all the enabled NICs that also had the NDIS6 service bound) of the previously missing NICs, but then when I went to fire up a VM using that NIC, I'd get this error . Then I'd shut the VM down. And the next time I'd go to check the list of NICs, that NIC would then be missing.

- The only bridged NIC that seems to work fine is one that doesn't even have the NDIS6 service bound to it.

Any ideas?!

Brettt wrote:The only bridged NIC that seems to work fine is one that doesn't even have the NDIS6 service bound to it.

You figured out the bug yourself! Nice! For a workaround, take a look at viewtopic.php?f=6&t=70052&p=335562#p335562. See if that helps...

socratis wrote:

Brettt wrote:The only bridged NIC that seems to work fine is one that doesn't even have the NDIS6 service bound to it.

You figured out the bug yourself! Nice! For a workaround, take a look at ...(snipped because I've not been a member long enough to post URLs).. See if that helps...

No such luck, unfortunately! I'd been through the NDIS5 workaround before resorting to my original post - I uninstalled/reinstalled-with-the-NDIS5 parameter, but then was left with still just the one NIC to choose from. Checking the NIC bindings, none had the "VirtualBox Bridged Networking Driver", and I've not been able to install it via C:\Program Files\Oracle\VirtualBox\drivers\network\netflt either. You can pick it, its confirmed as being Authenticode signed, but it doesn't actually install anything. A couple of mentions that it was fixed in 5.0.6 though, will give that a shot now.

Yes, I realized that not all people had success, after I read the rest of the thread that I pointed you to. However, since you're going to be upgrading, why don't you go for the latest and greatest 5.0.10?

socratis wrote:Yes, I realized that not all people had success, after I read the rest of the thread that I pointed you to. However, since you're going to be upgrading, why don't you go for the latest and greatest 5.0.10?

Already did, see my original post

Yeap, you're right. One thing is for sure; pulling an all-nighter at my age doesn't help...

Test build 104375 (with filename VirtualBox-5.0.51-104375-Win.exe) solved the issue with bridged networking for me. See Ticket #14578 ("Unable to select network adaptor that has TCP/IP disabled.") for details.

LastWord wrote:Test build 104375 (with filename VirtualBox-5.0.51-104375-Win.exe) solved the issue with bridged networking for me. See Ticket #14578 ("Unable to select network adaptor that has TCP/IP disabled.") for details.

Thanks mate. Downloading now.

Update Edit: Yep, this solves the bridged networking issue perfectly. My thanks to whoever slaved over the weekend to work on this!