Windows 7 network lost after Vbox update

[Linuxgod]

After updating Virtualbox to version 3.2.12, I have lost all networking capability in Windows 7. I spent an entire day dedicated to fixing it to no avail. The Network and Sharing center says the adapter is fine, but there is absolutely no connection. I have tried 3 different network cards, so it is not hardware related, Also I run a tri-boot system (Windows 7, Windows XP, freeBSD), and my other two OS's work fine. I am super frustrated! lol

What could the problem be? All the network settings look fine.

Dell Inspiron 530s
Core2Duo E4600 @ 2.4 Ghz
2 250GB HD's
tried Intel Pro10/100 & Realtek RTL8139 Network adapters
Nvidia G210 Graphics card

[Hachiman]

Could you please attach the log file?

[Linuxgod]

What log file do you want and where would I find it? There haven't been any errors reported. When I run Network Diagnostics, it simply says "Your network adapter has a problem, and that's it.

[Linuxgod]

I would think there is a bug in the virtualbox network drivers. However I did get it fixed by using the original Windows 7 disk and using the upgrade option it re-installed the original system files and it is running fine now.

I'll see if I can find the installation log for virtualbox and post it. I sure would like to know what caused it.

[fun_4_me_now]

Are you using Bitdefender? DON'T use it with VB!!!! Don't use it with Cygwin either.

I had the same type of network issue with bitdefender EVERY time I updated VB.

During initial setup on your machine BD2010 (and 2009) would do some type of system check and write to the windows registry. If VB was already installed it would continue to work just fine. Upon VB update, networking would die (vista32 host). After that initial setup it would never run that config again and NO amount of uninstalling and reinstalling (add remove programs OR bitdefender removal tool) would prompt that inital internal config to run again as the results were already in the reg.

The solution (direct from BD's very unwilling upper level tech support (actually the developers, I had to make it clear that I was not going away EVER and in fact scam their main corporate office #)) was to remove BD and then all registry keys related to BD (using a custom script they provided) and then reinstall BD.

It got to the point where for 2 years I pretty much was deleting/reinstalling BD EVERY time I upgraded VB!!!!!!!! I rarely got past the 30 day trial where it asks for my key, and they advised me that using my key too many times, even on the same machine will be flagged by their reg server and the key disabled, so to use the 30 day trial until I was sure everything was ok. I ran in trail even though I paid, for the remainder of my subscription. Using BD was very time consuming. I have since switched to Kaspersky as BD really doesn't come with tech support, just installation support and support on things that are in fact in the manual. They will NOT deal with any bugs or issues in their software and will in fact not even TRY to provide support. They will move to email correspondence and stop helping, or worse they will have you do time consuming things (just to keep you off their back) like format and reinstall windows/progs (6 times) .