ForceProcess bug with alteration of path to notepad++.exe

[BUCKAROO]

Tested: Sandboxie/4.05.04 (Windows 8; 64-bit)

Notepad++ minimalist package
http://notepad-plus-plus.org/download/

Extract to "directory".

@
"%ProgramFiles%\Sandboxie\SbieIni.exe" set _ForceProcess Enabled y
"%ProgramFiles%\Sandboxie\SbieIni.exe" append _ForceProcess ForceProcess notepad++.exe
"%ProgramFiles%\Sandboxie\SbieIni.exe" append _ForceProcess ForceProcess _notepad++.exe
"%ProgramFiles%\Sandboxie\SbieIni.exe" append _ForceProcess ForceProcess __notepad++.exe
"%ProgramFiles%\Sandboxie\SbieIni.exe" append _ForceProcess ForceProcess notepadplusplus.exe
@

Open notepad++.exe (important)

Exit gracefully.

MOVE or RENAME "directory" to "_directory".

Open notepad++.exe

Load langs.xml failed!
Load config.xml failed!
Load stylers.xml failed!
ScintillaEditView::init SCINTILLA ERROR - Can not load the dynamic library

Temporary workaround
It will "Run Sandboxed".

Temporary fix
COPY notepad++.exe and assume any ForceProcess filename even keep it same.

It's fine (again) until I change the directory path where notepad++.exe resides from a previous successful Force(Process | Folder?) run.

[tzuk]

I think this could be an instance of the problem where you move an EXE file out of the sandbox.

Put an EXE file that did not yet execute in the sandbox folder.
Run the EXE file, it will start sandboxed.
Move it out of the sandbox.
Run the EXE file, it will still start sandboxed.
If the EXE is copied rather than moved, it will not start sandboxed.

Problem seem to be that Windows is reporting the old path location to Sandboxie. I don't know
if there is a solution to this problem, but I'm probably not going to look into that.

[BUCKAROO]

For the info, thanks. That'd explain why this bug actually survived across a re-install of Sandboxie. Wonder what it would take to make what Windows' subsystem forget... apart from a Windows restart.