Windows Sandbox is missing or cannot start
What to do first
Windows Sandbox is missing or cannot start. The PC may run Home edition, have virtualization disabled, lack memory or disk space, or have Containers-DisposableClientVM disabled. Record the current state before changing it, use only the supported Windows path described below, and verify the same operation again after any required restart.
This is a general troubleshooting guide, not an announcement of a current outage.
Affected products and symptoms
- Product
- Windows Sandbox
- Versions and conditions
- Windows 11 (confirm the edition and hardware requirements for the feature)
- Error codes and identifiers
- 0x80070002
Symptoms
- Windows Sandbox is missing or cannot start.
- The same condition can persist after a retry or restart.
Causes and conditions
The PC may run Home edition, have virtualization disabled, lack memory or disk space, or have Containers-DisposableClientVM disabled.
Before you start
- Save open documents and allow time for a Windows restart if required.
- Run administrative actions only on a personally managed PC or with administrator approval.
- Save the diagnostic command output so the before and after states can be compared.
Precautions
- Do not bulk-delete registry entries, system folders, credentials, or storage metadata.
- Do not run unofficial scripts or unknown drivers with administrator rights.
Tools and official pages used in this guide
Check the official requirements, interface names, and limitations for this step.
Step-by-step instructions
In Settings > System > About, check that you are not using Home. Check virtualization under Task Manager > Performance > CPU. Do not use unofficial scripts to force the feature onto unsupported hardware.
Classify the failure: missing feature, enablement error, startup error or missing expected application. These lead respectively to requirements, Windows feature processing, virtualization/environment or application configuration. Save Windows build, physical/VM status and the complete message before repeating commands.
Files saved only inside Sandbox disappear when it closes. For a launch check, use disposable test files without sensitive information. If replacing a persistent work VM, plan how to retrieve required results before ending the session.
Confirm Pro, Enterprise, or Education edition, virtualization support, at least 4 GB RAM, at least 1 GB free storage, and at least two CPU cores.
Read each Hyper-V Requirements item and virtualization state. If any requirement is No or disabled, check the PC maker's model-specific UEFI requirements before retrying Windows feature installation.
For physical PCs, follow manufacturer virtualization instructions. A VM requires host-provided nested virtualization; users of managed VDI or cloud PCs may not control it. Review memory and space after saving work without deleting unfamiliar system files. Enable the feature once after confirming prerequisites.
systeminfo.exeOpen Turn Windows features on or off, enable Windows Sandbox, and restart Windows.
Right-click Start > Terminal (Admin) and run Enable-WindowsOptionalFeature. If RestartNeeded is True, save work and restart; do not judge Sandbox missing before that restart.
Use disposable, non-sensitive test content. Record ordinary launch versus .wsb launch. If ordinary launch works but the configuration fails, investigate that file before changing OS prerequisites. Preserve it and compare a minimal configuration, adding options individually. Treat application installation failure after desktop startup separately.
Enable-WindowsOptionalFeature -FeatureName Containers-DisposableClientVM -All -OnlineOfficial links for this step
- Install Windows Sandbox
Check the official requirements, interface names, and limitations for this step.
- Install Windows Sandbox
Restart Windows after adding the feature, search Start for Windows Sandbox, and open it. Confirm that a fresh desktop appears. Closing Sandbox discards files inside it, so decide how to handle any required output before beginning work.
Some Windows 11 versions lack inbox Store apps such as Notepad inside Sandbox. A different application list from the host does not mean startup failed when its desktop opens. Check the target application OS requirements and installation method separately.
Run Get-WindowsOptionalFeature -Online -FeatureName Containers-DisposableClientVM and repeat the original operation once under the same conditions. If it succeeds, verify again after a restart and record the setting that changed.
State=Enabled confirms the feature is active; Disabled means it is off. If enablement or a restart is pending, restart Windows and rerun the same check.
Retrieve necessary test results before closing because session work is not persistent. Close and relaunch, and retest after restart. Collect build, feature state, startup errors, physical/VM status and configuration-file use. Report desktop startup separately from successful use of the intended application.
Get-WindowsOptionalFeature -Online -FeatureName Containers-DisposableClientVM
Check the result
- The Sandbox desktop opens and can be launched again after closing
- The verification command reports the expected enabled, healthy, or connected state.
- The result remains correct after a Windows restart and no new matching critical event appears.
If the problem continues
- Save the complete startup error, Windows build and virtualization status
- If hardware requirements, organization policy, or server settings are responsible, ask the owner to make the change instead of bypassing it on the client.
Scope of this guide
Troubleshooting guide — Restore the feature so it starts, connects, or completes normally and passes the same verification after a Windows restart.
Frequently asked questions
Why is Sandbox absent on Windows Home?
Windows Sandbox is unsupported on Home. Confirm Pro, Enterprise, or Education and the hardware prerequisites.
Can Sandbox run inside another VM?
The outer host must expose nested virtualization, and cloud or managed VM providers may impose additional limits.
Should I change virtualization if only ordinary launch works?
If ordinary Sandbox opens, inspect the .wsb XML, extension, options and paths first. Configuration failure alone does not justify changing firmware virtualization.
Official sources and dates
Source publication or resolution date: Not specified. Sources checked: 2026-10-13. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.
Related troubleshooting guides
Windows errors and troubleshooting →
- Hyper-V is missing from Windows Features or cannot be enabled
- WSL 2 error 0x80370102 prevents a distribution from starting
- WSL 2 or Hyper-V cannot run inside a Hyper-V virtual machine
- PC will not boot after a CPU swap: check ASUS CPU support and required BIOS