Setup Ended Prematurely

[Armada]

I have the same problem. This is a known problem, it has been on the bugtracker for almost half a year: Ticket #1730

I tried disabling background applications, I even ran a diagnostic start-up and then enabling the installer service but even that didn't work.

Here's my log: http://pastebin.com/f58c57593

[MasterYoda34]

Just FYI, I continue to get the same error message on version 2.1.

[Kent_Geek]

I have the same problem on 2.1.0, but all previous versions work fine on this machine. There's a new thread in which a few of us who have the problem on 2.1.0 are posting.

[dani]

Hi, I'm having the same problem installing VBox 2.1.2 on XP Pro SP3.
I've already tried disabling all nics but this hasn't solved the problem.
This is my log: http://pastebin.com/m1235cfaa

[dani]

I found the other thread and tried the special build contacting a developer.
It worked for me!
Link to my other post:
http://forums.virtualbox.org/viewtopic. ... 7600#57600

[shufty]

I don't know if the issue i was having was fixed in 2.1.2 since 2.1.0 but i have it installed now, not sure if removing all remnant directories from prog files had anything to do with it, failing because there are temp files in there. anyway, im sure a new one will be out soon for everyone to enjoy.

[Ademaro]

some problem.
log file in attachment.

p.s.: I have installed vBox v2.2.0

[Sasquatch]

some problem.
log file in attachment.

p.s.: I have installed vBox v2.2.0

About 2.2.0 was a known issue, which should have been fixed in 2.2.2 and 2.2.4. Please use 2.2.4 and see if you still have it. You can also try 3.0.0.

[Frode]

I've had issues upgrading since 2.1.2. I've got three computers stuck on various versions, unable to upgrade or uninstall. I've given up trying to fix it and just give it a try any time a new version appears, in the hope something magical happens.

[javier blanque]

Same problem with 3.0, trying to install with VBox 2.2.4, then removing 2.2.4, which ended with [grave problem] then removin manually the folders from the old installation, but the problem is the same [Sun xVM VirtualBox Setup Wizard ended prematurely].
If you have a solution, please, let me know...
Best regards,
Javier

[Monk]

It's frustrating. Since 2.2.0 I can't upgrade or uninstall. It fails to uninstall when I try, so I can't install a different version! ARGH!

http://www.virtualbox.org/ticket/3701#comment:3 and http://www.virtualbox.org/ticket/1730 give some insight which leads me to here:

http://www.virtualbox.org/wiki/MSI_Logging

OK! The MS cleanup utility worked for me! If you do this on Vista, remember to right-click the clean installer and run as administrator if you have UAC enabled. But now 3.0 installed and I'm too lazy to reboot to complete the install as instructed, but at least it let me install it!

I hope this helps anyone else with the same issue. Dunno if this was in a FAQ somewhere or what, but man what a pain.

[Frode]

You just made my xmas card list. That utility should be the first suggestion when people report this issue I think.

While the 3.0 installer still hung at the very end and had to be killed, it _did_ complete installation and everything seems to be working properly. Now for seeing if this fixes up the remaining machines.

[mrizzo]

I am having the same problems. I had no problem installing at home and now on my other PC, which is running Vista Ultimate - 32bit, I keep getting the premature error.
I have tried with 2.2.4 and now with 3.0.2. Same problem on each. I enabled the logging and will post that as an attachment. I am at a loss here, UAC is turned off, I even
tried to run as Admin anyhow....I have full Admin rights, never had any other version of it installed on this PC. No other VM ware environments are on the machine either.
I watched the Program Files dir and saw the VirtualBox directory get created, all the files were in there, right up until the message appeared on the installer.
I also found a file in the temp directory with a very similar time stamp, this file is called , 1f2f8559.msi.


Anyone have any other ideas on what I an try, I would really like to try and get this working as this is my main work PC and need this up and running.

Thanks

Mike

Update....When I unchecked USB and Network support, it then installed....I saw these two errors in the MSI.log file.
DIFXAPP: ERROR encountered while installing driver package C:\Program Files\Sun\xVM VirtualBox\drivers\network\netadp\VBoxNetAdp.inf (when I tried to install the network adapters)
DIFXAPP: ERROR encountered while installing driver package C:\Program Files\Sun\xVM VirtualBox\drivers\USB\device\VBoxUSB.inf (when I selected the USB support)

So it looks like it has something to do with the two adapters that are offered to you.

[vo_danh]

I had version VirtualBox-2.2.2-46594-Win.exe from a friend, it notified me there was an update VirtualBox-3.0.2-49928-Win.exe, so i downloaded the update and ran it right after i closed 2.2.2.

Gave me the error in this discussion on XP32 SP2. I think the 3.0.2 uninstalled the 2.2.2 to install the new version but ran into an error, when it cancled the install the program no longer showed up under remove programs. Tried reinstalling 2.2.2 and got the same error. Came here after some searched, and found this
http://www.virtualbox.org/ticket/3373 which fixed it. Although the user had an issue with an old vmware ethernet adapter installed, the problem was similiar. I removed the adapter the virtualbox installed initially that now has a yellow exclaimation mark showing it has a problem. I simply uninstalled/removed it and was able to install 3.0.2 immediately. Hope this helps.

[Frode]

The cleanup utility allowed me to install. On my XP 32bit I even got the networking component in ok. But my XP x64 still just hangs on that part. But at least I can get it installed if I just skip the network component. Haven't tried with just USB yet, since I was so happy to get the flipping thing updated finally. I believe I was stuck on 2.1.4 still.

I don't have any broken device drivers or leftover VMware protcols, so unfortunately this new information was of no help to me. But fingers crossed it helps someone else.