Release Notes
Sandboxie-Plus 1.18.3 is a maintenance release focused primarily on stability, usability, and compatibility improvements across SandMan, Start.exe, and the tracing subsystem.
The standalone SandMan trace monitor now provides a visible Cleanup Trace Log action, making it easier to clear accumulated trace data directly from the monitor.
Several issues in the SandMan user interface have been addressed. Changes made to the File Migration action dropdown are now correctly preserved when clicking Apply or OK while the editor still has keyboard focus. The File Panel and Browse Files views have also been improved when deleting files or folders: expanded directory states are retained, and the interface now restores the selection, keyboard focus, and scroll position to the nearest remaining item instead of unexpectedly resetting the view.
The trace logging subsystem received a number of stability and state-management fixes. Crashes and stale entries that could occur when clearing the Trace Log while both integrated and standalone trace views were open have been resolved. The standalone Trace Logging controls now correctly reflect the actual monitor state and no longer inadvertently disable logging when the monitor window is closed. When closing the standalone monitor while tracing remains active, Sandboxie now offers the choice to stop logging and clear the log, disable logging while retaining the existing log data, or leave logging running in the background.
Start.exe autorun handling has been made more robust. It now correctly handles oversized registry values, applies proper bounds to shortcut paths, supports paginated Startup directories, and dynamically allocates launch command lines instead of relying on fixed-size buffers. These changes improve reliability in systems with unusually large or complex autorun configurations.
This release also restores compatibility with Firefox 154 in Standard Isolation mode.
Finally, an initialization issue affecting sandboxed processes that already carry an AppContainer token has been fixed.
For a full list of changes please review the change log.
