Sandboxie is a program that makes it possible to run programs under Windows in a protected environment. In this way, changes made by programs or web browsers are easy to undo, and there is no risk of affecting important parts of the operating system.
Sandboxie can be used on Windows 7 or higher and is now offered as open source, after Sophos stopped using it. Sandboxie is available in a classic and plus version. Internally they work the same, but the latter has a more modern Qt-built user interface. Version 1.0.5 is the first stable release in the 1.0 series and the release notes for this release can be found below.
Release v1.0.5 / 5.55.5
The 1.0.x line of builds is finally ready for a final release as version 1.0.5
The first major feature is Privacy Mode, here most of the PC is set to be treated like a Write[File/Key]Path meaning the sandbox locations are writable but the unsandboxed locations are not readable. The Hard disk appears empty except for C:\Windows and C:\Program Files and the registry only allows reading of the machine but not user root keys. This way sandboxed processes can work but can not access private user data.
To make this mode useful an other feature has been implemented called “Rule Specificity” it can be enabled independently but is always enabled in Privacy enhanced boxes. It allows to specify rules to override other rules, this is not based on specifying an order or priority, but instead by measuring how specific a rule is and always attributing the highest priority to the most specific rule.
Here the specificity is measures by the path length that matches the rule, except the last wildcard.
So for example the built in privacy rules plus a custom one
Here the rules are ordered by their specificity.
Also there is a new type Normal[File/Key/Ipc]Path which defines a default sandbox behavior for a path.
The next major feature is “App Compartment” mode “NoSecurityIsolation=y”, this is a new mode of operation which disables the token based security isolation, which brings the security down to the level of other sand boxing solutions, but by doing so greatly improves compatibility. For all use cases where the goal is only compartmentalization, running multiple instances, etc, but not hard core security this mode is preferable as it should avoid many typical sandboxie issues caused by processes running with a heavily restricted token.
In this mode file system and registry accesses are still being filtered to enforce the access rules, this filtering can be disabled with “NoSecurityFiltering=y”
To ensure this “unsecure” mode is at least as secure as the sandboxing offered by other sandboxing products, a new object access filter was added that can be enabled with “EnableObjectFiltering=y” in the global settings.
|5.55.5 / 1.0.5
|Windows 7, Windows 8, Windows 10, Windows 11