Page 2 of 2
Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 2. Nov 2009, 19:06
by Mavtech
Deleting all Virtualbox entries in the registry and/or rebooting fixed this for me.
Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 9. Nov 2009, 22:27
by adamtarshis
Removing the registry entries and rebooting didnt help in my case - running on xp trying to upgrade to 3.0.10 from 3.0.4.
The fix for me was the following advice below that i found on
http://forum.oszone.net/thread-89196-49.html
What I had to do was go into the Local Policies security console and change the setting "Devices: Unsigned driver installation behavior: from "Not defined" to "Warn but allow installation".
Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 20. Nov 2009, 07:34
by kbook
Here's the way I install it on my VISTA
- Run the installation file "VirtualBox-3.0.12-54655-Win"
- Once the dialog shows up, don't click next but go to the temporary folder at
"C:\Users\xxxxx\AppData\Local" where xxxxx is your username.
- You will see Virtualbox folder. Then, copy those folder out to your desktop
- cancel the installation
Then, browse to your folder you just copy. Double click on the "VirtualBox-3.0.12-r54655-MultiArch_x86.msi" [for 3.0.12 version]
- install everything just like before. When a box popup asking about Trusting from Sun MAKE SURE you check ALWAYS. Then it should finish installation without any error. At least, this worked for me after I had 1603 many times.

Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 20. Nov 2009, 07:43
by jperlow
3.0.12 installed cleanly without errors... I guess .10 was a dud
Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 20. Nov 2009, 17:10
by remyzero
I was having the same error 1603 w/ trying to install v3.0.12 on one of my Vista 32-Bit Business PCs. I looked at the other posts about removing the registry entries or network adapter but the adapter was never created and I didn't bother looking through the registry.
I did try running as different users, disabling Avast's real-time protection and a reboot without any luck (user account control was already disabled a long time ago).
After remembering I had left the default setup options as 'install all' that included USB support, I tried disconnecting my external USB Sans Digital drive, but Windows was complaining about being unable to 'safely remove' the device. Now, with no programs open and no open files/sessions to that drive I looked at the task manager and killed the search/index service.
I was then able to 'safely remove' the USB drive and re-ran the setup again...this time it worked like a charm.
Hope it helps.
-Jeremy
Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 9. Dec 2009, 15:27
by randy
I also had the same error. After following all the suggestions in this thread (unplugging usb-drives, deleting all reg-entries containing "virtualbox" (some could not be deleted though) and rebooting), the installation was completed normally! thanks guys and good luck to the others with the same problem

Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 22. Feb 2010, 02:36
by teyu38
i had same error code 1603 (windows vista )! after remove VB, same thing (ccleaner to clean up registry and reboot : no way...)
I fix this problem using
Windows Installer CleanUp http://www.commentcamarche.net/faq/818- ... er-CleanUp 
Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 26. Mar 2010, 20:03
by spgle
Hi,
had the same and took a look at the web....
The following tips worked for me.
Context :
I'm using VB 3.1.6, under Windows XP 2003 SP2.
Tips:
I turned off the check on drivers properly signed or not. Disabling this check during
VB install for Windows in security policies made the VB install work fine.
I turned on the policy back after the install....
Other:
strange.... Policy for drivers was not set to disable install when the driver
was not properly signed but to 'ask me'....There is no validation requested during installation of VB, just a failed install. Turning off the check was the solution... at least for me.
Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 14. Apr 2010, 02:57
by Andrewzz
I have tried a lot to install the latest version of VB 3.1.6 but unable to.
I enable the installer to log it, and I found this on the log.
Code: Select all
DIFXAPP: INFO: ENTER: DriverPackageInstallW
DIFXAPP: INFO: VBoxUSBMon.inf: checking signature with catalog 'C:\Program Files\Sun\VirtualBox\drivers\USB\filter\VBoxUSBMon.cat' ...
DIFXAPP: ERROR: Signature verification failed while checking integrity of driver package 'VBoxUSBMon.inf' ('C:\Program Files\Sun\VirtualBox\drivers\USB\filter\VBoxUSBMon.inf'). (Error code 0x1: Función incorrecta.)
DIFXAPP: INFO: Successfully removed '{B7D782D2-96DF-4775-A0E1-A76CF7B04B65}' from reference list of driver store entry ''
DIFXAPP: INFO: RETURN: DriverPackageInstallW (0x800B0100)
DIFXAPP: ERROR: encountered while installing driver package 'C:\Program Files\Sun\VirtualBox\drivers\USB\filter\VBoxUSBMon.inf'
DIFXAPP: ERROR: InstallDriverPackages failed with error 0x800B0100
DIFXAPP: RETURN: InstallDriverPackages() 2148204800 (0x800B0100)
CustomAction MsiInstallDrivers returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 21:46:06: InstallFinalize. Return value 3.
It says something about drivers, so I disable the check of the signature, and try again to install but still unable to.
I'm using Windows 7 64x, any idea of how to make it work?
Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 14. May 2010, 16:31
by pmeadows
I am using 3.1.8 on Win 7 x64 and am having the same issue. I tried the .dll replacement fix for the msi through orca but haven't had any luck. I have rebooted a million times and tried running the exe as an administrator as well. Does anyone have a fix for this one? This is nuts...
Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 18. May 2010, 09:41
by IDEFIX76
Hello every body !
I have the same problem after install Visual Basic 2010 on my Windows 7 32bits.
I want to update my Vbox 3.1.6 to the 3.1.8 and this error appear
I've tried all your explains in this board but I can't install Vbox.
Somebody can help us ?
Thk
Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 24. May 2010, 17:30
by ricojonah
I've successfully overcome this 1603 error installation/repair/removal issue with version 3.1.6 by doing the following:
1) Performed a "barebones" installation of Virtualbox 3.2.0 (deselecting ALL optional components, including USB, Bridged Networking, Python support, etc.) The installalation completed successfully (I assume this left the old 3.1.6 drivers on the system, which I didn't want. On to step 2 to correct this..)
2) Ran the same Virtualbox 3.2.0 installer and selected the uninstall/remove option. The removal completed successfully.
3) Using the same 3.2.0 installer (again), performed a full installation of VirtualBox 3.2.0 (including USB / Python / Networking components).
NOTE: This worked for me on a 64-bit Win7 host. YMMV. If this works for anyone else (especially on a 32-bit host) please post to confirm.
Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 7. Jun 2010, 10:55
by mlivshut
Yes, this worked for me. My host is WinXP Home SP2. I'm running Ubuntu 9.10 guest.
My installation originally failed due to this problem:
http://forums.virtualbox.org/viewtopic. ... 64&start=0
After that problem was resolved, cleanup through your steps worked fine.
The only thing about this Oracle buyout is that they delete Sun/VirtualBox directory and delete Guest Extensions from there too.
If only they could copy it to Oracle/VirtualBox directory first ... that would be customer-friendly of them.
thanks!
Michael Livshutz
Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 22. Jul 2010, 16:29
by drexful
I was able to resolve this issue by unchecking the python support option during the install. I am running winxp SP3 for the host.
Re: VirtualBox Setup ended prematurely - Error 1603
Posted: 7. Feb 2014, 13:50
by johnbot
Had the same error installing 4.3.6 r91406 on Win XP SP-3. Went the easy way and followed
I was able to resolve this issue by unchecking the python support option during the install.
Worked perfect. (Thanks for posting, drexful

) Never needed Python support, had always disabled it in the past. Only this time I had thought "why not just install it?" - giving me trouble for nothing

!