How to run notepad++ unsandboxed?

Mr.X

Active member
Staff member
notepad++.exe is not sandboxed; it never was/is.
FileRootPath=R:\\%SANDBOX% where R: is a RAM disk.

When I run X program in its red sandbox, a .ini file is created by it among other files in the RAM disk.
Next, I browse the program folder in the RAM disk.
When I right-click > Edit on such ini file, notepad++.exe is launched in a red sandbox.

How to run notepad++ unsandboxed?
 
I don't know if the FileRoot being a RAM disk changes something. I have used breakout processes to start something outside a sandbox. Sandboxie has added a feature to breakout documents, which I did not try, but it should apply in your case.

added breakout document functionality #2741
  • use a syntax like this 'BreakoutDocument=C:\path*.txt' to specify path and extension
  • Security Warning: do not use paths terminated with a wildcard like 'BreakoutDocument=C:\path*' as they will allow for execution of malicious scripts outside the sandbox!

So BreakoutDocument=C:\path*.ini might work.

This and "BreakoutProcess=" can be configured at Sandbox Options > Program Control > [Breakout Programs]
 
Of course, unsandboxed explorer. I've never sandboxed notepad++ or explorer. They don't have a dedicated sandbox or forced program.
 
Last edited:
Sandboxie 1.17.0 added:

added global option 'ForceBoxDocs=y', this forces all programs opening a file from a boxed path to the appropriate sandbox

Maybe ForceBoxDocs=y is set causing this, or ForceBoxDocs=n can be set to alter the behavior.
 
Trying again using BreakoutProcess= only.
Curiously, other file types, such as json or log files open in a unsandboxed notepad++ instance, as desired.
txt and ini files show this issue.
I haven't tried other file types though.
 
I had opened files from within a sandbox by browsing to the sandbox folder with an unsandboxed explorer and notepad before. As ForceBoxDocs=y came along I set it to avoid opening a file from within a sandbox outside by accident. I also had broken out a process that was started by something inside the sandbox. Well, none of that represents your use case and does not reflect or resolve the issues you have. In other words, I don't know how to be helpful.
 
Back
Top