please set prioritize sandboxie so that their data is stored in designated sandboxes

[yeqwe]

Is your feature request related to a problem or use case?

I set D:\program run in the sandboxie A, but there have alot of temp data, and i want delete it, but it also delete my useful date,so the sandboxie A become more than 30Gb

Describe the solution you'd like

please set prioritize sandboxie so that their data is stored in designated sandboxes

For instance, I enforce that my D:\program （there have alot of software）directory opens within Sandbox A to ensure everything runing in the sandboxie.
However, to prevent data loss for the D:\program\steam directory when Sandbox A is cleared, I want to assign Steam to operate within Sandbox B.

Describe alternatives you've considered

No response

[yeqwe]

the alternatives is Set up each software catalog in each sandbox, and also set up for each software installed in the future

[LetItGlow]

Fixing a sandbox like this is no easy task, especially when its set to cover a whole folder like "C:\ProgramFiles", which can have tons and tons of external files. Every program is writing to another location, which isn't really the scope of SBie, imo.
Sbie is more like: "I want those 3 programs of 100 installed sandboxed".
Unless the recovery is perfect, you create a parallel ecosystem. Oh well, let me help you with Steam.

SandboxiePlus has a feature called "Breakout Programs", you could actually use.

1. Slap your Steam Folder/Exe in the "Breakout Programs" of "Sandbox A".
2. Remove the enforcement of Steam in "Sandbox A".
3. Set the Steam Folder/Exe as a "Forced Programs" of "Sandbox B".

This has some caveats as well, as Steam will now run in "Sandbox B", with no data, as they remain in "Sandbox A".
If your Steamgames were installed INSIDE the "Sandbox A" (why?), you will have to jump through a couple of hoops.

1. Do the stuff i wrote above with the "breakout".
2. Start Steam in "Sandbox B", so it can create it's path structure inside C:\Sandbox\ .
3. Close Steam completely.
4. Move the contents of the sandboxed Steam's filesystem from "Sandbox A" to the proper location of "Sandbox B".

Any savegames/screenshots inside have to be synced or moved by hand (unless Recovery kicked in and moved them for you).
Sandbox B should now have your entire Lib and should start syncing your saves.

If you ever reinstall, maybe having "writethrough" is the better option and saves a ton of space, because Sandboxie doesn't have to copy Gigabytes of data from another drive to C:\ .
Some people don't know, you can install Games on another drive inside Steam.
Steam can remain on C:\ , but the games install on D:\ (which is... ultimately handy) - even Network Drives work!

Here is a quick guide for that:

1. Install Steam on your real system's C:\ .
2. Create a folder called "SteamLibrary" on another drive with enough space, we will use R:\ as example.
3. Make a sandbox and set Steam forced to run inside that box.
4. Go to "Resource Access - Files" settings of that box and set "R:\SteamLibrary\*" as "Open for All".
5. Start Steam (sandboxed) and login.
6. In Steam, create a new library on R:\ , this will writethrough to real disk and make it valid.
7. When installing games, Steam will ask where to install. Always pick the Library on R:\ as target.

Here are some optional settings for a couple use cases:

• (optional) Set the library folder "R:\SteamLibrary" forced into the same Sandbox as well, if you need that somehow.
• (use case specific) When covering a whole folder like OP did, set the Steam Programfolder as Breakout.
• (use case specific) Set the "R:\SteamLibrary" as breakout. Steam will run sandboxed, but not Games. (for some reason some games lag badly when ran inside SBiE)
• (data retaining) Set "C:\Users%username%\Pictures\Steam\*" as "Resource Access - Files" (OpenPipePath), it will directly write screenshots to real disk now, so nothing is lost when deleting the contents of the sandbox (except for Steam itself lol).
• (use case specific) Set "C:\Program Files (x86)\Steam\*" as "Resource Access - Files" (OpenPipePath). This will always use the real client from the disk and can update it, if needed.

When deleting the contents of this "Steam Sandbox", it will only delete the copies of the Steam Client, savegames and couple other temp files. Games itself will not be affected and remain on disk. And redownloading Gigabytes of data is a hassle.
This is very handy, when you have to format your PC, as other disks remain as they are.

Maybe I could make templates for that, when I have time.

[yeqwe]

i hnow what your mean, and I set it up the same option like you . i store steam game in real disk. but when i clean sandboxie A , it will ask me for login steam, so i want set priority run folder. If it's harder to do, I'll close the issue. thank you very much

[DavidXanatos]

I do not understand this feature request,
you can use multiple sandboxes you can make them have different root folders you can use snapshots to only delete new data in a box on cleanup.
Please clarify what the requested feature is supposed to do and how it is supposed to work.