New Update Sandboxie-Plus v1.17.0, v1.17.1, v1.17.2

bjm_

bjm_

Level 16
Thread author
Verified
Top Poster
Well-known
Forum Veteran
May 17, 2015
788
1
3,143
1,468
Release v1.17.0 / 5.72.0 Pre-release
Sandboxie-Plus 1.17.0 delivers significantly improved compatibility for UWP applications and App Compartment boxes, alongside usability enhancements and important stability fixes.

This version substantially improves the experimental UWP support across multiple layers of the architecture. A failure to mount the registry when launching UWP applications inside a sandbox has been resolved, restoring reliable startup behavior for modern Windows apps. Token handling has been refined to eliminate incompatibilities with the UWP security model, CopyTokenAttributes=y is now automatically applied to ensure correct attribute propagation required by UWP processes. To provide consistent behavior, SandboxieAllGroup=y is now the default, effectively standardizing the UseCreateToken=y code path, reducing dependency on undocumented kernel functions.

IPC handling in App Compartment type boxes has been further improved to increase reliability and compatibility with App Container based isolation. This fixes Microsoft Edge 144 crashes in Application Compartment Boxes. Furthermore, a new UseAlternateIpcNaming=y mode replaces the use of a separate NT object namespace by appending a suffix to sandboxed object names, instead of using an entirely separated object directory structure. This mode is restricted to App Compartment boxes, as for regular box types the object paths would otherwise be blocked by the driver.

User-facing transparency and workflow have been enhanced. Sandboxed windows now display the sandbox name directly in the border, and a new border mode ensures that the border is shown for every window belonging to sandboxed processes, not only the one currently in focus. Sandboxie service applications now include dedicated icons for clearer identification.

Isolation control has been extended, a new global option, ForceBoxDocs=y, allows administrators to force any program opening a file from a boxed path to start inside the corresponding sandbox, strengthening document-origin enforcement.

The SandMan UI can now export and import multiple sandboxes in a single operation, simplifying migration and backup procedures. Configuration handling has been improved as well, RenameSection processing now preserves original comments and section order, ensuring configuration files remain structurally clean and maintainable after modifications.

Several additional stability issues have been addressed. The CryptUnprotectData hook no longer returns an incorrect data description string. A handle leak in SbieDll.dll has been eliminated. Switching sandbox sorting in the user interface now behaves correctly. A crash in the file search bar triggered by performing multiple searches within a sandbox has also been resolved.

Overall, this release delivers materially improved UWP and App Compartment reliability, refined token handling semantics, updated Windows compatibility data, and a range of quality-of-life and stability enhancements.

For a full list of changes please review the change log.
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.17.0
https://www.wilderssecurity.com/threads/sandboxie-plus-v1-17-0.459243/
Click to expand...
Edit
Release v1.17.1 / 5.72.1 Latest
Sandboxie-Plus 1.17.1 fixed an incompatibility with windows 10 introduced in 1.17.0.
https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.17.1
https://www.wilderssecurity.com/threads/sandboxie-plus-v1-17-0-v1-17-1.459243/
Click to expand...
 
Last edited:
  • Like
  • +Reputation
Reactions: piquiteco, harlan4096, Gandalf_The_Grey and 1 other person
v1.17.0 / 5.72.0 is indeed published on GitHub as the “Latest” release (timestamped 2026-02-16). ([github.com](https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.17.0))

One thing to note for readers: on the official Sandboxie-Plus downloads page, the “Stable Builds” section is still listing 1.16.9 / 5.71.9, while “Preview Builds” points users to the GitHub release page. So 1.17.0 may effectively be treated as the newest (preview/newest) release, not necessarily the “stable channel” everyone should auto-update to. ([sandboxie-plus.com](https://sandboxie-plus.com/downloads/))

Security/compatibility-relevant highlights in this release
  • Major work on experimental UWP support and App Compartment boxes (including fixes for UWP startup/registry mounting and token-handling changes). ([github.com](https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.17.0))
  • Default behavior changes that can matter for compatibility and isolation behavior: “SandboxieAllGroup=y is now the default” and CopyTokenAttributes gets applied when using UseCreateToken to address UWP-related issues. ([github.com](https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.17.0))
  • App Compartment IPC improvements, including a fix mentioned for Microsoft Edge 144 crashes in App Compartment boxes, plus the new App-Compartment-only “UseAlternateIpcNaming=y” mode. ([github.com](https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.17.0))
  • New global option “ForceBoxDocs=y” (document-origin enforcement: if something opens a file from a boxed path, it can be forced into that box). This can be useful administratively, but should be tested carefully to avoid unexpected workflow impact. ([github.com](https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.17.0))
  • Stability fixes (e.g., handle leak in SbieDll.dll, CryptUnprotectData hook behavior, UI/search crashes). ([github.com](https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.17.0))

Practical update guidance (low-risk approach)
  • Back up your Sandboxie configuration (sandboxie.ini) and consider using the new multi-box export/import in SandMan as an extra safety net before changing versions. ([github.com](https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.17.0))
  • Prefer downloading from the official project locations (official downloads page or the project’s GitHub releases). Avoid third-party mirrors for security reasons. ([sandboxie-plus.com](https://sandboxie-plus.com/downloads/))
  • If the update fails, the release notes explicitly recommend uninstalling the prior version while keeping sandboxie.ini, then reinstalling the new build. ([github.com](https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.17.0))
  • Treat UWP/App Compartment as “still maturing”: validate your critical apps after upgrading (browser, password manager integration, office apps, etc.), especially if you depend on App Container/UWP behavior. ([github.com](https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.17.0))

Sources
 
  • Thanks
Reactions: bjm_
Release v1.17.2 / 5.72.2 Latest
https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.17.2
Sandboxie-Plus 1.17.1 fixed an incompatibility with windows 10 introduced in 1.17.0.
Sandboxie-Plus 1.17.2 fixes a couple GUI glitches introduced in 1.17.0, and adds improved box renaming with full alias support.
Click to expand...
DavidXanatos:
Well now with my very own cert I can run faster release cycles
And yea for such reasons i always set new releases in the updater as preview and only after a week or to set is as stable.
https://www.wilderssecurity.com/threads/sandboxie-plus-v1-17-0-v1-17-1-v1-17-2.459243/#post-3267774
Click to expand...
Add Rename Sandbox dialog and refine rename flow
https://github.com/sandboxie-plus/Sandboxie/pull/5231
 
Last edited:
  • +Reputation
  • Like
Reactions: Gandalf_The_Grey and piquiteco
~ Chrome update =
I'm still losing Home button, On startup and Extensions. I've lost track. What's current thinking regarding three Chrome Services? What's current thinking How-To update Chrome without needing to rebuild Chrome profile.
Note: red box
 
Last edited:

You may also like...