Don't copy files from local drive, but allow the folder

[Wolfspirit]

Hi,

I'd like to use Sandboxie to test software which writes to C:\Users\username...
I've installed the software on my computer, but I'd like sandboxie to have it's own environment.
Is there a way I can allow access to C:\Users\Wolfspirit\AppData\AppName but prevent Sandboxie from using the local settings which are stored there?
So that the App thinks there is an empty directory?
If I deny this folder, then it can't even read. But I wan't sandboxie to use the sandboxed folder for all files!

That allows also to use apps that can't live with "deny" access, but will prevent them to not see local data.

Is that possible?
Maybe a feature request if not yet possible?!

Thank you!
('m sorry if that was asked already. Have searched the forum, but wasn't able to find it)

[Guest10]

The only time that I do something like this is if I install a Firefox beta version inside of a sandbox.
To keep the sandboxed install from seeing the install that is outside of the sandbox, I temporarily rename 2 folders that are outside of the sandbox - the Firefox Program Files folder and the Firefox profile folder.
That way the sandboxed install does not see that the program is installed outside of the sandbox, and it does a full install with a completely new Firefox profile folder, inside the sandbox.
Then, go back and restore the names of the folders that are outside of the sandbox.

[Wolfspirit]

Thanks for your response.
That doesn't help for me.

I'd like to use it, to check how an application looks on a clean computer.
I know that the Application stores everything in the AppData Directory of the user.
I created the Folder in AppData and started the application within the sandbox.
Usually the Program creates every file on its own, but there it copys the local settings over.

The settings are based on many files and I can't create all of them manually.
And I'd like to remove the folders in there to have a "clean" copy again.

[Guest10]

I'd like to use it, to check how an application looks on a clean computer.
I know that the Application stores everything in the AppData Directory of the user.

So, can't you temporarily rename the folder that it uses under AppData (the unsandboxed folder), and then install it in a sandbox?
It won't see the AppData sub-folder that it would normally look for, because it was renamed.

I created the Folder in AppData and started the application within the sandbox.

An AppData sub-folder that's outside the sandbox? I thought that folder was already there, from the unsandboxed program install.

Maybe you don't know how to install the program in a sandbox.
Besides renaming the folder(s) outside of the sandbox as mentioned above:

To install a program in a sandbox:
Create the sandbox that you will use, if you haven't already done so.
If you've been experimenting with it, right-click on the Sandboxie Control tray icon, and choose "Delete Contents" for that sandbox.
In Windows Explorer, right-click the installer for the program you want to install > click on "Run Sandboxed" > Choose the sandbox > OK

[Wolfspirit]

Hey there,
Thank you for your replay again.

I know how to install an application within the sandbox.
I'm a developer and member of an opensource software and want to try my application without it getting any settings from the unboxed appdata folder.
The Users sometimes have problems with the settings and I want to retry their bug reports clean settings.

That's my file structure:

Local:
AppData
- SomeApp
-- Folder...
-- Folder1...
--- File 1...

I sure can rename, but I'm using that application unsandboxed nearly all the time.
I don't want to close it. It'd mean I've to close it, rename it, install it...etc.

I can't start the app sandboxed with clean settings, while already using that application unsandboxed.
If you could set "use local files, but sandbox only" for a specific folder, I'd set the SomeApp folder and remove everything in there within the sandbox.
The Program will then create clean settings in there.

Sorry if I wasn't clear.

[mizzmona]

Maybe uninstall your application, from inside the intended sandbox...

(being sure that nothing real is uninstalled, so do check settings prior to doing that)...

then maybe not allow access to the unboxed appdata folders by that sandbox...

and then install your application inside that sandbox, for testing...?

Not saying it would work. Only, maybe, that maybe it's worth a shot.

[Guest10]

The only way that I can think of that might come close to this is to do the rename operation as I described, one time, and install the program in a sandbox so that it contains all default settings.

Then, you can make a copy of the sandbox and store that copy in another folder.
You can copy the sandbox back to where it was; use it with the default settings that it contains; and then "Delete Contents" to get rid of it - as many times as you like.

Maybe make a .cmd file that will "Delete Contents" of the sandbox and also copy the saved sandbox back where it belongs.
Delete Sandbox
"C:\Program Files\Sandboxie\Start.exe" /box:MySandbox delete_sandbox