If one does a Windows Shut-Down with Sandboxie still active in the System Tray, are there any complications? Let us assume the program defaults are set (Automatic Sandbox Clean-up, Never Automatically).
Would the existing sandbox's operation and normal function continue, as before the Shut-Down, upon the next Windows boot-up, when the Sandboxie Control program is automatically or manually re-started?
If Sandboxie is set to clean-up "When Sandboxie Closes," and the user just shuts down the OS, does this trigger the clean-up, or does Sandboxie have to be closed first with its own "Exit" command for this to occur?
I haven't had any problems but I like to have an idea as to what a program considers as "normal operation" to avoid the unexpected. I did search the Forum for "Shut-Down" and found nothing, but if this question is answered in documentation elsewhere on the site, just direct me there.
Windows Shut-Down with Sandboxie running
From your knowledge of the program's operation and integration (is this the right word?) with the OS, would these "problems" be limited to inability to recover sandbox contents? This is OK.tzuk wrote:... there is room for problems if the delete process takes too long. Windows could decide that Control.exe is taking too much time to end itself, so it would help it to end.
However, the real reason for my question was to make sure there would be no lasting effects on the OS ... anything that could persist into the next re-boot. For example, is there anything you know about the program's operation that could leave the OS looking for part of the Windows Registry in a now-nonexistent location? Or is this a non-issue?
I think most users don't automatically remember to turn off processes running in the System Tray before turning-off their computers. Usually it isn't necessary. Is Sandboxie different or in any way more "delicate" than normal, because of what it does?
The Anything Else forum makes for fascinating reading. Am I correct that I found in a prior post the answer to my concern, namely, that, without a "graceful" exit, the Windows Registry may become confused?
With all the reports of how great the program runs I was beginning to thnk that my concern about the Registry problems was misplaced. To explain my concern, the Registry on my previous install of Windows had become such an uncorrectable (correct adjective unsuitable for the forum) mess that I am a bit "hyper," now, about the possiblity of having even a few (permanent) entries looking for something that isn't there ...The registry keys are located below HKCU\Sandbox [in the Windows Registry], and they are always empty and volatile. Volatile means they vaporize the next time the computer restarts.
This is a non-issue.However, the real reason for my question was to make sure there would be no lasting effects on the OS ... anything that could persist into the next re-boot. ...[snip]... Or is this a non-issue?
Let us assume for sake of discussion, that you have two physical hard drives. The first drive C: contains Windows with its registry, and system files, and C:\Windows system folder, and your applications, and data, and so on.
Further assume the second drive D: is empty and is only ever used by Sandboxie. It has a folder D:\Sandbox which you set as the container of all sandboxes.
Now, suppose you run a few programs and this causes Sandboxie to fill drive D: with a bunch of sandboxed stuff.
I will remind you that the whole point of Sandboxie is to keep sandboxed programs from touching your system. If Sandboxie is doing its job correctly, then drive C: remains untouched. This includes the Windows registry on drive C: -- it also remains untouched. [see Note at end]
Files that are added or changed by sandboxed programs, will be stored somewhere below D:\Sandbox\Device, and registry information in D:\Sandbox\Data.
I will say also, just for added clarity, that the Sandboxie registry is extremely different than the Windows registry, and Windows can't possibly mistake a Sandboxie registry file, as a part of the registry.
Now, suppose you restart your computer before you deleted the sandbox. Now your computer comes up and you have have a bunch of left-over files in your drive D:.
As far as drive C: is concerned, and that includes your registry, nothing has changed. Neither drive C, nor the registry in it, have been used any more, or become fragmented any more, than before the sandboxing.
* * *
The principle of the above scenario remains the same, even if you only have a single drive C:, and it contains the sandbox. You are just as safe, and your Windows installation (with its registry) remains un-messed-up the same in both cases.
* * *
Note: As for the few lines you quoted regarding the keys below HKCU\Sandbox. You will note I said the keys are created volatile. Volatile means they aren't written to disk. They are in-memory-only keys, so they can't fragment or corrupt your on-disk copy of the registry. They are deleted when you delete the sandbox. But if you don't delete the sandbox, they simply disappear when Windows shuts down.
* * *
I hope this wasn't too long, and that it made everything clear for you.
tzuk
Not too long at all, and beautifully written. Thanks for taking the time. This should be permanently preserved with the Sandboxie documentation, elsewhere on the site.
After reading your reply I have to give a compliment. Years ago, the general excuse for unintelligible software documentation was that "it was written by the programmers" who were too close to their programs to write from the user's point of view. More likely the only language they could handle was assembly. Anyway after using the program and reading your explanation, there clearly some folks who can do both! Credit where credit is due ...
After reading your reply I have to give a compliment. Years ago, the general excuse for unintelligible software documentation was that "it was written by the programmers" who were too close to their programs to write from the user's point of view. More likely the only language they could handle was assembly. Anyway after using the program and reading your explanation, there clearly some folks who can do both! Credit where credit is due ...
-
- Posts: 0
- Joined: Wed Dec 31, 1969 7:00 pm
Windows Shut-Down with Sandboxie running
I'd like to add my two-cents worth to Ron's comments - which I agree with completely. First, your explanation, Tzuk, should be retained and be included in your website wherever appropriate. It helps a lot. Second, a big thanks to Tzuk for a great program. The more I use and read in the Users Forum about Sandboxie, the more impressed with Sandboxie I become. I quickly became a registered user to help support Tzuk's efforts.....Slim Jim
Who is online
Users browsing this forum: No registered users and 1 guest