4.0.4 install errors - destroys host networking

[ebonweaver]

At least in the case of an upgrade install, the latest 4.0.4 installer kicks this error when installing network drivers: Error Renaming Connection Cannot rename this connection. A connection with the name you specified already exists. Specify a different name.

The install seems to finish, though Windows kicks the typical "this didn't install properly" dialogue. However, networking on the host is then broken, the network location is damaged beyond Windows ability to repair. In other words, your installer just bricked my machine until I apparently figure out how to repair the destruction of my network card/drivers/configuration.

[ebonweaver]

After a lot of uninstalling and reinstalling I have restored all system functionality and have 4.0.4 installed properly. Without spending a lot more time on painful testing, it is either that installing this version over the last version breaks things, or installing this version under a user account and providing admin credentials causes problems compared to installing under an admin account. In either case, neither has been a problem in a past.

for reference this is on Win 7 64bit which I know you have had compatibility problems with before, this was just more dramatic as it killed host functionality.

[Chuck McKinnis]

I have also observed this in Windows XP SP3 when upgrading to 4.0.4 and 4.0.6. The message I get when attempting to open a network folder is "No Network Provider accepted the given network path". I found a workaround to the problem by uninstalling Client for Microsoft Networks, re-booting, and installing Client for Microsoft Networks. I suspect that something in the VirtualBox networking installation is corrupting the Client for Microsoft Networks installation.