sodcalculator

10 Tech How-To

Fix sandbox issue in Windows 10 build v19h1

Guide 10-46574 · Updated · Step by step

If you are getting errors or a blank screen when launching Windows Sandbox on Windows 10 build 1903 (version 19H1), the fix usually involves enabling the required virtualization features in Windows Features, turning on virtualization in your BIOS/UEFI, and making sure your CPU supports it. This article walks through the exact steps, common causes, and what to do if the first fix doesn’t work.

What Is Windows Sandbox in 19H1?

Windows Sandbox is a lightweight desktop environment that runs a fresh, isolated instance of Windows inside your current Windows 10. It was introduced as a feature in Windows 10 version 1903 (build 18362), which is the release often called 19H1. The sandbox is meant for safely testing untrusted software, opening suspicious attachments, or browsing risky websites without affecting your main system. Every time you close the sandbox, everything inside it is permanently deleted.

Unlike a virtual machine (VM) like Hyper-V or VirtualBox, Windows Sandbox is designed to be quick to start and tightly integrated with the host OS. It uses the same kernel and reuses the host’s memory pages, so it boots in a few seconds and uses a relatively small amount of disk space. But this tight integration also means it has strict hardware and software requirements. If any of those are missing or misconfigured, the sandbox fails to start.

Why Does the Sandbox Fail on 19H1?

The most common reasons Windows Sandbox does not work on a 19H1 build are:

  • Virtualization is disabled in the BIOS/UEFI (the most frequent cause).
  • The required Windows features are not enabled: “Windows Sandbox” itself, “Virtual Machine Platform”, and “Windows Hypervisor Platform”.
  • The CPU does not support virtualization or second-level address translation (SLAT).
  • Another hypervisor (like VirtualBox or older Hyper-V) is interfering.
  • The Windows 10 edition is Home, which does not include Windows Sandbox.
  • The system is running an older build of 19H1 that has a known bug; updating to the latest cumulative update fixes it.

Let’s go through the fixes in order of likelihood.

Step-by-Step Fix for Windows Sandbox Issues

1. Check Your Windows Edition

Windows Sandbox is only available in Windows 10 Pro, Enterprise, or Education editions. If you are on Windows 10 Home, the feature will not appear in Windows Features, and you cannot enable it without upgrading your edition. To check your edition, press Win + R, type winver, and press Enter. The dialog shows the version and edition. If it says “Home”, you need to upgrade to Pro to use Sandbox.

2. Enable Required Windows Features

Press Win + R, type optionalfeatures, and press Enter to open the Windows Features dialog. Look for the following entries and make sure they are checked:

  • Windows Sandbox
  • Virtual Machine Platform
  • Windows Hypervisor Platform

If any are unchecked, check them and click OK. Windows will install the necessary components and ask you to restart. After restarting, try launching Windows Sandbox again.

3. Enable Virtualization in BIOS/UEFI

Even if the Windows features are on, the CPU must have virtualization enabled in the firmware. Restart your PC and enter the BIOS/UEFI (usually by pressing Del, F2, F10, or Esc during boot, depending on the manufacturer). Look for a setting named “Intel Virtualization Technology” (Intel VT-x), “AMD-V” (SVM Mode), or “Virtualization” and set it to Enabled. Save and exit. After booting back into Windows, verify that virtualization is active.

4. Verify Virtualization Is Active in Windows

Open Task Manager (Ctrl + Shift + Esc), go to the Performance tab, and select CPU. Under the graph, you should see “Virtualization: Enabled”. If it says “Disabled”, the BIOS setting is off or not properly applied. If it says “Enabled” but the sandbox still fails, proceed to the next step.

5. Check for Conflicting Hypervisors

If you have VirtualBox, VMware, or an older version of Hyper-V installed, they may be holding the hypervisor resources. Windows Sandbox requires the Windows Hypervisor Platform to be active. Sometimes, third-party virtualization software disables it. Try uninstalling or disabling those programs temporarily, then re-enable the Windows Hypervisor Platform feature and restart.

6. Update Windows 10

Microsoft has released several cumulative updates for 19H1 that fixed sandbox-related bugs. Go to Settings > Update & Security > Windows Update and install all pending updates. After updating, restart and test the sandbox again. If it still fails, consider moving to a newer Windows 10 version (like 20H1 or later) if possible, as 19H1 is no longer supported and may have unresolved issues.

