Better see the illustration, not sure how to phrase it

[Requester123]

This request is in regard to "patches" (programs that alter other specific programs or files).
Sometimes those patching program also carry secondary code (trojans, worms, etc) and my idea was to use sandboxie as some sort of fence, where the sandboxed program could only affect certain files (defined by the user) and not "wonder off" and affect the rest of the system. Those chosen files could retain alterations.

I hope I make myself understood, please see the rudimentary illustration (click to expand)

[tzuk]

The point of Sandboxie is isolation, so conceptually, your request has little to do with Sandboxie.

Nevertheless Sandboxie is a versatile tool and you could probably use the File Access settings to fine-tune the paths that do not get isolated, which is pretty much what you wanted.

[Requester123]

Thank you, will have a look.

[Requester123]

Thank you for your answer Tzuk.

An analogy of my idea could be the following:
Imagine you hire a plumber to fix your kitchen sink, but while you weren't looking he goes to the bedroom and steals your jewellery from the top drawer.
What I was looking was to keep him in the kitchen and give him access only to the sink (which it was what he was supposed to do) and not even to anywhere else in that small kitchen (not even the cookie jar, because I know he is a naughty boy!)

Just trying to get myself understood, I felt I wasn't entirely successful the first time.
Cheers.

[MitchE323]

Nevertheless Sandboxie is a versatile tool and you could probably use the File Access settings to fine-tune the paths that do not get isolated, which is pretty much what you wanted.

ForceProcess=Plumber.exe
ClosedFilePath=Plumber.exe,C:\Bedroom\Dresser\Top Drawer
ClosedFilePath=Plumber.exe,C:\Kitchen\Cookie Jar
OpenFilePath=Plumber.exe,C:\Kitchen\Sink