Sandboxie is written for one operating system only, and that focus shapes everything about it. It hooks into the way Windows creates processes, stores settings and draws windows, which means its behaviour on a given PC depends a good deal on which version of Windows is installed, which edition, which processor architecture and which applications you intend to contain. This guide looks at Sandboxie on Windows 10 and Windows 11 from the user's chair: how it appears in the shell, how it marks sandboxed windows, how it copes with updates and Insider builds, how it treats the major browsers, and where Windows Defender, User Account Control and ARM laptops fit into the picture.
Supported Windows Versions at a Glance
The current builds target 64-bit Windows 10 and Windows 11, on either x64 or ARM64 processors. Since the 1.16 series, the project has used a modern compiler and Qt toolchain and no longer produces 32-bit builds, so a 32-bit installation of Windows is not a supported host. Hardware virtualisation is not required, which sets Sandboxie apart from Windows Sandbox and full virtual machines; it runs on machines where virtualisation is disabled in firmware or simply unavailable.
| Platform | Status | Notes |
|---|---|---|
| Windows 11, x64 | Main target | Plus and Classic installers available |
| Windows 10, x64 | Main target | Plus and Classic installers available |
| Windows 10 or 11, ARM64 | Supported in Plus | Available since Plus 1.5.0; a trial on the free tier |
| Windows 7 | Legacy | Support was dropped in 1.16.1, then restored by compatibility patches in 1.16.3 |
| Any 32-bit Windows | Not supported | No 32-bit builds since the 1.16 series |
Installation needs administrator rights, because the program installs a kernel driver. Compiled installers are published on the project's GitHub releases page; the download offered on this site is the archive of the master branch, which is source code for those who want to inspect or build it.
How Sandboxie Integrates with the Windows Shell
Much of the convenience of a Sandboxie Windows installation comes from the fact that it does not ask you to change how you launch programs. It adds itself to the places where Windows users already work.
The classic and Windows 11 context menus
Right-clicking a program or shortcut offers the option to run it sandboxed. On Windows 10 this lives in the traditional context menu. Windows 11 introduced a condensed menu that hides many third-party entries behind an extra click, and Plus supports that modern Windows 11 context menu directly, so the sandbox option is visible without digging. This support is part of the free tier.
The notification area
The Plus interface, SandMan, sits in the notification area at the right of the taskbar. From there you can open the main window, see which boxes are active and reach common actions. The 1.18.2 release added a search facility to the tray, which is helpful once you have accumulated more than a handful of boxes.
Command-line launching
For shortcuts, scripts and scheduled tasks, Start.exe launches programs into a named box. It can also terminate boxed programs, list their process identifiers and empty a sandbox.
Start.exe /box:DefaultBox notepad.exe
Start.exe /terminate_all
Start.exe /box:DefaultBox delete_sandbox_silentForcing programs into a box
If you would rather not remember to right-click, a program can be forced into a sandbox whenever it starts. A line such as ForceProcess=firefox.exe in a box's settings achieves this, with wildcards permitted. A forced folder takes precedence over a forced process, and the rule applies only to programs started outside a sandbox.
Telling Sandboxed Windows Apart
When the same browser can run both inside and outside a box, it matters a great deal that you can tell at a glance which copy you are looking at. Sandboxie offers several cues.
- Title marks. A sandboxed window shows
[#]marks around its title. With the BoxNameTitle setting, the name of the box can appear between those marks. - Coloured borders. The active sandboxed window is outlined with a coloured border, yellow for the default box. BorderColor lets you assign a different colour to each box.
- Administrator marker. Since 1.17.6, the window title includes "(Administrator)" when a sandboxed program is running with administrator rights.
- The process list. SandMan lists running processes grouped by box, which is the definitive record if a visual cue is ever ambiguous.
The 1.18.2 release refined the border further, adding outside-border modes and a BorderInsideMaximized option so that the frame remains visible on maximised windows. It also introduced BoxAliasDisplayMode for display aliases, useful if your box names are terse but you want friendlier labels on screen. On Windows 11, applications with custom title bars once provoked high CPU use in the Desktop Window Manager; that was fixed in 1.17.6, and 1.17.9 added a DisableCustomTitleOpt option for further control.
Give each box a distinct border colour. It costs nothing, and it is the quickest way to stop yourself typing a password into the wrong copy of a browser.
Sandboxie Windows Compatibility with Updates and Insider Builds
Because Sandboxie works at the level of the kernel and system calls, changes inside Windows can affect it. A cumulative update or, more often, an Insider Preview build can temporarily break the driver until the project adjusts. This is not a defect peculiar to any one release; it is the price of working so close to the operating system.
The project responds to these changes as part of its regular cadence. The 1.18.2 release, for example, explicitly addressed compatibility with Windows Insider builds. In practice this suggests a sensible approach for most people:
- On a production machine, prefer the stable release over pre-releases, and treat major Windows feature updates as a moment to check that boxes still start.
- On an Insider machine, expect occasional breakage and look for a Sandboxie update before assuming your configuration is at fault.
- If an update of Sandboxie itself fails, follow the advice repeated in every release note: uninstall the previous version while keeping the main configuration file, then install the new build.
The current stable release is Plus 1.18.8, paired with Classic 5.73.8. A pre-release, 1.19.0 with Classic 5.74.0, contains extensive hardening after an audit of the codebase, and the project asks testers to fall back to 1.18.8 if they meet regressions. That is useful guidance for anyone running Insider builds who might be tempted to stack two sets of pre-release software on one machine.
Windows Home Versus Pro
One of the more practical arguments for Sandboxie on Windows is that it is indifferent to edition. Windows Sandbox, Microsoft's own disposable environment, is built into the Pro, Enterprise and Education editions but not Home, and it needs hardware virtualisation. Home users therefore cannot use it at all.
Sandboxie has no such requirement. It runs on Home just as it runs on Pro, it needs no virtualisation hardware, and it can maintain many boxes at once, whereas Windows Sandbox provides a single instance whose clean desktop is destroyed when it closes. Sandboxie also uses the programs already installed on your machine rather than a fresh guest, and its boxes persist until you empty them.
Choosing between them on Pro
On a Pro machine you have both options, and they suit different tasks. Windows Sandbox is a clean, throwaway desktop with a stronger boundary because it is a lightweight virtual machine. Sandboxie is quicker and more convenient for containing a particular program you use every day. For work involving drivers, operating system testing or malware analysis, a full virtual machine remains the strongest choice, and researchers often run Sandboxie inside one.
Browsers, Electron Apps, UAC and Defender
Browsers are the most common reason people install Sandboxie, and the 1.18 series spent a good deal of effort on them. Close behind come Electron applications, questions about administrator rights, and the relationship with Microsoft Defender, all of which are treated below.
Edge, Chrome and other Chromium browsers
Microsoft Edge, Google Chrome and Brave are all built on Chromium. The 1.18.0 release made Chromium profile sharing reliable for these browsers and added support for the Chromium elevation service and DPAPI, which Chromium uses to protect stored data. Later, 1.18.5 fixed crashes affecting Chromium and Electron programs running in App Compartment boxes.
Where a Chromium-based program fails to start, Sandboxie may show message SBIE2189, which since 1.17.4 suggests adding a SpecialImage entry for the program. The suggestion takes this form, with the executable name substituted:
SpecialImage=chrome,program.exeFirefox
Firefox has its own architecture and therefore its own fixes. The 1.18.3 release added compatibility with Firefox 154 in Standard Isolation boxes, and the current stable release, 1.18.8, fixed video playback in Firefox on streaming sites. If you force Firefox into a box, as in the example above, these improvements apply automatically after updating.
Electron applications
Many popular Windows desktop programs are built on Electron, which bundles Chromium inside the application. Since 1.17.4, Sandboxie detects Electron programs automatically and applies suitable handling. If that detection causes a problem for a particular program, it can be turned off:
UseElectronDetection=nUser Account Control and administrator rights
Administrator rights are needed to install Sandboxie, since the driver must be loaded. Inside a box, the picture depends on box type. A Standard box runs programs with a heavily restricted token. A Security Hardened box goes further with DropAdminRights, so that sandboxed programs cannot act as administrators at all; this mode requires a supporter certificate. The "(Administrator)" title marker introduced in 1.17.6 makes it obvious when a boxed program holds administrator rights, and the 1.17.3 release fixed a bypass of the EditAdminOnly protection, which restricts configuration changes to administrators.
Coexisting with Windows Defender
Microsoft Defender and Sandboxie do different jobs, and you need both. Sandboxie is not antivirus: it contains programs but does not detect malicious ones. Defender scans files but does not isolate the programs you run.
Their relationship was not always comfortable. Before Plus 0.5.0 in December 2020, builds were unsigned and were falsely flagged by antivirus products, Defender included. That release was the first to be digitally signed, an effort funded by Patreon donors. Stable releases since then are signed, but pre-releases are sometimes unsigned, so a warning on a pre-release does not necessarily mean anything is wrong. Whatever you recover from a box should be scanned before you open it outside, because recovered files are copies that leave the sandbox.
Keep Defender switched on. A sandbox reduces what a program can change; it does not tell you whether that program was harmful in the first place.
Windows 7 and ARM Laptops
Running on Windows 7
Windows 7 occupies an awkward position. The project announced that support was dropped in 1.16.1, after moving to a modern toolchain, but compatibility patches in 1.16.3 restored it. Sandboxie still runs there, yet it should be regarded as legacy. Windows 10 and Windows 11 are where development and testing are concentrated, and a Windows 7 user should not expect every new feature to behave as it does on a current system.
ARM64 laptops
ARM-based Windows laptops are supported by the Plus edition through a dedicated ARM64 installer, available since version 1.5.0 in October 2022. Classic has no ARM64 build. On the free tier, ARM64 is offered as a trial; continued use requires a supporter certificate. Everything else about the experience, from the context menu to border colours, is the same as on x64.
Frequently Asked Questions
Does Sandboxie work on Windows 11?
Yes. Windows 11 is one of the two main targets, alongside Windows 10, and Plus supports the modern Windows 11 context menu as well as a Windows 11-style theme option.
Can I use Sandboxie on Windows 10 Home?
Yes. Unlike Windows Sandbox, which requires Pro, Enterprise or Education, Sandboxie runs on Home editions and does not need hardware virtualisation.
Why did Sandboxie stop working after a Windows update?
Windows updates and especially Insider builds can temporarily break the driver. Check for a newer Sandboxie release; if updating fails, uninstall while keeping the configuration file and reinstall.
Is there a 32-bit version for older PCs?
No. 32-bit builds were discontinued in the 1.16 series. Only 64-bit Windows on x64 or ARM64 is supported.
Will Windows Defender flag Sandboxie?
Stable builds have been digitally signed since Plus 0.5.0, which addressed earlier false positives. Some pre-releases are unsigned and may attract warnings.
What should I do if a Chromium app will not start in a box?
Look for message SBIE2189, which suggests adding a SpecialImage entry for the program, and make sure you are on a 1.18-series release with its Chromium fixes.
Conclusion
Sandboxie on Windows 10 and Windows 11 is a mature, well-integrated tool. It sits in the context menu and the notification area, marks sandboxed windows clearly with title marks and coloured borders, and handles the major browsers and Electron applications with fixes that have accumulated across the 1.17 and 1.18 series. It works equally on Home and Pro, needs no virtualisation hardware, and supports ARM64 laptops through the Plus edition. Those qualities make it a practical everyday companion rather than a specialist instrument.
Its closeness to the operating system is both its strength and its main caveat. Windows updates and Insider builds can disturb the driver until a new release arrives, Windows 7 is now legacy territory, and no sandbox replaces an antivirus product such as Defender. If you keep to stable releases on machines that matter, update Sandboxie promptly after major Windows changes, and scan anything you recover from a box, Sandboxie Windows integration will serve you quietly and reliably for a long time.