If you do this, and you've got a 'lot' of tabs open, when you run the browser unsandboxed, all these tabs will automatically open and 'suck' who-know-what into your now unprotected MS Windows installation. If the information in the tabbed sites is important to a current project, just deleting these may not be so attractive. As well, you may have Firefox set to automatically open a web page whenever it runs, and may prefer not to have this happen without protection.Sandboxie Firefox Tips:
Updating Firefox and its Add-ons
In the default configuration, any updates to Firefox or its add-ons will happen only within the sandbox. When the sandbox is deleted, all such updates will be deleted as well. To avoid this problem, you should run Firefox outside the sandbox when you recognize that any updates are available. Let the normal Firefox finish updating, including any necessary restarts of Firefox. Finally, exit Firefox and restart it under Sandboxie.
If Firefox is forced to always run under Sandboxie (as discussed above), use the Disable Forced Programs command to disable forced sandboxing for a duration of several minutes. Then follow the procedure in the preceding paragraph. Finally, use the Disable Forced Programs command again to resume forced sandboxing.
The workaround:Exit Firefox and delete the contents of its sandbox.
Turn Sandboxie 'off' (Disable Forced Programs).
Run firefox.exe -p
Create a new profile with a distinctive name, perhaps 'NoTabs'.
Double-click the new profile, and a tab-less, un-sandboxed Firefox will open. It will open to a screen that does not automatically display web content.
Open Help -> About, Click 'Check for Updates'. The update will download.
Turn Sandboxie 'on' again (cancel Disable Forced Programs).
Run firerox.exe -p
Double-click your original profile, and Firefox will open with the same tabs active, same homepage, all as before the upgrade was started. Verify the version, but it should now be the latest one.
There may be a problem with Firefox continuing to ask which Profile you want, at following startups, but the fix should be self-apparent -- there's a checkbox in the Profile Manager that stops this behavior.
