Windows Sandbox: the session that dies clean
Windows Sandbox — an optional component on Pro, Enterprise and Education editions, with virtualization enabled in the firmware — boots a throwaway copy of Windows in seconds. Nothing persists: installed programs, downloaded files, registry edits and any malware all evaporate when you close the window, because the whole session runs on a differencing layer that is discarded on exit. It is the perfect cage for a sketchy installer, a one-off conversion tool or a file you do not trust — with one real limitation: whatever you legitimately liked dies with the session unless you copy it out beforehand.
Where the VM wins — and where its junk accumulates
A Hyper-V or VirtualBox machine is the right tool the moment an experiment needs to survive the day: snapshots, a different OS, a shared test environment, reboots across updates. Persistence is the whole point, and persistence is also the bill. Sandbox leaves nearly nothing behind; the VM quietly amasses a small archive of everything you never cleaned up.
- A VM's virtual disk grows monotonically and never shrinks on its own — a quick test setup settles at 40–80 GB of host disk without trying
- Every kept checkpoint or snapshot freezes a link in a differencing chain that must all stay alive
- ISO images, exported machines and abandoned VM folders pile up in default locations years after the experiment ended
- Hypervisor host services take a small bite of RAM and CPU at every boot, whether or not you have run a VM this month
- Windows Sandbox caches its base image once and discards the session layer at close — the footprint stays flat by design
The working rule — and the cleanup after either
The rule we use on test machines: Sandbox for anything disposable, a VM for anything you will boot twice. When the testing season ends, delete abandoned machines from the hypervisor's own manager first, then remove the files — deleting only the files leaves the manager's catalog broken. The ISOs, installers and export archives your experiments downloaded are ordinary junk, and a cleanup sweep like Kleaner PRO clears them along with the rest of the download dust; the VMs themselves you still remove by hand.
Questions and Answers
Is Windows Sandbox better than a virtual machine?
For throwaway tests, yes — it boots in seconds and destroys everything on close. For anything that must persist — snapshots, another OS, repeated reboots — only the VM can do that.
Does Windows Sandbox leave files on my PC?
Almost none: the base image is cached once and reused, and the session layer is discarded completely when you close the window. Only files you deliberately copy out of the sandbox survive.
Know what is included before you buy.
The one-time 30-minute trial covers core tools. PRO-labelled features stay locked until a paid license is activated.
Read next
Write to us: [email protected]