virtualbox.org

Running Windows 10 build 10240 with VirtualBox 5.0.4r102546 I see that VBOX will not list an interface in the list of adapters available for bridging unless the interface has either Ipv4 or IPv6 protocol linked to it. If the NIC has an IP on the host seems not to make a difference. I want to only have the VirtualBox NDIS6 Bridged Networking Driver linked to NICs that are only used for bridged networking for guests. Anyone else experience this?

Morgan

I have the same problem after upgrade to 5.0.4 on the Windows 10 host with Hyper-V installed but not enabled.

I've got the same problem, same VirtualBox version, but Windows 7

Yep. I have done this for years, but it fails on Windows 10 host with VB 5.0.4.