sodcalculator

10 Tech How-To

Fix Windows Sandbox Error 0xc0370106

Guide 10-57517 · Updated · Step by step

Windows Sandbox error 0xc0370106 appears when the feature fails to start, usually because of a corrupted system file, a pending Windows update, or a conflict with virtualization settings. The most reliable fix is to run the System File Checker and DISM tools in an elevated Command Prompt, then restart your PC; if that fails, check that virtualization is enabled in BIOS and that the required Windows features are turned on.

What This Error Means

Error 0xc0370106 is a Windows error code that typically indicates a problem with the Windows Sandbox executable or its underlying components. Windows Sandbox is a lightweight virtual machine that lets you run untrusted software in an isolated environment. When it fails to launch, you might see a dialog box with this code, or the Sandbox window may close immediately after opening.

The error is not unique to any specific Windows 10 version, but it is more commonly reported after a feature update or when third-party antivirus software interferes with virtualization. Understanding that this is a system-level failure, not a problem with your files, helps narrow down the troubleshooting steps.

Prerequisites for Windows Sandbox

Before attempting any fix, confirm your system meets the requirements. Windows Sandbox is only available on Windows 10 Pro, Enterprise, or Education editions—it is not included in the Home edition. Your CPU must support virtualization and have it enabled in the BIOS/UEFI. You also need at least 4 GB of RAM (8 GB is recommended) and about 1 GB of free disk space.

  • Check your Windows edition: Settings > System > About > Windows specifications.
  • Verify virtualization is enabled: open Task Manager > Performance > CPU, and look for “Virtualization: Enabled” in the bottom right.
  • Ensure you have at least 10 GB of free disk space for the Sandbox’s virtual hard disk.

If virtualization shows as disabled, you must enter your BIOS/UEFI (usually by pressing F2, Del, or Esc during boot) and enable Intel VT-x or AMD-V. The exact menu name varies by motherboard manufacturer.

Fix 1: Run System File Checker and DISM

Corrupted system files are the most common cause of 0xc0370106. The System File Checker (SFC) scans and repairs protected system files, while the Deployment Imaging Service and Management Tool (DISM) fixes the system image itself. Run both in order:

  1. Right-click the Start button and select “Command Prompt (Admin)” or “Windows PowerShell (Admin)”.
  2. Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. Wait for the scan to complete (this can take 10–20 minutes).
  3. After DISM finishes, type sfc /scannow and press Enter. This will also take several minutes.
  4. Restart your computer and try launching Windows Sandbox again.

If SFC finds files it cannot repair, run the DISM command again, then reboot and run SFC once more. This two-step process often resolves the error.

Fix 2: Re-enable Windows Sandbox and Virtual Machine Platform

Sometimes the required Windows features get partially disabled after an update. Re-enabling them forces Windows to reinstall the necessary components:

  1. Open Control Panel > Programs > Turn Windows features on or off.
  2. Find “Windows Sandbox” and uncheck it. Also uncheck “Virtual Machine Platform” and “Windows Hypervisor Platform” if they are present.
  3. Click OK and restart your computer.
  4. Go back to the same window and re-check all three options.
  5. Click OK and restart again.

This process removes and reinstalls the Sandbox’s core files, which can clear the error. Note that you may need to enable “Hyper-V” as well, but this is not always required—Windows Sandbox uses its own hypervisor.

Fix 3: Update Windows and Check for Pending Reboots

A pending Windows update can block the Sandbox from starting. The error often appears when the system is waiting for a reboot to finish installing updates. Go to Settings > Update & Security > Windows Update and click “Check for updates”. Install any pending updates, then restart. After the restart, try launching the Sandbox.

If updates are already installed, check if a restart is pending by opening Command Prompt and typing shutdown /a—if you see a message about an abort, no restart is pending. You can also check the Windows Update history for failed updates that might need manual retry.

Fix 4: Disable Conflicting Antivirus or Hyper-V

Third-party antivirus software with real-time protection can interfere with the Sandbox’s virtual machine. Temporarily disable your antivirus (not Windows Defender) and test the Sandbox. If it works, add an exception for the Sandbox process or switch to a different security suite.

Conversely, if you have Hyper-V enabled manually, it can conflict with the Sandbox. Windows Sandbox is designed to work alongside Hyper-V, but some configurations break this. Try disabling Hyper-V in Windows Features, restart, and test the Sandbox. If it works, you can re-enable Hyper-V later—the conflict is usually resolved after a clean restart.

Fix 5: Reset Windows Sandbox Data

If none of the above work, the Sandbox’s local state may be corrupted. Windows Sandbox does not have a built-in reset button, but you can delete its configuration files manually:

  1. Press Win + R, type %ProgramData%\Microsoft\Windows\Sandbox and press Enter.
  2. If the folder exists, delete its contents (you may need administrator permission).
  3. Also check %LocalAppData%\Packages\Microsoft.Windows.Sandbox* and delete those folders.
  4. Restart your PC and try again.

This clears any corrupted profile data without affecting your main system. It is a safe step because the Sandbox is ephemeral—it does not store persistent files.

Frequently Asked Questions

Can I use Windows Sandbox on Windows 10 Home? No. Windows Sandbox is exclusive to Pro, Enterprise, and Education editions. Home users can use a traditional virtual machine program or upgrade to Pro.

Will this error damage my files? No. The error only prevents the Sandbox from launching. Your personal files and installed programs are unaffected.

Why does the error appear after a Windows update? Feature updates can reset Windows feature settings or leave the system in a partially updated state. Re-enabling the features (Fix 2) and running DISM (Fix 1) usually resolves this.

Is it safe to run DISM and SFC? Yes. Both tools are built into Windows and only repair corrupted system files. They do not delete personal data.

What if I don’t have virtualization enabled in BIOS? You must enable it. Without hardware virtualization, Windows Sandbox cannot run. The BIOS setting is usually called “Intel Virtualization Technology” or “SVM Mode” for AMD processors.

Does the error mean my PC is too slow? Not necessarily. The error is a software issue, not a performance issue. However, if your PC has less than 4 GB of RAM, the Sandbox may fail even after fixing the error.

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 →