Windows 10 Sandbox is a lightweight virtual machine that lets you run untrusted software in an isolated desktop environment, but it can be missing if your system doesn’t meet the requirements or the feature isn’t enabled. This guide walks you through the likely causes and step-by-step fixes to get Sandbox working again on a supported Windows 10 Pro or Enterprise edition.
What Is Windows Sandbox and Why Would It Be Missing?
Windows Sandbox is a built-in feature introduced in Windows 10 version 1903 (May 2019 update). It creates a temporary, isolated desktop that is completely separate from your main system. When you close the Sandbox, everything inside it is permanently deleted, making it useful for testing suspicious files or installing software you don’t fully trust.
However, the feature is not available on every Windows 10 installation. If you don’t see “Windows Sandbox” in the Windows Features list, or if you get an error when trying to enable it, one of the following is usually the culprit:
- You’re running Windows 10 Home or a version older than 1903.
- Your CPU doesn’t support virtualization or it’s disabled in the BIOS/UEFI.
- Hyper-V is not enabled (Sandbox depends on it).
- Your system lacks sufficient RAM or disk space.
- Windows Sandbox is blocked by Group Policy or registry settings.
Check Your Windows Edition and Version
Windows Sandbox is only available on Windows 10 Pro, Enterprise, or Education editions. It is not included in Windows 10 Home. Also, your system must be running version 1903 or later. To check your edition and version:
- Press Win + R, type
winver, and press Enter. - Look at the “Version” line (e.g., 22H2) and the “Edition” line (e.g., Windows 10 Pro).
- If you have Home, you cannot enable Sandbox without upgrading to Pro or using a third-party virtual machine instead.
- If your version is older than 1903, run Windows Update to install the latest feature update.
Enable Required Windows Features
Windows Sandbox relies on two features: Virtual Machine Platform and Windows Hypervisor Platform. If either is disabled, Sandbox won’t appear in the optional features list. Here’s how to enable them:
- Open Control Panel → Programs → Turn Windows features on or off.
- Scroll down and check Windows Sandbox (if it’s listed).
- If it’s not listed, check Virtual Machine Platform and Windows Hypervisor Platform.
- Click OK and restart your PC when prompted.
If Windows Sandbox still doesn’t appear after enabling those, proceed to the next section.
Verify Virtualization Is Enabled in BIOS/UEFI
Windows Sandbox requires hardware virtualization (Intel VT-x or AMD-V). Even if your CPU supports it, the feature might be turned off in your BIOS/UEFI settings. To check if virtualization is active:
- Open Task Manager (Ctrl + Shift + Esc).
- Go to the Performance tab and select CPU.
- Look for “Virtualization: Enabled” or “Disabled” in the bottom-right corner.
If it says Disabled, restart your PC and enter BIOS/UEFI (usually by pressing Del, F2, or F10 during boot). Look for a setting named “Intel Virtualization Technology”, “SVM Mode” (AMD), or “Virtualization Extensions”. Enable it, save, and reboot. After that, re-check Task Manager and try enabling Windows Sandbox again.
Common Errors and Their Fixes
Even when everything is enabled, you might encounter specific error messages. Here are the most common ones and how to resolve them:
- “Windows Sandbox failed to start” – This often means a Windows feature is missing or virtualization is off. Re-check the previous steps and ensure your system meets the minimum requirements (4GB RAM, 1GB free disk space, and a 64-bit CPU with virtualization).
- “Windows Sandbox cannot be installed” – Usually appears when Hyper-V is not fully enabled. Run the following in an elevated PowerShell:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Alland restart. - “Windows Sandbox is not supported on this machine” – This typically means your CPU doesn’t have the required virtualization extensions (like SLAT) or they are disabled in BIOS. Check with a hardware diagnostic tool like Coreinfo (from Microsoft Sysinternals) to confirm.
Use Group Policy or Registry to Force Enable
In some cases, Windows Sandbox might be present but hidden by a Group Policy setting. If you’re on a work or school PC, the administrator may have disabled it. To check:
- Press Win + R, type
gpedit.msc, and press Enter (only available on Pro/Enterprise). - Navigate to Computer Configuration → Administrative Templates → Windows Components → Windows Sandbox.
- Double-click “Allow Windows Sandbox” and set it to Enabled.
- Click OK and restart.
If Group Policy is not available, you can try the registry: Go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows, create a key named Sandbox if it doesn’t exist, and add a DWORD value AllowSandbox with value 1. Then restart.
Alternatives If You Can’t Use Windows Sandbox
If you’ve tried everything and Sandbox still won’t work, you have other options for testing untrusted software:
- VirtualBox – Free, open-source virtualization software that works on Windows 10 Home. You can create a VM with any Windows or Linux ISO.
- VMware Workstation Player – Another free virtualization tool (for non-commercial use) that supports Windows and Linux guests.
- Hyper-V Manager – If you have Pro/Enterprise and Hyper-V is enabled, you can create a full VM manually, though it’s more complex than Sandbox.
- Third-party sandboxing apps – Tools like Sandboxie isolate programs without a full virtual machine, though they work differently and may not be as secure.
Frequently Asked Questions
Why is Windows Sandbox not showing in Windows Features?
This usually means your edition is Home, your version is below 1903, or virtualization is disabled. Check your edition and version first, then enable Virtual Machine Platform and Hyper-V. If it still doesn’t appear, verify virtualization is enabled in BIOS and that your CPU supports SLAT (Second Level Address Translation).
Can I enable Windows Sandbox on Windows 10 Home?
No. Windows Sandbox is only available on Pro, Enterprise, and Education editions. If you have Home, you would need to upgrade to Pro (which costs money) or use a third-party virtual machine like VirtualBox.
Does Windows Sandbox require Hyper-V?
Yes, Windows Sandbox depends on the Hyper-V hypervisor. When you enable Windows Sandbox, Windows automatically enables the required Hyper-V components, but you can also manually enable “Windows Hypervisor Platform” and “Virtual Machine Platform” to ensure compatibility.
Why do I get “Windows Sandbox failed to start” even after enabling it?
This error often means your system doesn’t meet the minimum requirements, virtualization is off, or a required feature is missing. Check that you have at least 4GB RAM (8GB recommended), 1GB free disk space, and that virtualization is enabled in Task Manager and BIOS. Also, ensure that “Virtual Machine Platform” is enabled.
Is Windows Sandbox safe to use?
Yes, it’s designed to be secure. Each session runs in a fresh, isolated environment that is destroyed when you close it. However, it’s not a full security boundary—malware could theoretically escape, so it’s still wise to avoid opening truly dangerous files.
Can I run Windows Sandbox on a laptop with an AMD processor?
Yes, as long as the CPU supports AMD-V (virtualization) and SLAT. Most modern AMD processors do. Just make sure virtualization is enabled in the BIOS/UEFI (often called SVM Mode).
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Set a Google Play Budget & Stop Accidental Purchases
- Destiny 2 Error Code Anteater: Fixes & Causes
- View Android Photos on Chromebook: Step-by-Step
- Fix Windows Could Not Prepare the Computer to Boot
- Windows 11 Security Settings: Best Config Guide
- Install Custom Recovery on Samsung Galaxy Trend