Launching Windows Sandbox in Windows 11 Pro or Enterprise to test untrusted software can suddenly abort with an error dialogue: Windows Sandbox failed to initialize. Error 0x80070015: The device is not ready. Windows Sandbox provides an isolated, disposable desktop environment powered by Hyper-V container technology. When the host hypervisor fails to mount the dynamic sandbox VHDX image or when virtualization dependencies are disabled, the initialization daemon collapses before the container window can render.
Repairing error 0x80070015 requires confirming hardware virtualization states in your UEFI/BIOS, restarting Hyper-V dependent services, and rebuilding container package features.
Why Does Windows Sandbox Throw Error 0x80070015?
The hexadecimal error code 0x80070015 translates to ERROR_NOT_READY in the Windows storage subsystem. Key triggers include:
- Hardware Virtualization Disabled in BIOS/UEFI: Intel VT-x or AMD-V virtualization extensions are turned off in motherboard firmware, preventing the Hyper-V hypervisor from generating isolated memory partitions.
- Conflicting Hyper-V Host Compute Network Services: The Host Network Service (HNS) or Hyper-V Virtual Machine Management service (VMMS) is stopped, disabled, or locked in an orphaned state.
- Storage Disk and VHDX Mounting Failures: Windows Sandbox attempts to create a dynamic disposable virtual hard disk under the user AppData directory, which fails if disk compression or third-party encryption locks the folder.
- Third-Party Hypervisor Collisions: Running VMware Workstation, VirtualBox, or Android emulators with nested virtualization configurations that lock low-level VT-x registers.
Method 1: Verify Hardware Virtualization in Task Manager and BIOS
Ensure that your CPU virtualization flags are enabled at the hardware level:
- Press Ctrl + Shift + Esc to open Task Manager.
- Switch to the Performance tab and select CPU.
- Look at the specifications listed below the live performance graph.
- Verify that Virtualization: reads Enabled.
- If it states Disabled, restart your PC and enter your BIOS/UEFI setup (typically by tapping Del, F2, or F12 during boot).
- Locate CPU configuration options and enable Intel Virtualization Technology (Intel VT-x) or SVM Mode (AMD-V). Save changes and boot back into Windows.
Method 2: Restart Dependent Hyper-V and Container Services
Windows Sandbox requires several background daemons to configure its disposable micro-VM:
- Press Windows Key + R, type
services.msc, and press Enter. - Scroll through the services list and locate each of the following:
- Hyper-V Host Compute Service (vmcompute)
- Hyper-V Virtual Machine Management (vmms)
- Host Network Service (hns)
- Virtual Disk (vds)
- Right-click each service, select Properties, set the Startup type to Automatic, and click Start if the service is currently stopped.
- If the services are already running, right-click and choose Restart.
- Attempt to launch Windows Sandbox.
Method 3: Disable and Re-enable Windows Sandbox Feature
Reinstalling the sandbox optional component clears corrupted sandbox system image layers:
- Press Windows Key + X and choose Terminal (Admin).
- Execute the following command to completely uninstall Windows Sandbox:
dism /online /disable-feature /featurename:Containers-DisposableClientVM /norestart - Next, disable the underlying Hyper-V container platform:
dism /online /disable-feature /featurename:HypervisorPlatform /norestart - Restart your computer.
- After rebooting, open Terminal (Admin) again and re-enable both features simultaneously:
dism /online /enable-feature /featurename:HypervisorPlatform /all /norestart dism /online /enable-feature /featurename:Containers-DisposableClientVM /all - Restart your computer once more. Windows will unpack a clean, uncorrupted Sandbox image during system startup.
Method 4: Clean Up Temporary Sandbox VHDX Files
Orphaned virtual disk mount files can prevent fresh container initialization:
- Press Windows Key + R, type
C:\ProgramData\Microsoft\Windows\Sandbox, and press Enter. - Delete any temporary folders or residual
.vhdxdisk containers in this directory. - Reboot your system and launch Windows Sandbox.