SUN Virtualbox hangs at end of install

[czpb8q]

Hi,

I have just installed virtual box 3.0.0 on my Windows XP SP2 pc but the installation hangs (seems to do nothing although in task manager the status of "Sun xVM Virtualbox Setup" is still running) at the end of the installation routine. Does anybody know about this problem and how to fix it?

Greetz,
Stan

[accessory]

I installed VB 3.0 on XP with SP3 without a problem. I am not sure about SP2. In the end of installation, XP will ask you about some device drivers that do not have a certificate and whether you want to continue or not. Have you seen those warnings? You have to click "continue anyway" to complete the installation.

[Sasquatch]

Aside of the driver questions, check version 3.0.2 that's currently being uploaded if it gives the same problem. You might have to wait for the official announcement and download links.

[davebazaaro]

I'm experiencing the same problem.

Gets to the end of the install stating "Finalizing installation" and "Setup will complete in approximately: 1 minute" but stays at that point. Mouse still moves and animations still run, but that's it. I don't get any prompts regarding drivers.

My host OS is Windows Vista 64-bit
My Guest 0S is Windows XP Tablet PC Edition 2005
VitrualBox version 3.0.4

Any pointers would be great. Thanks in advance.

[Sasquatch]

Did you try to install VB by using the right mouse on the installer file and select "Run as Administrator"?

[CCCMikey]

I had the same problem installing 3.1.2.

I started killing things in Task Manager, and found the following:

1 - Kill Runonce.exe and your network adapters will reset and reconnect.
2 - Repeat kill Runonce.exe a few more times after giving it a little while to do whatever it's trying to do.

Install then finished normally. The only sign of problems is in Device Manager:



Virtual Machine Network Services Driver #9 reports an error: Code 19 - Configuration information in the registry is incomplete or damaged.

Perhaps it's having trouble because I've had many network adapters come and go in this PC, and it's also previously had an aborted install of VirtualBox (when this problem happened before and I gave up) as well has having Microsoft Virtual PC up until I uninstalled in order to migrate to VirtualBox again.

[PeterAndersen]

I got the same problem updating from 3.0.12 to 3.1.2 on a windows xp sp3 host.
Reading the above post, I checked that the program was installed, that the network adapters was installed.
After the installation had been hanging for a long time I kill the process in the task manager, no network problem and VB work like a charm - I will report if any problems occurs.

/Peter

[mpack]

I have just installed virtual box 3.0.0 on my Windows XP SP2 pc but the installation hangs

Did it really hang, or was it just taking a very long time to do something?

In all recent versions of VBox install I have noticed (and reported) that when the install appears to hang, if you look down at the quick launch area of the task bar, you may see a new network icon which is apparantly hunting for a connection. If you hover the mouse over this icon a tooltip will inform you that this is the "VirtualBox Host-Only Network Adapter" - in which case there's no way it can find a connection: with the VBox install not even completed yet, how could it find a VM to talk to?

So, right click on the icon and disable it. The VBox install process instantly completes. Then (before running VBox for the first time) you go into Device Manager where you will find the VBox Host Only adapter with a red cross through it: re-enable it and you are ready to rock.

[JPWhite]

I experienced similar problems installing onto a Windows XP SP3 host OS using VB 3.1.2 or 3.0.4. Hangs at the end.

I solved the problem by unhooking the cat5 cable from the NIC prior to installing VB 3.1.2. Towards the end one will notice a new network adapter trying to acquire an IP address. At this point I reconnected the CAT5 cable. The 'real' NIC retrains fine. After about a minute the virtual NIC trains successfully. All is well after that and the install completes just fine.

JP

[johnpfjefferies]

I also experienced this hang at the end of installation on a Windows XP host. As others have said, I aborted the process in the task manager and did successfully install Ubuntu. The problem is almost certainly related to installing the virtual network that others have mentioned. My pc is a laptop and the aborted installation was done whilst connected to the wireless network.

Unfortunately, the guess additions didn't work - the shared folders addition amongst a couple of others failed to install. Not too surprising.

I fixed it by connecting via a cable and restarting the Virtualbox installation. The installer appeared clever enough to know how far it had previously got, but more importantly the installation finished successfully. The guest additions then also built and being used successfully. [It wasn't quite a straight line, there were several other unsuccessful attempts at fixing it along the way, and several reboots, but I do believe that the fix is as simple as I've said.

John

[deeanna]

Hi,

I had the same hang occur to me - I'm running:
- WinXP Pro x32 SP3
- VirtualBox-4.0.8-71778-Win.exe

To resolve I did the following:
- I killed it through TaskMgr
- After the killing, I was then prompted twice more for the "continue anyways" prompts of which I "continued"
- After this finished, I ran the .exe again, and chose / ran "repair"
- repair found no errors

HTH,
Deeanna

[mpack]

Do not kill a Windows host install process with task manager. That will quite probably result in a botched installation. Instead disable the network icon on the taskbar as I already described above; this allows the installation process to complete successfully.

As to the suggestion of disconnecting the physical ethernet cable... I'm not sure why that should work: the virtual NIC in question is the "Host Only" one, which does not use a physical NIC.

[deeanna]

agree mpack; normally i do not kill an installation. however obviously something is wrong with the .exe / .exe builder.

Hence I ran the repair and all is fine

Deeanna