The error message “Windows Sandbox failed to initialize” (frequently accompanied by error codes such as 0x80070002, 0x80070057, or 0x800706d9) occurs in Windows 11 when the operating system’s lightweight disposable virtualization environment fails to construct its virtual hard disk, bind virtual network endpoints, or communicate with the Hyper-V host management service. Because Windows Sandbox dynamically generates an isolated container from your current Windows build on every launch, any corruption in the host component store, disabled CPU virtualization in UEFI, or conflicting third-party hypervisors causes initialization to fail. Resolving this issue involves verifying BIOS virtualization, restarting Hyper-V services, and repairing optional features.
Why Windows Sandbox Fails to Initialize
Unlike traditional virtual machines that utilize monolithic virtual hard disks, Windows Sandbox employs dynamic base images using “dynamic generated VHDs” mapped directly against the host OS files in C:\Windows\System32. When you launch Windows Sandbox, the host invokes the Host Compute Service (vmcompute) to construct a sandbox container with its own kernel, memory partition, and user session.
The primary origins of initialization failure include:
- Hardware Virtualization Disabled: Intel VT-x or AMD-V disabled in the motherboard UEFI/BIOS firmware.
- Stopped Hyper-V and Container Services: Critical background daemons (such as
vmcompute,vmicvss, orhns) set to disabled or failing to start. For related state machine errors, see our guide on fixing the group or resource is not in the correct state in Windows 11. - Corrupted Windows Component Store: Damaged system manifests preventing Sandbox from cloning host OS binaries. (Explore our guide on fixing SFC Scannow Windows Resource Protection errors).
- Third-Party Hypervisor Conflicts: Software like VMware Workstation or VirtualBox holding exclusive virtualization locks on the CPU.
| Error Code | Identified Cause | Primary Resolution |
|---|---|---|
| 0x80070002 | The system cannot find the file specified | Run DISM servicing to restore missing sandbox manifests |
| 0x80070057 | The parameter is incorrect | Clear corrupted sandbox temporary cache in ProgramData |
| 0x800706d9 | There are no more endpoints available from the endpoint mapper | Enable and start Windows Defender Firewall and HNS services |
| 0xc0350007 | No virtualization support present | Enable Intel Virtualization Technology (VT-x) or AMD-V in BIOS |
Step 1: Verify Hardware Virtualization in Task Manager
Before modifying software settings, confirm that your computer’s CPU virtualization extensions are actively enabled at the hardware level.
- Press Ctrl + Shift + Esc to launch Task Manager.
- Click the Performance tab on the left sidebar.
- Select CPU.
- Look beneath the real-time performance graphs on the right side for the entry labelled Virtualization.
- Ensure it displays as Enabled. If it reads Disabled, restart your PC, enter your motherboard UEFI/BIOS settings (by pressing Del, F2, or F12 during boot), locate CPU Configuration, and enable Intel VT-x, Intel Virtualization Technology, or AMD SVM Mode.
Step 2: Restart and Verify Hyper-V and Container Services
Windows Sandbox requires several dependent background virtualization services to be operational.
- Press Windows Key + R, type
services.msc, and hit Enter. - Locate each of the following services and verify their status:
- Hyper-V Host Computer Service (vmcompute)
- Hyper-V Virtual Machine Management (vmms)
- Host Network Service (hns)
- Windows Defender Firewall (mpssvc)
- If any service is stopped, right-click it and choose Start. If it is already running, select Restart.
- Right-click each service, select Properties, ensure the Startup type is set to Automatic, and click Apply.
Step 3: Reinstall Windows Sandbox Optional Feature
Corrupted sandbox container packages can be completely rebuilt by toggling the optional feature off and on.
- Press Windows Key + R, type
optionalfeatures.exe, and press Enter to open the Windows Features dialogue. - Scroll down to locate Windows Sandbox.
- Untick the checkbox next to Windows Sandbox and click OK.
- Restart your PC when prompted to remove the corrupted feature files.
- After rebooting, reopen
optionalfeatures.exe, tick Windows Sandbox and Virtual Machine Platform, click OK, and reboot again to install clean feature binaries.
Step 4: Repair Component Store and System Files via Elevated Terminal
If Sandbox cannot locate base image files (error 0x80070002), repairing the Windows image using DISM downloads pristine component manifests from Windows Update.
- Press Windows Key + X and select Terminal (Admin).
- Execute the following commands sequentially:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
- Allow both utilities to complete. Once finished, restart your PC.
Step 5: Clear Temporary Sandbox Data Containers
Stale sandbox containers left behind by abnormal shutdowns can block the creation of new virtual instances.
- Open File Explorer, ensure hidden files are visible, and navigate to:
C:\ProgramData\Microsoft\Windows\Containers\Sandboxes
- If the folder exists and contains orphaned subfolders, delete them.
- Relaunch Windows Sandbox from the Start menu. It will now initialize a pristine, isolated testing environment without error.