Windows 7 host, VBox 3.2.4 cannot do bridged networking

[Mike Benson]

Upgraded from 3.1.4 to 3.2.4 on a Windows 7 Ultimate 64-bit host

Existing VMs would not start (E_FAIL). Checking the settings highlighted a problem with the network adapter.

The VMs all use bridged networking. The dropdown for the host network adapter to bridge was empty, and nothing could be selected.

Tried creating a new VM in 3.2.4, same problem - can't set network adapter to bridged networking, because I can't select a host adapter to bridge.

Downgrade to 3.1.8 - everything works as before.

[Sander van Leeuwen]

I assume that was caused by an installation problem. Could you generate installation logs and attach them here? (see ​http://www.virtualbox.org/wiki/MSI_Logging)

[Technologov]

Interesting bug. Added myself.

-Technologov

[lostwf]

I have encountered the same issue with Windows 7 64Bit and the latest version of VBox 3.2.8 or trying to go back to version 3.1.8. The Bridged network device only has no selections as an option

The windows clean utility has been removed, but I will add my log files Any ideas?

Thanks Wayne

[lostwf]

Upgraded to 3.2.10 but the issue is still the same. I am using windows 7 enterprise N

thanks

[misha]

Replying to lostwf: The logs attached show that your system has reached the maximum number of filter drivers it can handle.
Since you're saying that re-installing the 3.1.8 back still works, this makes me think that the 3.1.8 uninstall does not clean properly.
Could you please attach MSI & Setup API logs for 3.1.8 uninstall to see what went wrong with it.
Also, after the 3.1.8 is uninstalled, please open the device manager and select "View->Show Hidden devices" and check whether there are any "Network Adapters\VirtualBox*" adapters are still present and whether there are any network adapters marked with warning icon (containing yellow "!")
Please also specify which other networking-related components you have installed on your host (i.e. Antivirus, VPN, Firewall, Virtualization software, etc.)

[lostwf]

To clarify, VBox 3.1.8 does not work and VBox 3.2.8 does not work. Both show a blank for the bridged adapter. The Virtual box adapters do not show any errors or warning in the device manager

VBox host network works fine, the issue is with bridging

Trend Client/server security agent is used and the personal fire wall is turned off

Did not include the logs because 3.1.8 does not work when installed

Trying to install a FreeBSD guest. Will add screen shots

[lostwf]

screen shots

[lostwf]

Resolved my issue not sure if it resolves the issue for others, my Windows 7 had run out of network filters, changing the registry entry for network filers form 8 to 14 allowed the bridging to the adapters to show

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters

Installed 3.2.12 and bridging is working correctly

Thanks Wayne

[Ub3rSc0t3H]

Thank you ...

Resolved my issue not sure if it resolves the issue for others, my Windows 7 had run out of network filters, changing the registry entry for network filers form 8 to 14 allowed the bridging to the adapters to show

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters

Installed 3.2.12 and bridging is working correctly

Thanks Wayne

This solved my issue.. I am running Windows 7 Ultimate 64Bit... Changing that certain registry value.. did indeed once re-installing VirtualBox (after uninstall ofc) fix my/ and this issue.