New Update Sandboxie-Plus v1.18.4 / 5.73.4 Latest

[bjm_]

Release v1.18.4 / 5.73.4 Latest
This release focuses primarily on refinements to SandMan’s INI editor, shell notification handling, and several smaller reliability fixes.

The SandMan INI editor has received a substantial auto-completion overhaul. Completion candidates are now ranked using context-aware semantic matching and fuzzy matching, while metadata is synchronized independently for each editor instance. Refreshes are also deferred during rapid typing or deletion to reduce unnecessary updates and improve responsiveness.

The completion popup itself has also been refined. Candidate tooltips no longer retain stale information while editing, Template and TemplateReject entries now show only the relevant setting-name information, and large description tooltips have been adjusted to avoid jumping unnecessarily between sides or obscuring completion candidates.

Shell notification handling has also been updated. UseShellNotifyIconProxy remains enabled by default when OpenWinClass=* is configured, preserving the behavior required by these sandboxes, while other sandboxed processes now use direct routing by default unless proxying is explicitly enabled. To make troubleshooting this behavior easier, low-noise SbieTrace logging has been added for Shell_NotifyIconW calls. The trace records the notification message, icon identity using either NIF_GUID/GUID or HWND/uID, and whether the effective route was direct or through the proxy.

A problem with shortcuts created from SandMan’s File Panel has been fixed. Previously, the “Create Shortcut” action did not set a working directory, causing sandboxed applications to inherit SandMan’s current directory. Programs relying on relative paths could consequently fail to locate their data files. Shortcuts created through the File Panel now receive the appropriate working directory.

This release additionally fixes an incorrect return type in SbieSvc and corrects archive path cleaning behavior.

Sandboxie Plus 1.18.4 is primarily a maintenance and usability release, with the most visible improvements affecting INI editing and completion behavior while also tightening shell notification routing and addressing several smaller issues reported since the previous release.

For a full list of changes please review the change log.

You can support the project through donations, any help will be greatly appreciated.
If you have issues with an update installation, just uninstall the previous version keeping the sandboxie.ini and reinstall the new build.

https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.18.4
https://forum.xanasoft.com/threads/sandboxie-plus-v1-18-4.13130/
https://www.wilderssecurity.com/threads/sandboxie-plus-v1-18-4.460665/
https://www.patreon.com/DavidXanatos/posts/sandboxie-plus-4-168782469

 

[Bot]

I cannot independently verify Sandboxie Plus v1.18.4 / 5.73.4 from this post alone. Confirm the tag, release assets, and changelog on the official GitHub repository before downloading or installing.

Official links from the announcement

• Release Release v1.18.4 / 5.73.4 · sandboxie-plus/Sandboxie
• CHANGELOG.md entry

If you proceed with an update

• Obtain the installer only from the official GitHub releases page.
• Keep a backup of sandboxie.ini.
• If the update installer has issues, uninstall the previous version while retaining sandboxie.ini, then install the new build, as stated in the announcement.

The post describes INI editor auto-completion and tooltip changes, adjusted Shell_NotifyIcon routing (including UseShellNotifyIconProxy when OpenWinClass=*), added SbieTrace logging for those calls, a File Panel shortcut working-directory fix, plus smaller SbieSvc and archive path corrections.

I cannot test these changes. Treat the GitHub changelog as the authoritative list.

 

[lokamoka820]

I have a question about Sandboxie. I haven't used it before, but I understand the concept. How do I update the browser when it runs inside Sandboxie? Updates usually happen in the background while it's open, but when I close Sandboxie, everything is wiped away. Do I need to open the browser outside of Sandboxie to update it, and then reopen it inside Sandboxie for future use?

 

[bjm_]

I have a question about Sandboxie. I haven't used it before, but I understand the concept. How do I update the browser when it runs inside Sandboxie? Updates usually happen in the background while it's open, but when I close Sandboxie, everything is wiped away. Do I need to open the browser outside of Sandboxie to update it, and then reopen it inside Sandboxie for future use?

fwiw ~ I maintain Brave|Chrome|Edge installed on host. I run their Services at Manual. I'll update browser outside of it's discrete sandbox so that the update installs permanently on the real system.

I maintain Chromium based browser Services at Manual. Before calling browser update. I'll turn on Enable Sandboxed Elevation Service and turn off Enable all security enhancements. After confirming browser profile survives update and before calling browser discrete sandbox. I'll turn off Enable Sandboxed Elevation Service and turn on Enable all security enhancements.