Windows Sandbox is a built-in lightweight virtual environment that lets you run untrusted apps safely, but it can fail to start for many reasons. If your problem is Windows Sandbox doesn’t work, this article explains common causes and gives step-by-step fixes so you can get it running again.
You’ll learn what system requirements and services Sandbox needs, how to enable missing features, diagnose conflicts with other virtualization software, fix BIOS and driver issues, and repair corrupted Windows components.
Key Takeaway
The most common fix is to ensure your PC meets the requirements (Windows 10 Pro/Enterprise/Education, build 1903+), enable virtualization in UEFI/BIOS, and turn on the required Windows features (Hyper-V and Windows Sandbox); if problems persist, repair system files and remove conflicting virtualization software.
Quick Fix Guide
| Reason for the Problem | Quick Solution |
|---|---|
| Unsupported Windows edition or build | Upgrade to Windows 10 Pro/Enterprise/Education and install the latest feature update (1903+). |
| Windows Sandbox feature not enabled | Enable Windows Sandbox in Control Panel > Turn Windows features on or off. |
| Hyper‑V or required services not enabled | Enable Hyper‑V and related features via Windows Features or PowerShell. |
| Virtualization disabled in BIOS/UEFI | Enable Intel VT-x / AMD‑V in your motherboard’s UEFI/BIOS. |
| CPU lacks virtualization or 64‑bit support | Use a CPU that supports VT‑x/AMD‑V and 64‑bit Windows. |
| Conflicting virtualization software | Uninstall or disable third‑party hypervisors (older VirtualBox/VMware) or configure them to work with Hyper‑V. |
| Not enough RAM/disk/CPU resources | Free up RAM and disk space (Sandbox needs ~1–2 GB RAM minimum and some free disk space). |
| Device Guard / Credential Guard active | Disable Device Guard/Credential Guard or adjust VBS policies that block Sandbox. |
| Corrupt system files or services | Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth; ensure vmcompute service is running. |
| Outdated BIOS/UEFI or drivers | Update BIOS/UEFI and chipset/virtualization-related drivers from the vendor. |
| Group Policy or enterprise restrictions | Remove policy that blocks virtualization features or contact IT to permit Sandbox. |
Detailed Fixes for “Windows Sandbox doesn’t work in Windows 10”
1) Unsupported Windows edition or build
Why this causes the problem
- Windows Sandbox is only available on Windows 10 Pro, Enterprise, or Education builds 1903 (May 2019 Update) and later. It is not included in Windows 10 Home or older builds.
Step-by-step solution
- Open Settings > System > About to see your edition (e.g., Windows 10 Home vs Pro).
- Run winver (Press Win + R, type winver, Enter) to check your build number.
- If you’re on Home, purchase/upgrade to Pro via Settings > Update & Security > Activation > Go to the Store or use a Pro product key.
- If build <1903, update Windows: Settings > Update & Security > Windows Update > Check for updates and install the latest feature update.
Notes
- Some OEM machines may ship with older images; ensure feature updates aren’t blocked by policies.
2) Windows Sandbox feature not enabled
Why this causes the problem
- Even with the right edition, Sandbox must be turned on as a Windows optional feature.
Step-by-step solution (GUI)
- Open Control Panel > Programs > Turn Windows features on or off.
- Check Windows Sandbox and click OK.
- Restart the PC when prompted.
Step-by-step solution (PowerShell)
- Open PowerShell as Administrator.
- Run:
- Enable (if using familiar feature name): Enable-WindowsOptionalFeature -Online -FeatureName “WindowsSandbox” -All
- If that returns an error, enable via Control Panel as above.
- Restart the PC.
Notes
- If the feature is missing entirely, confirm your Windows edition and build (see reason #1).
3) Hyper‑V or required services not enabled
Why this causes the problem
- Sandbox relies on Hyper‑V virtualization technology and related services (Hyper‑V platform & Host Compute Service).
Step-by-step solution
- Open Control Panel > Programs > Turn Windows features on or off.
- Ensure Hyper‑V, Virtual Machine Platform, and Windows Hypervisor Platform are checked (Hyper‑V must be enabled for Sandbox).
- Click OK and restart.
- Verify the Hyper‑V Host Compute Service (vmcompute) is running: open Services (services.msc), find Hyper-V Host Compute Service, and ensure its status is Running and startup type is Manual or Automatic.
PowerShell enable example
- Open PowerShell as Administrator and run:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All -All - Restart afterward.
Notes
- If enabling Hyper‑V causes conflicts with other virtualization software, see reason #6.
4) Virtualization disabled in BIOS/UEFI
Why this causes the problem
- Virtualization extensions (Intel VT‑x or AMD‑V) must be enabled at the firmware level for Hyper‑V/Sandbox to operate.
Step-by-step solution
- Reboot and enter firmware settings (commonly F2, Del, Esc, or a vendor key shown at boot).
- In UEFI/BIOS menus, look for Intel Virtualization Technology, VT-x, SVM Mode, or AMD Virtualization and set it to Enabled.
- Save changes and restart.
How to check from Windows
- Open Task Manager > Performance > CPU and look for Virtualization: Enabled, or run systeminfo.exe in Command Prompt and look for virtualization entries.
- Alternatively run msinfo32 and inspect System Summary > Virtualization-based security and Hyper-V – VM Monitor Mode Extensions.
Notes
- Some laptops require disabling Security > Virtualization-based Security or similar to enable normal virtualization — check vendor docs.
5) CPU lacks virtualization or 64‑bit support
Why this causes the problem
- Sandbox requires an x64 CPU with hardware virtualization support; older 32‑bit CPUs or some low‑end CPUs do not support VT‑x/AMD‑V.
Step-by-step solution
- Run msinfo32 and check System Type: it must be x64-based PC.
- In msinfo32, ensure Hyper-V – VM Monitor Mode Extensions shows Yes.
- If your CPU lacks the features, the only fix is to use hardware that meets the requirements.
Notes
- Consider upgrading hardware if Sandbox is required.
6) Conflicting virtualization software
Why this causes the problem
- Older versions of VirtualBox or VMware conflict with Hyper‑V, blocking Sandbox. Some 3rd-party tools install drivers that prevent Hyper‑V from starting.
Step-by-step solution
- If you have VirtualBox/VMware, either update to versions that support Hyper‑V or uninstall them:
- Settings > Apps > Apps & features, find the program, and Uninstall.
- Disable Hyper‑V (only if you need 3rd-party hypervisors and cannot update) with PowerShell:
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
Restart. - If you prefer to keep both, install recent VirtualBox (6.0+) or VMware Workstation 15.5.5+ that support Hyper‑V compatibility and enable Windows Hypervisor Platform.
Notes
- Uninstall cleanup may require removing leftover drivers — see vendor uninstall docs.
7) Memory, disk, or CPU resource constraints
Why this causes the problem
- Sandbox creates a lightweight VM that needs RAM and disk space; insufficient resources can prevent it from starting.
Step-by-step solution
- Ensure you have at least 4 GB RAM (8 GB recommended) and free disk space (several GB).
- Close heavy applications, free up RAM, and clear disk space via Settings > System > Storage > Free up space now.
- Reboot and try Sandbox again.
Notes
- Systems with very tight resources may never run Sandbox effectively.
8) Device Guard / Credential Guard / Virtualization‑based Security (VBS)
Why this causes the problem
- Device Guard, Credential Guard or other VBS features can reserve virtualization and prevent Sandbox or Hyper‑V from functioning as expected.
Step-by-step solution
- Run msinfo32 and check Device Guard / Virtualization-based security status.
- To disable VBS via Group Policy:
- Run gpedit.msc > Computer Configuration > Administrative Templates > System > Device Guard.
- Set Turn On Virtualization Based Security to Disabled or adjust settings to not block Sandbox.
- Or use Registry / MDM settings if in enterprise — contact IT if managed.
- Reboot and test.
Notes
- Disabling Device Guard may reduce certain protections; consult IT policy.
9) Corrupt system files or Windows components
Why this causes the problem
- Damaged Windows components, corrupted system files, or broken Hyper‑V services can stop Sandbox from starting.
Step-by-step solution
- Open Command Prompt as Administrator.
- Run:
- sfc /scannow
- After SFC completes, run DISM /Online /Cleanup-Image /RestoreHealth
- Reboot and re-enable Windows Sandbox if needed via Control Panel > Turn Windows features on or off.
- Check the Hyper-V Host Compute Service (vmcompute) in services.msc is running.
Notes
- DISM connects to Windows Update sources; ensure internet access.
10) Outdated BIOS/UEFI or drivers
Why this causes the problem
- Firmware or chipset drivers with bugs can break virtualization support or stability needed by Sandbox.
Step-by-step solution
- Identify motherboard or system model: Settings > System > About, or run wmic baseboard get product,Manufacturer,version,serialnumber.
- Visit the manufacturer’s support site and download the latest BIOS/UEFI and chipset drivers.
- Follow vendor instructions to flash/update the BIOS (careful: follow vendor guidance — a failed flash can brick the system).
- Update CPUs/ICH drivers via Device Manager or vendor packages.
- Reboot and test Sandbox.
Notes
- Always back up important data before BIOS updates.
11) Group Policy, registry, or enterprise restrictions
Why this causes the problem
- Organizational policies or registry edits can block optional features, Hyper‑V, or Sandbox explicitly.
Step-by-step solution
- If the PC is domain-joined or managed, check with your IT admin whether Sandbox is allowed.
- Check local policy: gpedit.msc > Computer Configuration > Administrative Templates > Windows Components for restrictions.
- Inspect registry keys (be cautious):
- Open regedit and search for policies under HKLM\SOFTWARE\Policies\Microsoft\Windows\ that mention Sandbox or Hyper‑V and remove them only if you understand the implications.
- If unsure, contact IT or restore policy defaults with:
secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose
(This resets security policy — use with care.)
Notes
- Never change enterprise policies without authorization.
Troubleshooting checklist and tips
- Run msinfo32 first: it gives a concise view of Virtualization support, Windows version, and Device Guard status.
- Use Event Viewer (Event Viewer > Applications and Services Logs > Microsoft > Windows > WindowsSandbox or Hyper-V-Worker) to view Sandbox-related errors.
- If Sandbox fails with a specific error code, search the code in Event Viewer; many issues map to clear causes (e.g., hypervisor launch failures).
- If you reinstall Windows components often, consider creating a restore point before making major changes.
- For enterprise-managed devices, Sandbox may be intentionally blocked — check with IT before troubleshooting.
FAQ
Can I run Windows Sandbox on Windows 10 Home?
No — Windows Sandbox is not available on Windows 10 Home. You must upgrade to Pro, Enterprise, or Education.
How do I reset or clear a Windows Sandbox instance?
Simply close the Sandbox window; each session is disposable and all changes are discarded. If Sandbox won’t start, reinstall the feature via Turn Windows features on or off and reboot.
Are there log files to diagnose Sandbox startup failures?
Yes — use Event Viewer: check Applications and Services Logs > Microsoft > Windows > WindowsSandbox and Hyper‑V related logs under Microsoft > Windows > Hyper-V-Worker and Hyper-V-Hypervisor.
Does disabling Hyper‑V allow VirtualBox/VMware to work instead?
Yes: to run older VirtualBox/VMware versions that don’t support Hyper‑V, disable Hyper‑V via PowerShell: Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All and reboot, or uninstall/upgrade the conflicting hypervisor to a Hyper‑V–compatible version.
Is Windows Sandbox safe to use for malware testing?
Sandbox isolates the guest session from the host and discards state on close, but it should not replace dedicated isolated lab environments for high-risk malware. Do not test highly sophisticated malware expecting perfect containment.
Conclusion
Most issues where Windows Sandbox doesn’t work stem from unmet requirements, disabled virtualization, or conflicts with other hypervisors. Start by verifying your Windows edition and build, enable virtualization in UEFI/BIOS, turn on Hyper‑V and the Sandbox feature, and then repair system files or update firmware if problems persist. With these checks and fixes you should be able to get Sandbox running reliably.
