Sandboxie Plus Download and First-Run Setup

Sandboxie Plus takes only a few minutes to install, yet the choices made in those minutes shape how comfortable the program feels for months afterwards. Picking the correct build for your processor, granting the installer the rights it needs, and spending a quarter of an hour on sensible first settings will save a good deal of puzzlement later. This guide follows the whole journey, from choosing the right Sandboxie Plus download to running your first sandboxed browser, configuring updates, applying a supporter certificate and upgrading cleanly when a new release appears.

The emphasis throughout is on the Plus edition, with its SandMan manager. Sandboxie Classic shares the same engine and is installed in a similar way, but its interface is no longer developed and new features reach it only through manual configuration, so most new users are better served by Plus.

Choosing the Right Sandboxie Plus Download

Sandboxie Plus is published as two installers, and the right one depends entirely on the processor in your PC. Most Windows computers, whether they carry Intel or AMD chips, use the x64 architecture. A smaller number of machines, typically thin laptops built around Qualcomm processors, run Windows on ARM64. Installing the wrong build simply will not work, because the kernel driver must match the architecture of the system it loads into.

If you are unsure which processor you have, open Settings, go to System and then About, and read the line labelled "System type". It will state either an x64-based processor or an ARM-based one. There is no longer a 32-bit build to consider: the 1.16 series discontinued 32-bit builds, so a 32-bit installation of Windows cannot run current releases.

What your PC needs

The requirements are modest. Windows 10 or Windows 11 in a 64-bit edition is the main target; Windows 7 remains a legacy platform at best. You will need administrator rights, because the installer places a kernel driver on the system. Hardware virtualisation is not required, which sets Sandboxie apart from Windows Sandbox and full virtual machines, and Home editions of Windows are perfectly suitable. Disk space matters only gradually: the installer is small, but each sandbox grows as the programs inside it write data.

Where the Installer Comes From

Compiled installers are published on the project's GitHub releases page, attached to each tagged release. Look for the release marked Latest, which at present is Plus 1.18.8, released on 17 October 2026 alongside Classic 5.73.8. A newer pre-release, 1.19.0, also exists; it is intended for testing and the developer has asked anyone who meets regressions to return to 1.18.8. For a first installation, the stable release is the sensible choice.

It is worth being clear about one point that confuses many visitors. The download offered on this website is the GitHub archive of the project's master branch, which is source code. It is useful for reading the code or for developers who intend to build the program, but it contains no installer and cannot be run as it stands. To install Sandboxie, obtain the signed installer from the releases page.

Since Plus 0.5.0, released in December 2020, stable builds have been digitally signed, a step funded by Patreon supporters after earlier unsigned builds were wrongly flagged by antivirus software, Microsoft Defender among them. If a security product complains about a stable installer, check the signature in the file's properties; a valid signature from the project is reassuring. Pre-releases are sometimes unsigned, so warnings about them are less surprising.

Running the Installer

Double-clicking the installer brings up the Windows User Account Control prompt almost at once. This is expected: installing a driver and a service requires administrator rights, and the installer cannot proceed without your consent. Confirm the prompt, and the setup wizard opens.

The wizard begins by presenting the licence terms. These deserve a moment's attention rather than a reflexive click, because Plus uses a custom licence rather than the GPL. Personal, non-commercial use is free, while commercial or educational use requires a Business certificate. Once you accept, the wizard for this Sandboxie Plus download proposes an installation folder, by default C:\Program Files\Sandboxie-Plus\. There is rarely a good reason to change it, and leaving it alone keeps paths consistent with documentation and forum advice.

The installer then copies its files, registers SbieSvc.exe as a Windows service and loads the SbieDrv.sys driver. This part takes only a short while on most machines. If you are upgrading from an earlier build rather than installing fresh, the installer stops the running components first; closing any sandboxed programs beforehand makes this smoother. When copying is complete, the wizard offers to launch SandMan, and accepting that offer is the natural next move.

If the installation fails at the driver stage, the usual suspects are a security product interfering with driver loading, a pending Windows update or an Insider build of Windows with which the current driver is not yet compatible. Windows updates and Insider builds can temporarily break the driver, and the project often ships compatibility fixes for them; release 1.18.2, for instance, included compatibility work for Windows Insider builds.

First Launch of SandMan

SandMan opens to a list of sandboxes, and on a new installation there is exactly one: DefaultBox. It is a Standard Isolation box, the free default type, and it is immediately ready for use. A support reminder may appear on the free tier; it is a request rather than a restriction on the basic features.

