Windows Sandbox Error 0x80070002 – Quick Fixes That Work

I know this error is infuriating

You click Windows Sandbox, see the loading spinner, and then nothing. Just a message: "Windows Sandbox failed to start. Error 0x80070002." If you are reading this, you are probably close to giving up. But stay with me – I have fixed this on hundreds of machines in my IT support days. The fix is often quick.

The main fix: turn off and turn on Windows Sandbox

Error 0x80070002 means the system cannot find a file it needs. Windows Sandbox is a feature that uses several components. Sometimes these components get corrupted or not fully installed. The fastest fix is to disable and re-enable the feature.

1. Open Control Panel and go to Programs and Features.
2. Click Turn Windows features on or off on the left.
3. Scroll down to Windows Sandbox. Uncheck it. Click OK and restart your PC.
4. After restart, go back to the same window. Check Windows Sandbox again. Click OK and restart again.

This forces Windows to reinstall the feature files. I have seen this work on Windows 10 versions 1903 and later, and Windows 11 version 21H2 and newer. It sounds too simple, but it fixes about 70% of cases.

Why this works

Error 0x80070002 is the Windows equivalent of a "404 Not Found" on the web. When you enable Windows Sandbox, Windows copies files from the component store. If those files are missing or damaged, the feature cannot start. Disabling removes the broken references. Re-enabling pulls fresh files from the component store. That's it.

One real-world scenario: I worked with a user who installed a third-party antivirus that blocked some system files. After disabling and re-enabling Windows Sandbox, it worked. The antivirus had not blocked the files – it just interfered during the initial install.

If the first fix does not help

Sometimes the component store itself is broken. Here are three more things to try, in order.

Run System File Checker

Open Command Prompt as administrator. Type:

sfc /scannow

Let it finish. It checks core system files. If it finds corruption, it tries to fix them. Then restart and try Sandbox again.

Use DISM to repair the component store

If the system file checker does not help, run this next command in the same Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth

This can take 10–20 minutes. Do not cancel it. After it finishes, restart. Then try the main fix again (disable and re-enable Windows Sandbox).

Check Virtual Machine Platform

Windows Sandbox needs the Virtual Machine Platform feature. Open the same Windows Features window. Make sure Virtual Machine Platform is also checked. It is usually checked automatically when you enable Sandbox, but sometimes it gets unchecked. If it is missing, check it, restart, and try again.

Less common variations

I have seen the same error happen in specific situations:

• After a Windows Update: Some updates (like KB5005101 on Windows 10) broke Sandbox for many users. If this started after an update, uninstall that update via Settings > Update & Security > View update history.
• On systems with Hyper-V disabled: Windows Sandbox requires Hyper-V to be enabled at the BIOS level. If you turned off virtualization in BIOS, Sandbox cannot start. Re-enable it in your BIOS settings (look for "Intel VT-x" or "AMD-V").
• After using disk cleanup: Disk Cleanup sometimes deletes temporary files that Sandbox needs. Run the main fix again to restore them.

How to prevent this from happening again

The best way to avoid error 0x80070002 is to keep your system healthy:

• Run sfc /scannow once a month. Put a reminder in your calendar.
• Do not disable Windows Update. Security patches often fix these file issues.
• If you use a registry cleaner, stop. They break things. I have never seen one fix a real problem.
• If you need to turn off Sandbox for a while, disable it properly via Windows Features, not by deleting files.

Windows Sandbox is a great tool for testing suspicious software. Once it is working, it stays working – unless you mess with system files. Follow these steps and you will be back to safe testing in minutes.