How to install a program that requires a re-boot?

[NewUser]

Some programs require that you re-boot the computer after you install them to complete the installation. How do I install such a program in a sandbox to be sure everything is captured in the sandbox?

How do I install a program in one sandbox and run it in another? For example, how do I install a browser in sandbox1 and run it in sandbox2 so that I can delete the contents of sandbox2 after the browsing session to delete cookies, history, etc. without deleting the installed browser?

[babybear]

I have exactly the same question. Is there any function in Sandboxie to perform a "fake" re-boot. I think whether this would work depends on which level the re-boot changes the system-files.....
BR, babybear

[SBIE User]

I have never tried installing a program in the sandbox that needs a reboot, so I can't help much.

However, in some cases the requested reboot may not even be necessary. You might want to look at the little portable, no-installation utility called WhyReboot at http://exodusdev.com/products/whyreboot .

That's not a sufficient answer, but you or others might find it useful in some limited cases where the reboot is not really required but is requested by the installation program.

[Sandbox User]

In my understanding you may just reboot and then execute the program you installed from inside of the sandbox.

=> You can have the windows explorer started sandbox, there you will find your newly installed program just after the reboot where you did installed it to.

[TerryWood]

To Sandbox User

Not sure I fully understand your reply. It would be of great help to me (and I am Sure others) If you could spell out the detail of what you have to do if a program requires a reboot>

Thanks

Terry

[Unknown_User_596]

@TerryWood

An easy way to execute the program after reboot may be: Right click on the explorer icon in the quick-launch bar. Then select "Run sandboxed". From this explorer instance navigate to the place where your new program is installed ("Program Files/...") and execute it from there.


But to stay clear: It is not a problem to execute the program after a reboot/thats need rebooting but I assume in most cases it will not work.

Typically a program requires to reboot because it is not able to exchange a driver file or locked file,... => Even if the progam "thinks" it has exchanged the driver in the system directory this is not true because the sandbox takes care this will not happen. So if that program needs a driver to be loaded this will not work.