The quickest way to see Sandboxie at work is to right-click DefaultBox, choose to run a program, and start something harmless such as Notepad. When the window opens, notice two signs that it is sandboxed: the title bar is wrapped in [#] marks, and a coloured border, yellow for the default box, outlines the window when it is active. In SandMan, the process appears beneath DefaultBox. Save a small text file from the sandboxed Notepad to the desktop and then look at your real desktop; the file is not there, because Sandboxie redirected the write into the box using copy-on-write. That brief experiment says more about how the program behaves than any description.

The box's contents live by default under C:\Sandbox\, inside a folder named after your user account and then the box. Deleting the box contents from SandMan discards everything written there, returning the box to a clean state.

Theme, dark mode and the vintage look

SandMan's appearance can be adjusted to taste in its options. A dark mode suits anyone who works with dark system themes or spends long evenings at the screen. A Windows 11-style theme brings the interface closer to the look of the current operating system. For those who used Sandboxie in its shareware days, Vintage View reproduces the layout of the old Sandboxie Control, which can make the transition from Classic feel more familiar. None of these choices affects how sandboxing works; they are purely about comfort.

Setting Up a First Browser Box

Running a web browser inside a sandbox is the classic use of Sandboxie, and it remains one of the most worthwhile. While you could use DefaultBox, a dedicated box makes the purpose clearer and lets you tailor its settings without affecting anything else.

From SandMan's menu, create a new box and give it a descriptive name, such as BrowserBox. Keep the box type at Standard Isolation unless you hold a certificate and want a Privacy Enhanced box, in which sandboxed programs cannot read your user data and instead see empty folders. Once the box exists, open its options to make it genuinely useful.

Forcing the browser into the box is the most valuable setting. A forced program always starts inside its sandbox when launched from outside one, so you cannot forget to sandbox it. Adding a recovery folder means that files you download inside the box prompt you to recover them to the real Downloads folder. In the configuration file, the result looks something like this:

[BrowserBox]
ForceProcess=firefox.exe
RecoverFolder=C:\Users\YourName\Downloads

Giving the box its own border colour through the BorderColor setting helps distinguish it at a glance from DefaultBox's yellow outline. With these settings in place, opening the browser from its usual shortcut starts it sandboxed, and a download triggers an Immediate Recovery prompt. Remember that a recovered file leaves the box and lands on your real system, so scan anything unfamiliar before you recover and open it.

Recent releases have improved browser handling noticeably. Release 1.18.0 delivered reliable Chromium profile sharing for Chrome, Edge and Brave, and 1.18.8 fixed Firefox video playback on streaming sites, so a sandboxed browser now behaves much as an ordinary one does.

Update Checks and Supporter Certificates

SandMan can check for new releases and tell you when one is available. The relevant controls sit under Options, in Global Settings, on the Support & Updates page. Leaving update checks enabled is wise, because releases regularly carry security fixes; 1.17.3 in March 2026, for example, fixed CVE-2026-32603 and a bypass of the EditAdminOnly protection. If you prefer to update deliberately, treat the notification as a prompt to read the release notes, then install at a moment that suits you; stable builds are the sound default.

Applying a supporter certificate

A supporter certificate enables the box types and features beyond the free tier: Privacy Enhanced, Security Hardened and App Compartment boxes, RAM disk boxes, USB drive sandboxing, ARM64 beyond the trial and a year of Sandboxie-Live support. Encryption, proxy injection and DNS filtering additionally require the Advanced Feature Pack, which the Contributor and Eternal certificates include.

Applying a certificate is simple. Go to Options, then Global Settings, and open the Support & Updates page. Paste the certificate text, or enter the serial key you received, into the field provided and apply it. A serial key needs an internet connection so that SandMan can fetch the certificate. Once accepted, the additional box types appear when you create or edit a box.

Several certificate types exist. Home and Personal suit individuals, the Family Pack covers a whole family even across households, Business is required for commercial or educational use with one PC per certificate, and Eternal has no expiry. A Personal certificate brings a year of updates, and builds released before it expires keep working afterwards.

Upgrading Later Without Losing Your Settings

Most upgrades are uneventful: download the new installer, run it, and it replaces the old components while keeping your boxes and settings. Close sandboxed programs first, and let the installer stop and restart the service and driver.

Occasionally an update fails, perhaps because a component would not stop or because a driver change did not apply cleanly. Every set of release notes gives the same remedy. Uninstall the previous version, and when the uninstaller asks, choose to keep the configuration file. Then restart if prompted and install the new build. Because the configuration file holds every box definition, forced program, recovery folder and certificate, keeping it means your carefully built setup returns intact after the reinstall.

• Before upgrading, make a copy of the main configuration file somewhere safe; it is a small text file, and having a backup costs nothing.
• Read the release notes for each version between yours and the new one, so that changed behaviour does not catch you out.
• If a pre-release causes problems, return to the stable Latest build using the same uninstall-and-keep-configuration method.

Frequently Asked Questions

Conclusion

Installing Sandboxie Plus is quick, but a careful start makes a real difference. Choosing the build that matches your processor, fetching the signed installer from the releases page rather than the source archive, and checking its checksum take only a minute or two. The installer itself asks little of you beyond administrator consent and acceptance of the licence, and SandMan greets you with DefaultBox ready to use, so the program can be put to work almost immediately.

The real value comes in the half-hour afterwards: a dedicated browser box with the browser forced into it, a recovery folder for downloads, a theme that suits your eyes and update checks left switched on. Add a certificate if you need the advanced box types, keep a copy of the configuration file, and remember the uninstall-and-keep-settings remedy for the rare failed update. With those habits in place, your Sandboxie Plus download becomes a dependable everyday tool rather than an experiment.