VirtualBox 4.3.20 install killed my system

Discussions related to using VirtualBox on Windows hosts.
Locked
twchan
Posts: 5
Joined: 26. Nov 2014, 19:18

VirtualBox 4.3.20 install killed my system

Post by twchan »

Hi,

I installed 4.3.20 (VirtualBox-4.3.20-96997-Win.exe) which seemed to indicate a normal successful upgrade (from 4.3.18). However, I lost my network once I launch a VM (with Bridged networking), which failed to start. Worst yet, after restarting the PC, Windows starts up but I lose all USB and all networking as well (the network icon on the Login screen shows an 'x'). The only way to recover was to do a System Restore back to just before the 4.3.20 install.

Anyone encountered this? Host is Win 8.1 Pro, Intel i7-4771, 32 GB RAM.

-T.W-
FoxJr
Posts: 1
Joined: 2. Dec 2014, 20:18

Re: VirtualBox 4.3.20 install killed my system

Post by FoxJr »

I'm experiencing the same problem.

I currently have virtual box 4.3.16 r95972 installed and everything works fine. When I try to upgrade virtual box 4.3.18 or 4.3.20 my PC network card becomes messed up and the whole system becomes unstable. Any suggestions? Below plz find PC specifications for your reference;

CPU: 3.07 gigahertz Intel Core i3 540 RAM: 8GB DDR3 HD: WD 500GB Network Card: Realtek PCIe GBE Family Controller Motherboard: ASUSTeK Computer INC. P7P55 LX Rev X.0x OS: Windows 8.1 Professional (Upgraded from Windows 8 Professional)

Thanks in advance.
VideOD
Posts: 2
Joined: 14. May 2015, 19:52

Re: VirtualBox 4.3.20 install killed my system

Post by VideOD »

Yes, I have the same issue with the latest update. Locked up my PC bad and had to do a system restore. Any thoughts? (Windows 8.1 home)

RE: installed this version - VirtualBox-4.3.28-100309-Win.exe
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: VirtualBox 4.3.20 install killed my system

Post by mpack »

If you have problems then you can describe them in the proper "Discuss the <xxx> release" topic, with the proper diagnostics (log files etc) to back you up. Ultimately you can raise a BugTracker ticket if you can describe a reproducable fault. The vague descriptions and "me too" reports in this topic are not very useful, so locking this to prevent more.
Locked