Win 7 64bit host network lost after install of 4.x

[djf94]

Can someone suggest anything else to try as i have now run out of ideas (and will soon start to run out of hair )

Attached are the install logs and hopefully someone might spot something and give some idea what else to try as I can no longer install any 4.x version of VirtualBox wihtout losing my host network connections

Host: Lenovo 14" Edge with Windows 7 SP1 64bit (FYI I have not tried 3.x versions of virtualbox)

The problem:
There is no error given during installing but the problem is after installing (which takes a very long time once it gets to 85% of the install bar - I believe this is where it is installing the Virtualbox network drivers) ALL host network connections lose their connection.

I had managed to install a 4.0.x version sometime ago but now 4.0.x and 4.1.x versions have the same issue. A friend with the exact same Lenovo Edge 14" (windows update and installed programs might be slightly different) can install without a problem!

If I untick the "VirtualBox Bridge Networking Driver" in the host's the network adapter properties then the connection is restored and okay. But after that of course I cannot access the virtualbox VMs via a network so this does not help me.

Looking at the VirtualBox Bridged Networking Driver in the host device manager it shows: "This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)." Manually trying to update the driver with the file in the Virtualbox directory gives the same error.

Also the "VirtualBox Host-Only Ehternet Adapter" device has the same status/error.

I have tried everything I can think of for several days:

• Run as admin
• Clear out driver store for any Oracle drivers (using pnputil.exe)
• Delete INFCACHE.1
• Deleted HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Config (this was when logged in with my account and not the admin)
• Set MaxNumFilters to 20 (14 Hex)
• Try to check the driver files signature is okay (using certmgr and signtool but not too sure how to confirm the results I get)
• Disable avast antivirus (this is disabling the service so it does not run at all and not just the disable shields)
• Update all windows updates
• Updated network drivers (LAN:Realtek PCIe GBE and Wifi:Intel Centrino Advanced-N 6200 AGN)

Many thanks and I look forward to being able to get VirtualBox running again (I miss it and need it)
James

[Etepetete]

I don't have a readily available fix for you but I would like to suggest checking the device manager as well as the LAN connection properties for errors.
You might want to follow the instruction listed in this post.
You can also try searching for more solutions by using for example google with the "site: forums.virtualbox.org" expression.

You can also try uninstalling, clearing userdata folders and registry and re-installing. (Be careful not to delete your VMs!)

[djf94]

Thanks and sorry for the late reply (thought the thread was set to inform me of replies but found out it was not)

I have tried and everything in device manager is fine. It is only when I enable the VirtualBox Bridged option in a network device' properties that the problem happens.

I have uninstalled CISCO Anywhere VPN on the host but still no luck

I have tried installing the latest releases for 4.0.16 but still the same problem.

I have a bug report open but no progress so have no idea if or when I might get an answer
I have to give up using VirtualBox as I have spent far too long trying to get it to work with no success

I have 2 new Lenovo Edge notebooks coming soon (not for me unfortunately) and will see how they go with VirtualBox but that is unlikely to shed any light on why my machine cannot work

Many thanks and if anyone has any other ideas to try let me know (I guess I will try as I really would like to get VirtualBox working again)
James

[joe_d]

I've had the same problem on Windows 8. I am afraid I have not found a complete solution, I am using the workaround of unchecking "VirtualBox Bridge Networking Driver" in the properties of my ethernet adapter. This is an acceptable solution for me as it doesn't stop me doing the things I want to do with the virtual machine. However I just wanted to make a post noting that the problem still exists with Virtualbox in Windows 8 and recording the solution that worked for me in case other people have the same problem.

The installation of the Virtualbox Host-Only Network Adapter somehow disables the host network adapter, or prevents it from being recognised by Windows 8.

After installation the network and sharing centre shows two networks, one for my physical Ethernet network adapter, and one for the Virtualbox one. After rebooting, however, my original network, the Local Area Connection network which uses the physical adapter, will have completely disappeared, only the Virtualbox network will be recognised or shown by the computer, either in the Network and Sharing Centre or by running ipconfig. Although the physical adapter will still be visible in the device manager, it is impossible to create a network with it, as it is not detected when you run the "Set up a new network" wizard. Windows 8 completely ignores the physical adapter and I simply cannot get it to recognise it is there or to use it. The troubleshooter detects a problem with the adapter but says it cannot fix it. The only network the computer will recognise is the Virtualbox Host-Only Network, using the virtual adapter. So the computer has no internet access at all.

The problem is fixed when you go into the properties of the physical adapter and uncheck "VirtualBox Bridged Networking Driver".