Windows Sandbox fails to start with "No hypervisor was found" error (0xc0351000) despite being enabled in Windows Features

Question

I am trying to use Windows Sandbox but it fails to start with the following error:

"No hypervisor was found. Please enable hypervisor support. Error 0xc0351000. No hypervisor is present on this system."

I have already enabled the following features in Windows Features:

• Windows Hypervisor Platform (enabled)
• Windows Sandbox (enabled)
• Hyper-V (enabled)
  

Attached are screenshots showing the error message and the enabled Windows Features.

Could you advise on how to fix this issue?

Answer 1

Hello الطالب معاذ عبدالقادر عبدالفتاح يحيى الشهاري,

Welcome to Microsoft Q&A forum.

The checkboxes only indicate that the virtualization component is installed. However, Windows Sandbox needs it to be loaded during boot. May I know if the AI assistant suggestion help you? Please let me know the results.

Also, can you please open the Task Manager, go to Performance > CPU and let me know the status of Virtualization?

I'm waiting for your reply.

Answer 2

0xc0351000 with "No hypervisor was found. Please enable hypervisor support." means Windows Sandbox does not see the Hyper-V hypervisor running. Windows Sandbox supports only the Hyper-V hypervisor.

Since Windows Sandbox, Windows Hypervisor Platform, and Hyper-V are already enabled, use this checklist:

1. Verify virtualization is enabled in firmware
   • Windows Sandbox requires virtualization to be enabled.
   • On a physical PC, confirm virtualization is enabled in the BIOS/UEFI.
2. If this is a virtual machine, enable nested virtualization
   • Run these commands on the host:

      Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true
      Update-VMVersion -VMName <VMName>
   

3. Confirm the Hyper-V hypervisor is actually running
   • Open System Information (msinfo32.exe).
   • In the details pane, look for: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
   • If that entry is missing, the hypervisor is not active.
4. Check hypervisor launch configuration
   • Open elevated PowerShell and run:

      bcdedit /enum | findstr -i hypervisorlaunchtype
   

   • If the result shows hypervisorlaunchtype Off, enable it with:

      bcdedit /set hypervisorlaunchtype Auto
   

   • Restart the PC afterward.
5. Re-enable Hyper-V from an elevated PowerShell session
   • This requires administrator rights.

      Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
   

   • Restart when prompted.
6. If Windows Sandbox itself needs to be re-enabled
   • Run:

      Enable-WindowsOptionalFeature -FeatureName "Containers-DisposableClientVM" -All -Online
   

   • Restart the PC.
7. Check for third-party hypervisor conflicts
   • Windows Sandbox only supports Hyper-V hypervisor. Third-party hypervisors are not supported for Sandbox.
   • If another virtualization product is installed, update it to a version that supports Hyper-V mode or turn it off.
8. Confirm the Windows edition supports Hyper-V/Sandbox
   • Hyper-V cannot be installed on Windows 10 Home or Windows 11 Home.

If the issue is specifically that Sandbox reports No hypervisor was found, the most relevant fixes are:

• enable virtualization in BIOS/UEFI,
• make sure hypervisorlaunchtype is not Off,
• ensure Hyper-V is enabled and the system has been restarted,
• enable nested virtualization if running inside a VM.

---

• Troubleshoot Windows Sandbox
• Install Windows Sandbox
• Troubleshooting Windows Subsystem for Linux
• Install Hyper-V (windows)