![]() |
| Install Software via Sandbox and leave installed if OK? |
|
Guest10
|
I'm not sure if you realize the difference between installing a program normally, and then running it under Sandboxie's control, or installing a program in a sandbox - which will have the effect of always running under Sandboxie's control.
So, just to make sure that it's clear: In the first case, if the program is installed normally, then all of it's files and Registry entries are installed outside of the sandbox. In this case, you would probably run the program under Sandboxie's control by using the right-click "Run sandboxed" option. Or, the program could be forced to run under Sandboxie's control every time it starts, if you have a registered version of Sandboxie. In the second case, a program is installed inside of a sandbox by creating a sandbox for the program (if it doesn't already exist), and then right-click the installer for that program > Run Sandboxed > (pick a sandbox for the install). In the installer program you might choose a path for the install like: C:\Program Files\Program Name\ and when the program runs, it will think that the actual path to it's folder is the above. But the actual path to 'program.exe' would be: C:\Sandbox\(user)\(sandbox)\drive\C\Program Files\Program Name\program.exe In this case all of the program's files and Registry entries exist only inside of the sandbox, and the program will automatically run sandboxed because of that. If you want to, you can get rid of the entire program's install by deleting the sandbox contents. Or, keep it in the sandbox for each use. After trying the program while it's installed inside a sandbox, you might decide to delete the sandbox contents and install it normally. |
||||||||||||
|
_________________ Paul XP Pro SP3 (Admin rights), Zone Alarm Pro Firewall, Malwarebytes Pro, Firefox 21, Thunderbird 17 |
|||||||||||||
|
JohnBox
|
Thanks for the detailed information, yes I do get the difference between sandbox and normal install. Thank you.
What you mention last is what I wanted to know about. When I am happy with the install in the sandbox I was looking for an option to simply allow it to be written to the drive, without installing it normally again, perhaps simply recover to the same folders/registry from the Quick Recovery, is that possible? I have C:\ in the Quick Recovery folders set for the sandbox, so that should work, no? After checking the software out, simply recover from sandbox and let it be written to the drive, no? |
||||||||||||
|
|
|||||||||||||
|
Guest10
|
If you set C: drive as a Quick Recovery folder, then all of the folders and files that are stored in the sandbox during the install will be available from the QR window, but none of the Registry entries will be recovered. Depending on the program that you install, there could be a large number of folders/files that you would have to scroll through and decide which ones to allow to be moved outside of the sandbox, overwriting those that may already be there. Of course, you could just allow all of the folders/files to be moved out, if that's your choice, but as I said that will not move Registry entries. The only approved method is to install the program normally, outside of the sandbox, once you are satisfied with it. |
||||||||||||||||
|
|
|||||||||||||||||
|
JohnBox
|
Great to know, thank you!
|
||||||||||||
|
|
|||||||||||||
| Install Software via Sandbox and leave installed if OK? |
|
||
|


Use the RSS feed to watch this topic for replies