New version lists all files not just those modified

[kimski]

I am now using version 3.72 and I have to say I like the previous version better. The previous version only listed files that I had edited. The new version now lists all my folders and files. That makes it nearly impossible to see which ones have been modified. So, I have to recover all the old files (last opened before I even installed Sandboxie) just to get them out of the Sandbox. Why are they showing up now? How do I get them out of the box? The advantage of showing only the edited files helps us see if someone is trying to hack us.

Also what does "cut" do? All it does for me is grey out the filename. I can't find any instructions in the manual on this.

Lastly, how can I delete a file from the box that is older than my recovered version? I don't want to be confused by it.

Thanks,

[Guest10]

I am now using version 3.72 and I have to say I like the previous version better. The previous version only listed files that I had edited. The new version now lists all my folders and files.

I don't really understand this. I'm not aware of anything that has changed. If you use a sandboxed program, such as a sandboxed Windows Explorer, it shows you the files that are in the sandbox as well as those that are outside of the sandbox, but in the corresponding folder.
That can be confusing, and make you think that all of the files you see are in the sandbox.

Also what does "cut" do? All it does for me is grey out the filename.

It's the same as Windows "Cut", which would typically be used before a Paste. So the file is marked to be deleted, as soon as it's Pasted someplace else (moved, in other words).

Lastly, how can I delete a file from the box that is older than my recovered version? I don't want to be confused by it.

Because of the confusion I mentioned above, about viewing the contents of a sandbox using a sandboxed Windows Explorer, I think the best way to delete a file that's in a sandbox is to use an UN-sandboxed Windows Explorer to navigate to and delete the file.
That way there's no confusion as to what files are actually inside of the sandbox.

[kimski]

Thanks for the info.

In my previous version (not sure which version, installed about 8 mo ago), the only files I would see in Sandbox were the ones that were edited. Now every single file is listed. So before if in "temp" I edited "test.txt" then that's all I'd see under "temp" in sandbox. Now I see "test.txt" as well as all the other files in the "temp" folder. It makes it hard to see now which files have been updated. That is the change I am referring to.

As for deleting files, you mention using a un-sandboxed windows explorer to delete file. I have 2 questions here. First, when you say "windows explorer" do you mean file explorer? If I delete the file there then the file would be deleted entirely. That's not what you meant is it? I don't want to delete the file. I just don't want it to show up in Sandbox. Now the only way to get things out of Sandbox is to recover them. 99% of the time the file hasn't changed so I just recover and overwrite. It seems like a lot of unnecessary work.

[Guest10]

In my previous version (not sure which version, installed about 8 mo ago), the only files I would see in Sandbox were the ones that were edited. Now every single file is listed. So before if in "temp" I edited "test.txt" then that's all I'd see under "temp" in sandbox. Now I see "test.txt" as well as all the other files in the "temp" folder.

That's the way it has always been, with all versions of Sandboxie.
When you use a sandboxed program to view a folder, you see the contents of that folder in the sandbox and also the contents of the same folder that's outside of the sandbox. Really, you see all folders and files that are outside of the sandbox as well as files that are inside of the sandbox you are using.

The exception is that if a file in the sandbox has the exact same name as a file in the same folder outside of the sandbox, then the file that's inside the sandbox will be the one that's shown. The file inside the sandbox will 'hide' the file with the same name that's outside of the sandbox, regardless of whether it's a newer or older copy of the file.

Files that exist only in the corresponding folder that's outside of the sandbox will also be shown when you use a sandboxed program. That's necessary if a sandboxed program is going to read files that are outside of the sandbox, as well as files that are in the same folder inside of the sandbox.
It's why using a sandboxed Windows Explorer to view folder contents can become confusing.

If you use an unsandboxed Windows Explorer to view the contents of a sandbox folder, you will see only the files that are actually inside of the sandbox.

As for deleting files, you mention using a un-sandboxed windows explorer to delete file. I have 2 questions here. First, when you say "windows explorer" do you mean file explorer? If I delete the file there then the file would be deleted entirely. That's not what you meant is it? I don't want to delete the file. I just don't want it to show up in Sandbox. rk.

I was referring to the Windows Explorer that is a part of Windows. Yes, you could call it a file explorer.
If you use an unsandboxed Windows Explorer it will delete a file for good, inside or outside of the sandbox.

If you use a sandboxed Windows Explorer to delete a file that you see in a folder, and that file is one that exists inside of the sandbox and there is also a file by the exact same name in the folder that's outside of the sandbox, then deleting the file inside of the sandbox will only mark that file as deleted (inside of the sandbox). The file will be seen by the sandboxed Windows Explorer as a deleted file, and that will 'hide' the file that's outside of the sandbox. It will appear to the sandboxed program as if that file has been deleted, both from inside and outside of the sandbox.

Experiment:
Create a folder C:\Temp outside of the sandbox and put a small .txt file as well as a few other files in it.
Use a sandboxed Notepad to open the file and modify and save it, but don't restore the file or delete the sandbox contents.
Close Notepad and use a sandboxed Windows Explorer to view the C:\Temp folder and open the .txt file to see that it is the one you modified. Close Notepad again and use the sandboxed Windows Explorer to delete the file.
It will appear that there is no .txt file in C:\Temp because the deleted copy of that file is 'hiding' the copy of the file that's outside of the sandbox.
The other files (that exist only outside of the sandbox) will still be seen by sandboxed Windows Explorer.
Close Explorer.

Use an unsandboxed Windows Explorer to view the C:\Temp folder contents. The unsandboxed copy of the .txt file is still there.
Now view the sandbox contents, still using the unsandboxed Explorer, in the corresponding folder inside of the sandbox:
C:\Sandbox\(user)\(sandbox)\drive\C\Temp\xxxx.txt
You will see that the copy of the .txt file inside of the sandbox is a 0 byte file, and has a "Created "file date that Windows knows is illegal: right-click the file > Properties > Created: Friday, May 23, 1986
That date is illegal for a file because it pre-dates DOS and Windows. Setting the file to 0 bytes and giving it that date is what allows the deleted file inside of the sandbox to 'hide' the file with the same name that's in the folder outside of the sandbox.