Windows Sandbox
Also called windows sandbox, wsb, containers disposable client vm
Disposable Windows VM built into Pro and related editions. Needs virtualization. It is not Sandboxie.
What you need to know
Windows Sandbox is a disposable Pro VM. It is not Sandboxie.
Enable the optional feature. Close the window and the VM is gone. Sandboxie is a different product. Home editions do not include this.
- What is it?
- Disposable Windows VM on Pro
- Same as Sandboxie?
- No. Sandboxie is third-party
- Needs Home?
- No. Home does not include it
What is Windows Sandbox?
Windows Sandbox is a disposable Windows VM. Each launch is clean. Closing it discards state. Sandboxie is a third-party isolation product with a different model.
If you have never used it
If you want a throwaway Windows desktop to run a suspicious exe, Windows Sandbox is an optional feature on Pro. Enable it in Windows Features. Closing the window wipes the VM. It is not Sandboxie, and it is not on Windows Home.
What is it used for?
A fresh Windows desktop. Host files are not there unless you copy them in.
Turn Windows features on or Enable-WindowsOptionalFeature Containers-DisposableClientVM. No Sandboxie installer.
Nothing persists after you close Sandbox ( aside from in-sandbox reboots on later Windows 11). That is the point.
Who is it for?
- Windows Pro users who want a disposable desktop
- People who were told to install Sandboxie instead
- Anyone on Home who will not find this feature
Current status
Windows Sandbox (2019) is a current disposable windows vm from Microsoft Corporation. The vendor still points Windows users at https://learn.microsoft.com/windows/security/application-security/application-isolation/windows-sandbox/.
How old is it?
Microsoft added Windows Sandbox in 2019 on Windows 10 Pro. It is newer than Sandboxie's long history. The inbox feature uses Microsoft's hypervisor, not the Sandboxie driver.
Versions
Major channels first. Exact build numbers are not all verified here.
System requirements
Values follow the publisher's public guidance. Workload still changes the real need.
Minimum
| Operating system | Windows 10 version 1903 or later, or Windows 11, Pro / Enterprise / Education, per Microsoft |
|---|---|
| RAM | 4 GB minimum, 8 GB recommended, per Microsoft Learn |
Resource profile
- CPU demand
- Follows what you open inside the app
- RAM demand
- Follows documents, tabs, or libraries
Installed processes
These executables belong to this product when it is installed.
| WindowsSandboxClient.exe | Main Windows executable |
|---|
Startup components
Sandbox starts only when you open Windows Sandbox. It is not a logon VM.
File locations
| Typical install | Windows optional feature Containers-DisposableClientVM |
|---|
Common problems
Installed Sandboxie by name mix-up
Sandboxie is third-party. Windows Sandbox is the inbox feature this article covers.
Feature missing on Home
Microsoft does not ship Sandbox on Home. Virtualization being on will not add the checkbox.
Getting unstuck
Enable Windows Sandbox in Windows Features, then restart
Learn lists 4 GB RAM minimum (8 GB recommended), two cores, and firmware virtualization.
Turn virtualization on in firmware if the box is grey
Same VT-x / AMD-V switch Hyper-V wants. Not a Sandboxie driver.
Copy the file into the sandbox. Do not expect host Desktop to appear
The VM is empty on purpose. That is isolation, not a failed install.
Alternatives
Sandboxie is a third-party isolator. A Hyper-V or VirtualBox VM persists until you delete it. WSL is Linux, not a Windows desktop sandbox.
Official help and downloads
Start with the vendor. Random exe sites are not a support channel.
| Download | learn.microsoft.com/windows/security/application-security/application-isolation/windows-sandbox/ Official installer or vendor page |
|---|---|
| Help | learn.microsoft.com/windows/security/application-security/application-isolation/windows-sandbox/ Vendor support |
| Official site | learn.microsoft.com/windows/security/application-security/application-isolation/windows-sandbox/ Start here, not a random exe host |
| Install Windows Sandbox | learn.microsoft.com/windows/security/application-security/application-isolation/windows-sandbox/windows-sandbox-install Optional feature plus virtualization |
Related hardware
Microsoft lists at least 4 GB RAM (8 GB recommended), two CPU cores, and virtualization in BIOS. An SSD is recommended.
Technical details
Technical details
Vendor version numbers change. This article does not pin a build.
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Windows Sandbox official site · Vendor product page
- Windows Sandbox help · Vendor support
- Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.