Solved: Windows 10 Sandbox no hypervisor was found (0xc0351000)

Getting the 'no hypervisor was found (0xc0351000)' error when trying to start Windows 10 Sandbox can be frustrating. This error stops Sandbox from running entirely. The culprit is almost always a misconfigured or unavailable Hyper-V hypervisor, which Sandbox needs to work.

This guide takes you step by step through the most common causes and solutions for this specific error. Follow along to get Sandbox up and running again.

Understanding the 0xc0351000 Error in Windows Sandbox

The error message 'no hypervisor was found (0xc0351000)' points to a missing or disabled Hyper-V hypervisor service. Windows Sandbox is built on Hyper-V, Microsoft's virtualization platform. If Hyper-V isn't running or configured properly, Sandbox simply won't launch.

The 0xc0351000 code itself is a generic Hyper-V error. But in practice, it means your Windows 10 system either can't find the hypervisor at all, or something is actively blocking it. This can be due to BIOS settings, Windows features, or even conflicts with third-party virtualization tools.

Check Hardware Virtualization Support and Enable It in BIOS

Hyper-V and Windows Sandbox require that your CPU and motherboard support hardware virtualization. For Intel CPUs, this is called Intel VT-x. For AMD CPUs, it's AMD-V. Even if your CPU supports it, the feature must be enabled in your computer's BIOS or UEFI firmware settings.

• Shut down your PC completely, then power it on and enter BIOS/UEFI by pressing the appropriate key (often F2, DEL, ESC, or F10) during boot.
• Look for settings named Virtualization Technology, Intel VT-x, Intel Virtualization Technology, AMD-V, or SVM Mode.
• Make sure this setting is enabled. Save and exit BIOS/UEFI, then let Windows boot normally.

If you don't see any virtualization option, check your CPU model on the manufacturer's website to verify support. On many laptops, the virtualization setting is hidden in an 'Advanced' or 'CPU Configuration' menu.

Ensure Hyper-V and Windows Sandbox Features Are Enabled

Even with hardware virtualization enabled, Windows still requires the Hyper-V and Windows Sandbox features to be installed. Sometimes these features are turned off by system updates or by users who previously disabled them.

1. Press Windows + R, type optionalfeatures, and press Enter.
2. In the Windows Features window, check the following boxes:
   • Hyper-V
   • Virtual Machine Platform
   • Windows Hypervisor Platform
   • Windows Sandbox
3. Click OK and allow Windows to install any missing components. You may need to restart your PC.

If any of these features cannot be enabled, check for error messages and consult your Windows edition. Home editions of Windows 10 do not officially support Hyper-V or Sandbox.

Disable Third-Party Virtualization Software and Conflicts

Software like VMware Workstation, VirtualBox, or older Android emulators can conflict with Hyper-V. Many of these tools install their own hypervisors or kernel drivers, which may prevent Hyper-V from starting. This is a common cause of the 0xc0351000 error.

To check for conflicts:

• Uninstall or temporarily disable third-party virtualization programs.
• After uninstalling, restart your PC to ensure all drivers are unloaded.
• Try launching Windows Sandbox again.

Recent versions of VirtualBox and VMware can run alongside Hyper-V, but only in special modes (e.g., VirtualBox 6.0+ with Hyper-V support). Older releases will almost always block Hyper-V.

Verify Hyper-V Services Are Running

Sometimes, even with everything installed correctly, the Hyper-V services may not start automatically or might be disabled. Windows relies on these services to launch Sandbox and other Hyper-V virtual machines.

• Press Windows + R, type services.msc, and press Enter.
• Scroll down and locate these services:
  • Hyper-V Virtual Machine Management
  • Hyper-V Host Compute Service
• Check that their status is 'Running' and their Startup Type is 'Automatic'. If not, right-click and select Start, then right-click again, select Properties, and set Startup Type to Automatic.

If the services fail to start, make sure no third-party software is interfering and that your Windows installation is up to date.

Set Hypervisor Launch to Auto Using bcdedit

Your PC's boot configuration may have the hypervisor launch setting disabled. This is a common tweak for running incompatible virtualization software or troubleshooting. If this setting is off, Hyper-V won't start and Sandbox will show the 0xc0351000 error.

1. Open Command Prompt as Administrator. Press Windows + X and select 'Command Prompt (Admin)' or 'Windows PowerShell (Admin)'.
2. Type the following command and press Enter:
   bcdedit /set hypervisorlaunchtype auto
3. Restart your PC after running the command.

This instructs Windows to load the Hyper-V hypervisor every time your system boots. If you see a message saying 'The operation completed successfully,' the change took effect. Sandbox should now start unless there are other issues.

Update Windows 10 and Device Drivers

Outdated system files or incompatible drivers can break Hyper-V and cause Sandbox errors. Microsoft regularly fixes virtualization bugs through Windows Updates.

• Open Settings > Update & Security and click 'Check for updates.' Install any available updates and reboot if prompted.
• Update your system's chipset and CPU drivers, especially if you're using a relatively new processor. Go to your motherboard or laptop manufacturer's website to download and install the latest drivers.

Driver or kernel-level software from security tools (like anti-cheat systems, low-level firewalls, or endpoint security agents) can also interfere with Hyper-V. Update or temporarily disable such software if you suspect a conflict.

Test Hyper-V with a Basic Virtual Machine

If the 0xc0351000 error persists, test whether Hyper-V itself is working outside of Windows Sandbox. This can rule out problems specific to Sandbox and point to a wider Hyper-V issue.

1. Press Windows + X, select 'Windows PowerShell (Admin)' or 'Command Prompt (Admin)'.
2. Type virtmgmt.msc and press Enter to open Hyper-V Manager. (If unavailable, the Hyper-V feature is not installed.)
3. In Hyper-V Manager, try creating a new virtual machine with default settings.

If the VM fails to start and shows the same or similar error, the core hypervisor is still not running or is blocked. Double check prior sections, especially BIOS settings, bcdedit, and software conflicts. If the VM works, the issue is likely with Sandbox itself - try uninstalling and reinstalling the Sandbox feature via Windows Features.

Frequently asked questions