SandboxToys2 cannot detect any sandbox with a custom FileRootPath

[isaak654]

SandboxToys2 cannot detect any of my dozen sandboxes and it erroneously display DefaultBox as empty (when it isn't):

The only workaround for me is to remove FileRootPath=F:\Sandbox\%USER%\%SANDBOX% and let Sandboxie Plus create C:\Sandbox\User\DefaultBox by running any sandboxed program in it... in this case, there will be additional entries like Explore, Registry, Tools:

If I apply this workaround for the other sandboxes one by one, unfortunately SandboxToys2 will still continue to detect only DefaultBox as in the second image - maybe some extra effort is needed here, not sure ¯\_(ツ)_/¯

System configuration and additional notes:

• Windows 10 Pro x64 22H2
• I can reproduce this with any SandboxToys2 version (the latest release as much as the first release)
• I downgraded my Sandboxie Plus version from 1.9.6 to 1.8.4 and from 1.8.4 to 1.6.7, but it didn't make any difference
• My Sandboxie.ini is in C:\Program Files\Sandboxie-Plus

Sandboxie.ini configuration:

[GlobalSettings]
FileRootPath=F:\Sandbox\%USER%\%SANDBOX%
KeyRootPath=\REGISTRY\USER\Sandbox_%USER%_%SANDBOX%
IpcRootPath=\Sandbox\%USER%\%SANDBOX%\Session_%SESSION%
TraceBufferPages=2560
TemplateReject=7zipShellEx
TemplateReject=RTSS
TemplateReject=WindowsRasMan
TemplateReject=WindowsLive
DefaultBox=DefaultBox

Note: removing DefaultBox=DefaultBox doesn't make a difference.

[isaak654]

It doesn't work for me in the new v2.5.2.

EDIT: fixed by deleting a duplicate of Sandboxie.ini that I had missed.

[offhub]

Is it portable installation?
Is there another Sandboxie.ini file located under %windir%?

EDIT: Are you running it in a sandbox?

EDIT2: Can you use Process Monitor to see which sandbox directories are being accessed by AutoHotkey.exe or SandboxToys2.exe programs?

Ctrl+L > Process Name + is + AutoHotkey.exe + Include > Add
Ctrl+L > Process Name + is + SandboxToys2.exe + Include > Add

[isaak654]

Is there another Sandboxie.ini file located under %windir%?

I forgot to remove it after testing it, and now the issue is fixed for me too.
Thank you!