I have noticed in certain situations, Sandboxie will give me permission issues. I cannot reproduce it 100% of the time but it does happen quite often. I notice if I "move" a file into a newly created sandbox, sometimes it acts like it only partially moves. This is hard to explain... I mean I can see the newly moved file inside the sandbox but it acts as if it is not a win32 executable because it gives me that error when I try running it and the icon is Vista's generic exe icon. When I try to delete it, it tells me that I don't have permission to do that. I have to delete the entire Sandbox and start over to get rid of the file. I notice that this only happens when I "move" a file and not when I copy.

To reproduce:

I have "setup" folders that I copy into every newly created sandbox. They are:

drive\D\Temp

I block all net access and disable all recovery options. You can probably use any exe file but if you can't reproduce the problem then I suggest downloading a Big Fish game. (That's when it usually happens... with a game)

1) Create a sandbox and run the browser
2) Copy the "setup" folders into the sandbox
3) Open Temp folder and "move" a game into it (must move, not copy)
4) Try running the game and it should give you an error
5) Now try deleting the game and you should get another error message about permissions

This is not a problem when you copy the file, only when you move it.

Your "setup" folders (i.e. where you copy stuff from), is that on the same drive as your sandbox? Or is it a different drive?

Sandboxie is installed on drive "D". The sandboxes are kept on drive "E" and the "setup" folders are kept inside the main "Sandbox" folder. (The one that holds all the sandboxes) Its path is E:\Sandbox\00 Setup

To help clear some things up about the setup folders... As you already know, you can install programs two different ways into a sandbox. One, right-mouse click on the exe and select "Run Sandboxed". Or copy (in this case) the game into the sandbox and run from within. I usually prefer using the ladder method.

Also as you know, Sandboxie does not create the drive folders by default (when you first create a sandbox) unless you use the first method mentioned above. Since I prefer the second, this is the reason why I have and use those "setup" folders. So I created a folder called "drive". Then I opened that folder and created another one called "D". Then opened that folder and created a final one called "Temp". So these 3 folders: drive\D\Temp are kept inside the "00 setup" folder and when I create a new sandbox I copy and paste them into the newly created sandbox after opening and closing the browser. That way all the main folders and registry hives are created. Then I can move a game into the Temp folder and run it from within the sandbox. I hope that made things clearer and not more confusing.

Curious, is there a way to have Sandboxie create the main folders and reg hives by default when a sandbox is created? If not, would you consider this as valuable option to possibly add in a future version?

I'm not sure that you've answered my question. You say that moving (but not copying) files into the sandbox causes permission issues. I'm asking is the move happening across different drives?

Oh... alright, now I understand. Yes, it does happen when "moving" (not copying) across drives but it also happens when "moving" files on the same partition the sandboxes are located on, too.

I see. I think the problem is that permissions on folders in the sandbox were not set as "inheritable". I fixed that in version 3.39.11, please let me know if it resolves the problem.

One thing to keep in mind, if possible, delete your sandbox folders (all the way up to E:\SANDBOX), so they can be re-created with the fixed permissions.

You were right and the newer version fixed the problem. Thanks.