[0.9.8b] Sandboxie.ini issues with %ProgramFiles% path from Classic to Plus

[isaak654]

Issues with Sandboxie.ini migration from Classic 5.53.0 to Plus 0.9.8b

1. The upgrade from Classic 5.53.0 to Plus 0.9.8b was an annoying experience, because Sandboxie Plus (soon after install) was autostarted automatically and created a new undesired Sandboxie.ini on Windows folder from scratch while I was having an existing Sandboxie.ini configuration on C:\Program Files\Sandboxie. Even after pasting it in C:\Program Files\Sandboxie-Plus, he created a new copy a second time on the Windows folder while it wasn't really needed.

For the record, this was the content of the Sandboxie.ini created unnecessarily the first time:

First sandboxie.ini copied on C:\Windows

#
# Sandboxie-Plus configuration file
#

[GlobalSettings]

[UserSettings_16D402E2]
SbieCtrl_AutoStartAgent=SandMan.exe

[DefaultBox]
...

While the second creation of Sandboxie.ini contained these lines:

Second sandboxie.ini copied on C:\Windows

#
# Sandboxie-Plus configuration file
#

[GlobalSettings]

[UserSettings_16D402E2]
SbieCtrl_AutoStartAgent=SandMan.exe
SbieCtrl_EnableAutoStart=y

[DefaultBox]
...

Expected behavior (1)

• Sandboxie Plus should offer an additional option to not create a new Sandboxie.ini automatically on the Windows folder when there is an existing Sandboxie.ini on C:\Program Files\Sandboxie or C:\Program Files\Sandboxie-Plus
• A checkbox to not start sandman after setup

---

2. Fortunately at the third attempt, Plus finally recognized the Sandboxie.ini that I had pasted on the C:\Program Files\Sandboxie-Plus folder. But at this point I noticed that my previous FileRootPath=D:\Sandbox\%USER%\%SANDBOX% line was replaced with a default value of FileRootPath (I don't recall what it was). I suppose that line was replaced automatically from one of the portable clean-up messages that apparently I wasn't able to skip, otherwise I can't explain it.

Expected behavior (2)

• Sandboxie Plus should offer a clear way to preserve a custom FileRootPath before those portable clean-up messages.

[DavidXanatos]

so should we have a checkbox to not start sandman after setup?

[isaak654]

so should we have a checkbox to not start sandman after setup?

Why not? But it may not be sufficient, I would also prefer another option to not have a new Sandboxie.ini generated automatically on the Windows folder when there is an existing Sandboxie.ini on the %ProgramFiles% folders used by Classic and Plus. I don't like to have an extra file when I don't need it.

Sandboxie Plus should offer a clear way to preserve a custom FileRootPath before those portable clean-up messages.

I would suggest to handle this one too. I just don't want my custom FileRootPath value to be overwritten so easily like it happened... or at least make the process more transparent.

[DavidXanatos]

I'll go with the checkbox, I dont liek checking default hardcoded locations as thay may be wrong and than people whom installed it to C:\MyTools\Sandboxie will still complain

about the FileRootPath no idea why that was overwriten, to the default value.