Common Error Messages and Their Meanings

When the sandbox fails, you may see one of these errors. Here is what they mean and what to do:

  • “Windows Sandbox failed to start” – This generic message usually points to virtualization being off or a missing feature. Check the steps above.
  • “Windows Sandbox cannot be run because this PC does not support virtualization” – Your CPU does not support VT-x/AMD-V, or it is disabled in BIOS. Check the BIOS setting and CPU compatibility.
  • “Windows Sandbox failed to start, error 0x80070002” – This often indicates a missing file or component. Try re-enabling the Windows Sandbox feature (uncheck, restart, recheck, restart).
  • “Windows Sandbox failed to start, error 0xc0370106” – This is related to the Windows Hypervisor Platform. Re-enable that feature and restart.

If you see a different error code, search for it along with “Windows Sandbox” for specific guidance, but the general fixes above resolve most cases.

Hardware Requirements and Limitations

Windows Sandbox has specific hardware requirements that you should verify:

  • A 64-bit CPU with at least 2 cores (4 cores recommended).
  • Virtualization enabled in BIOS (VT-x or AMD-V).
  • Second Level Address Translation (SLAT) support (most modern CPUs have it).
  • At least 4 GB of RAM (8 GB or more recommended).
  • At least 1 GB of free disk space (SSD recommended for better performance).

If your CPU is older (pre-2010 or so) it may lack SLAT, which Windows Sandbox requires. You can check SLAT support with the command systeminfo in Command Prompt – look for “Hyper-V Requirements”. If it says “A hypervisor has been detected” or “Virtualization Enabled In Firmware: Yes”, you are good. If it says “No” for SLAT, your CPU is not supported.

Alternatives to Windows Sandbox

If you cannot get Windows Sandbox to work, there are other ways to test untrusted software:

  • Use a virtual machine – Install VirtualBox or VMware Workstation Player (both free for personal use) and run a Windows or Linux VM. This is more resource-intensive but works on any hardware that supports virtualization.
  • Use Windows Defender Application Guard – This is available in Windows 10 Pro/Enterprise and uses Hyper-V to isolate Edge browser sessions. It is not a full sandbox but is useful for browsing.
  • Use a third-party sandbox – Tools like Sandboxie (now open-source) can run applications in a sandbox without needing virtualization, though they are not as secure as a true VM.
  • Use a live USB – Boot from a Linux live USB to test software without touching your main OS, though Windows software will not run.

Each alternative has trade-offs in security, convenience, and system requirements. A VM is the most flexible, while Sandboxie is lighter but less isolated.

Frequently Asked Questions

Why is Windows Sandbox missing from Windows Features?

If you do not see “Windows Sandbox” in the Windows Features list, your edition is likely Windows 10 Home, which does not include it. You must upgrade to Pro, Enterprise, or Education. Alternatively, your build might be older than 18362; check your build with winver and update to at least 18362.

Can I enable Windows Sandbox on Windows 10 Home?

No, Microsoft restricts Windows Sandbox to Pro, Enterprise, and Education editions. There is no officially supported way to enable it on Home. You can use a third-party sandbox or a virtual machine instead.

Will Windows Sandbox work if I have Hyper-V enabled?

Yes, Windows Sandbox actually uses Hyper-V technology under the hood. If Hyper-V is enabled, that is fine. The problem is often the opposite: Hyper-V is disabled, and the Windows Hypervisor Platform is not enabled. Make sure both “Virtual Machine Platform” and “Windows Hypervisor Platform” are checked.

Does Windows Sandbox affect my main system performance?

While the sandbox is running, it uses CPU, RAM, and disk resources, but it is designed to be lightweight. When closed, it uses no resources. However, if your system has only 4 GB of RAM, running the sandbox may slow down your main system noticeably. Closing the sandbox frees all resources immediately.

Is Windows Sandbox safe to use for testing malware?

Windows Sandbox is isolated from the host, so malware inside it cannot affect your main system. However, it is not a full security boundary – sophisticated malware might try to escape the sandbox. For high-risk testing, use a dedicated VM with networking disabled and take snapshots.

Why does the sandbox close immediately after starting?

This can happen if the sandbox fails to initialize due to missing features or a corrupt component. Try re-enabling Windows Sandbox and the Virtual Machine Platform, then restart. Also, check that you have enough free disk space (at least 1 GB) and that your CPU supports SLAT.

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

The whole Tech How-To bed →