Hello, I'm using Sandboxie 3.64 on Windows7 64-bit.

I couldn't get a nice summary in the title. When enabling forced folders and launching programs from the normal Windows start menu, if the program is in a forced folder, it changes the current working directory of Sandboxie Control and some abnormal behavior occurs unless that working directory is changed outside of the forced folder (I can do that by launching Notepad in the sandbox or restarting Sandboxie Control). The first issue would be Sandboxie being unable to mount the registry hive on subsequent instantiations of the sandbox, triggering a SBIE1241 [C0000120 / 22] error; the other issue is being able to totally keep the sandbox wiped clean, since cmd.exe will be launched through the Sandbox itself. The second one is particularly troublesome because it interferes with an automatic deletion of the sandbox contents.

I'm not sure I understand your problem report.

How can you tell that current working directory for Sandboxie Control has changed?

As for cmd.exe causing errors, perhaps cmd.exe itself is starting as a forced program.

Please list the specific forced programs and forced folders settings that you use.

Sorry, I was speculating that the current working directory for Sandboxie Control has changed, I don't know how to confirm or disprove it.

As for the sandbox, the ini configuration for the one that gives problems is as such:


This is a game that's not installed inside of the sandbox and installs start menu shortcuts, but I force everything under its folder to be sandboxed and direct access its own folder so that it cannot modify anything else (It's actually a mod for Half-Life 2, to be specific, but I tend to not trust it given that it does install customized versions of the game *.exe and *.dll files).

After having started the game using the normal Windows start menu, trying to delete the sandbox contents afterwords just ends up running the rmdir command inside of the sandbox rather than outside of it. With automatic deletion on, it just ends up in an endless cycle of trying to delete the contents of the sandbox after the cmd.exe process tries to run inside of it. I can only workaround it by restarting Sandboxie Control it seems..

This shows your forced settings for just one sandbox. We still don't know if some other sandbox has settings that cause "cmd" run in the sandbox. Perhaps you should quote your enire Sandboxie.ini.

Alright; I'll link my whole Sandboxie.ini here rather than making the thread rather long: http://dl.dropbox.com/u/13513277/Sandboxie.ini

The only other "force" setting I see is the one on the Dropbox folder. Try getting rid of this to see if it makes any difference.

Also, you can remove the two IPC settings in DefaultBox, they are built into Sandboxie. (But of course, it also doesn't matter if you don't bother to remove them.)