How to Test New Programs Safely with Sandboxie-Plus

Run an unknown installer inside an isolated layer, inspect exactly what it wrote to disk, and discard all of it in one click without a full virtual machine.

Sandboxie-Plus runs a program inside an isolated layer on top of your real system: everything it writes lands in a sandbox folder, and deleting that folder removes every trace. It is a lighter option than a full virtual machine when all you want is to try one installer or open one questionable file.

Sandboxie versus a virtual machine

A virtual machine gives you a complete second computer, and costs a gigabyte of disk plus a setup session before you can use it. A sandbox starts instantly, shares your real desktop, and works on Windows editions that lack the built-in Hyper-V features. What it does not do is isolate the kernel or hide your hardware, so a driver-level exploit or a program that deliberately detects sandboxing can still behave badly. Use Sandboxie for software you want to try and probably throw away, and a virtual machine when you need a genuinely separate computer.

Install and create your first sandbox

1. Run the installer as administrator and keep the default program folder.
2. On first launch, accept the default sandbox or create a new one with a name you will recognise later.
3. Point the sandbox folder at a drive with room, since sandboxed data grows quickly.
4. Leave the compatibility template on its default preset and only change it if one specific program misbehaves.
5. Enable the option to start empty on launch if the sandbox is only ever used for one-off tests.

Run a program inside

1. Right-click the installer and choose the sandboxed run option.
2. Watch the window borders: sandboxed windows are marked so you always know where you are.
3. Install the program normally. Inside the sandbox it believes it modified the real system.
4. Note any prompt that demands administrator rights or a reboot; those are the signs a program wants the whole machine.
5. When you are done, right-click the sandbox and delete its contents.

The sandbox keeps its contents in a folder tree that mirrors the real one, so you can open it and see precisely which files were written, which registry keys were touched, and what the installer left behind. That single view teaches you more about bundled software than any review. If you decide to keep a program permanently, install it normally afterwards rather than copying files out of the sandbox.

Everyday use: forced programs and access rules

Once the workflow feels natural, make it automatic by adding a program to the forced list so it always starts sandboxed, then pin its shortcut. Browsers are the classic candidate, since a forced browser shields the rest of the system from whatever a page throws at it. Resource access rules let a sandboxed program see one specific folder, such as a downloads directory or a game save, which is usually what you want when testing something legitimate.

Limits before you install for real

Games with anti-cheat, drivers, VPN clients and anything that needs a kernel service will not run correctly in a sandbox, and some will simply refuse to start. Performance inside is close to native but not identical. Remember that a sandbox protects your file system, not your network: a program inside can still send data out, so cut network access when you genuinely do not trust the source. Review what it wrote, decide whether you need it at all, and only then install it on the host, keeping a restore point as a second line of defence.