Confirm that the system is Windows 10/11 Professional or Enterprise Edition and version ≥1903; 2. Enable Windows Sandbox, virtual machine platform, Windows virtualization platform and Hyper-V in "Windows Features"; 3. Enter the BIOS to enable CPU virtualization technology (Intel VT-x/AMD-V); 4. Check whether "Virtualization" in the Task Manager displays "Enabled"; 5. Make sure that key services such as Hyper-V Host Compute Service are "automatic" and "running"; 6. Clean components through PowerShell if necessary and reset the Sandbox function; 7. Check the error codes related to Windows Sandbox Host Service in the event viewer for further troubleshooting; 8. Exclude security software interference and ensure that the system is updated intact. Following the above steps to check one by one can solve the problem of Windows Sandbox startup failure.

Windows Sandbox failed to start — This problem is not uncommon among professional/enterprise users using Windows 10 or Windows 11. Although Sandbox is a lightweight, convenient isolation environment, startup failures are often related to system configuration or hardware support. Here are some common causes and solutions to help you quickly troubleshoot and fix them.

1. Confirm the system version and version requirements

Windows Sandbox only supports:

• Windows 10 Professional/Enterprise Edition (version 1903 or higher)
• Windows 11 Professional/Enterprise Edition
• Not supported for home version

? Inspection method:

1. Press Win R , enter winver , and enter.
2. Check whether the system version is ≥ 1903.
3. Right-click "This Computer" → Properties to confirm whether the system type is "Professional Edition" or "Enterprise Edition".

?? Home version users cannot use Sandbox unless they upgrade the system or manually add feature packages (not recommended, poor stability).

2. Enable the necessary functions and services

Sandbox relies on multiple Windows functions and services and must be enabled.

Steps to enable:

1. Press Win X → Select Apps and Features → Programs and Features → Enable or turn off Windows features
2. Check the following options:
   • ?? Windows Sandbox
   • ?? Virtual Machine Platform
   • ?? Windows Virtualization Platform
   • ?? Hyper-V (if available)

?? If the "Hyper-V" gray color is not optional, it may be due to hardware not being supported or BIOS settings.

3. Click "OK" to restart the computer.

3. Check whether hardware virtualization is enabled

Sandbox relies on CPU-dependent virtualization technology (Intel VT-x / AMD-V) and must be enabled in the BIOS.

Inspection method:

1. Press Ctrl Shift Esc to open Task Manager.
2. Switch to the Performance tab → CPU.
3. Check whether Virtualization displays Enabled.

? If "Disabled" is displayed:

• Restart the computer and enter BIOS/UEFI (usually press F2, F12, and Del keys)
• Find options like "Intel Virtualization Technology" or "SVM Mode" and set to Enabled
• Save and restart

? The BIOS paths of different motherboards are different. Common locations: Advanced → CPU Configuration or Security options.

4. Ensure that the Windows Sandbox service is running normally

Sometimes the related services are disabled or crashed.

Inspection Service:

1. Press Win R , enter services.msc , and enter.
2. Find the following service to make sure the status is "Running" and the startup type is "Auto":
   • Hyper-V Host Compute Service
   • Hyper-V Virtual Machine Management
   • Remote Procedure Call (RPC)

If the service fails to start, try restarting the system, or run command prompt (administrator) to execute:

 net start vmms

5. Clean up temporary files or reset Sandbox

Occasional system cache or temporary file corruption can cause startup failure.

Try resetting:

1. Close all Sandbox-related windows.

2. Open PowerShell (Admin), run:

    Get-AppxPackage *windowsclient* | Remove-AppxPackage

   Note: This will not affect the system, it will just clean up temporary components.

3. Re-enable the Windows Sandbox feature (uncheck → Restart → Then check → Restart)

---

6. Check the error log location problem

If all the above is invalid, check the system log:

1. Press Win R and enter eventvwr.msc
2. Navigate to: Windows Logs → System
3. Find error events from Windows Sandbox Host Service or vmcompute

Common error codes:

• 0x80070148 : Insufficient resources or virtualization is not enabled
• 0x80070005 : Permission issue, try to run as administrator
• 0x80370102 : Virtualization is not enabled in BIOS

---

Summary: Quick checklist

• ? Is the system Win10/11 Professional or Enterprise version?
• ? Windows Sandbox feature is enabled?
• ? Virtualization (VT-x/SVM) is enabled in BIOS?
• ? Task Manager displays "Virtualization: Enabled"?
• ? Hyper-V related services are running?
• ? Is the system updated in the latest complete?

---

Basically that's it. If it still doesn't work, it may be due to system image corruption or security software intercept (such as some antivirus software disables virtualization), you can try temporarily closing the third-party protection software and try again. Not complicated, but it is easy to ignore details.

The above is the detailed content of Windows Sandbox failed to start. For more information, please follow other related articles on the PHP Chinese website!