All, I'm trying to upgrade my Windows 7 host from 4.3.10 to 4.3.12 on Windows 7. When I start the installer, everything goes smooothly, until I see "rolling back action" and I finally get this:"Oracle VM Virtualbox 4.3.12 Setup Wizard ended prematurely"

Looking in the windows event logs., I got:- Error creating restore point. I resolved this and the issue still happened.- Error 1603, which looks like an installshield "machine specific" error. Since it's a catch-all error, I have no idea where to go from here.

Any ideas?

EDIT: Solved this by:

Uninstalling Virtualbox

Going into the registry at: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Network

Changing "MaxFilters from 8 to 20 (decimal)"

Rebooting

Installing 4.3.12

Really need better install logging.

Last edited by Tronmech on 19. May 2014, 21:34, edited 1 time in total.

Well, I figured out why the kernel driver wasn't found, the driver path was "\\??\C:\program files\Oracle\Virtualbox\vboxdrv.sys" I looked at a non-upgraded windows 7 host that is working, and the OTHER VBOX drivers, and the right path is "system32\DRIVERS\vboxdrv.sys"

I noticed that some people on this forum had issues with installs on Windows 7 when not runing as THE "Administrator" user. In that case, teh bridged network driver didn't install (and in my case it didn't either), so I'll try that, and if it still fails, I'll see if I can at least reset the Kernel driver and be at least functional.

Tronmech wrote:When I start the installer, everything goes smooothly, until I see "rolling back action" and I finally get this:"Oracle VM Virtualbox 4.3.12 Setup Wizard ended prematurely" Solved this by:

Uninstalling Virtualbox

Going into the registry at: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Network

Call me the mother of all noobs as I don't speak computer language but I'm trying my best to follow your guide.I did manage to go to into the registry: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Network BUT...Where do I find this "MaxFilters"?Please view my print screen here (via Flickr): /photos/98234538@N06/17326887452/(I'm unable to provide a proper link as I've just created an account here and I'm not allowed to post URLs just yet).Can someone please, please, please guide me? I've been tearing my hair out for days over this!I wanna install the VirtualBox so badly! PS: Pardon my broken English. Lol.

FYI: For those trying to get the latest version of VirtualBox (4.3.28) installed on Windows 10 and can't figure out why the install fails and it rolls back.. adding the MaxFilters key to the registry (above) works like a charm.

The latest version I was able to get to run on Windows 10 was VirtualBox 3.2.30.. which doesn't do much good if you're working with boot2docker.

Hope that saves someone else 3 days of their life noodling with intallers!

Have you tried this? My VMs wouldn't start until I did this. The problem is the VBox Installer. VBox uses a driver for the virtulization, and a registry key is pointing it to the wrong direction, and VBox VMs won't start because it needs the driver in order to virtualize the OS you're trying to run as a guest.Please close VirtualBox before doing this procedure, you can start it back up when you finish these simple intructions.1.Open Regedit in Windows2.Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\VBoxDrv3.Right-click on ImagePath and click Modify4.Copy and Paste this data:

In Windows 7 (don't know about the others) the installer uses rundll32.exe and dies as above when rundll32 is corrupted or missing.

To restore rundll32, follow the instructions below, expanded on those by Charles York, posted at answers answers DOT microsoft DOT com/en-us/windows/forum/windows_7-system/windows-7-rundll32exe-corrupt/bec29408-1a77-4703-bf03-dc73069aa838 [as a new member I can't post URLs].

Go to Start > All Programs > Accessories. There you must right-click on "Command Prompt" and choose "Run as administrator".

At the command prompt, type

cd \windows\winsxs

Now you need to find the directory where it is hiding. Enter

dir /s rundll32.exe

which will eventually return with the directory if it is there. To stop it searching needlessly any further, press Ctrl-C.

To save typo frustration, copy and paste the directory name (from the first character after C:\Windows\winsxs\):

cd <directory name>

Once you're in the correct directory, copy the file across (here is where you need to be administrator):

copy rundll32.exe \windows\system32\

Note that in the command prompt window, highlighting is block-orientated as opposed to line-orientated. This implies that if the directory name you want to copy contains a line break, you must copy and paste it in parts. The parts pasted together must not have any spaces in, unless the directory name has spaces, in which case you need to enclose it in double quotes.

If you can't find rundll32.exe using the above, try plan B in Charles's post. If that doesn't work either, search the Net for how to recover run32dll.exe from installation media. Using the installation media is quicker than plan B, though.

faridsaidan wrote:Call me the mother of all noobs as I don't speak computer language but I'm trying my best to follow your guide.I did manage to go to into the registry: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Network BUT...Where do I find this "MaxFilters"?Please view my print screen here (via Flickr): /photos/98234538@N06/17326887452/(I'm unable to provide a proper link as I've just created an account here and I'm not allowed to post URLs just yet).Can someone please, please, please guide me? I've been tearing my hair out for days over this!I wanna install the VirtualBox so badly! PS: Pardon my broken English. Lol.

Dont get it either, What if we dont have a MaxFilter? Where and How do we create one?

mdizzle9d9 wrote:FYI: For those trying to get the latest version of VirtualBox (4.3.28) installed on Windows 10 and can't figure out why the install fails and it rolls back.. adding the MaxFilters key to the registry (above) works like a charm.

The latest version I was able to get to run on Windows 10 was VirtualBox 3.2.30.. which doesn't do much good if you're working with boot2docker.

Hope that saves someone else 3 days of their life noodling with intallers!