How to Fix the Windows Sandbox “No Hypervisor Was Found 0XC0351000” Error
Windows Sandbox is a handy utility to test untrusted apps and files in a secure virtual environment. The setup process is pretty straightforward for Windows Sandbox. However, when you attempt to launch the app, you may encounter the “No Hypervisor was found code 0XC0351000” error.
The error message indicates that Windows Sandbox was unable to detect Hypervisor. This can happen due to many reasons, including incorrectly configured virtual machine-related features in Windows Features.
Follow the steps in the article below to troubleshoot this error on your Windows PC.
1. Check and Enable Virtualization Technology in BIOS
All the virtualization-based tools need hardware virtualization enabled in BIOS to work. If you haven’t configured your hardware virtualization, check if it is enabled in Task Manager. If not, you can manually enable it in BIOS to support virtualization tools.
To check the virtualization status:
Now we’ll cover how to enable Hardware Virtualization in BISO on an HP computer. The instructions to enable hardware virtualization may vary depending on your computer manufacturer. you may find specific instructions on your computer manufacturer’s website, or check outhow to enter the BIOS in Windows 10/11.
Wait for your computer to restart. Open Task Manager to see the Virtualization status in the CPU tab. If it says “Enabled,” try to open Windows Sandbox to see if it works without the error.
2. Enable Virtual Machine Platform Features
Windows Sandbox is available as an optional feature that you can install from the Windows Features dialog, and we’ve covered how to do this in our guide onhow to enable and set up Windows Sandbox in Windows 11. Similarly, you may need to enable a few additional optional features essential to run the virtualization tool successfully.
The two optional features you need to enable areVirtual Machine PlatformandWindows Hypervisor Platform. These tools enable platform support for virtual machines and provide the necessary API to run virtualization software on Windows.
To enable virtualization features:
3. Set Hypervisor to Run at System Startup
Windows Sandbox may not work if Hypervisor fails to start during system startup. To fix this issue, you may modify your Boot Configuration Data (BCD) file to launch Hypervisor automatically at system startup.
To set Hypervisor to launch at system startup:
Note that with the Hypervisor set to launch at startup, virtual machines running on third-party virtualization tools such as VMWare may not work correctly.
To disable Hypervisor at startup, type the following command in the elevated Command Prompt:
Once done, restart your computer to apply the changes.
Get Set With Your Sandbox Again
While only available on the Pro, Enterprise, and Education editions of the Windows 10 and 11 running systems, Sandbox is an excellent lightweight virtualization solution to test unsafe files and apps on your PC.
However, if this virtualization option is unavailable, consider using a Windows Sandbox alternative such as Sandboxie-Plus. It is free to use and works on all the editions of Windows OS.
Don’t want to use Windows Sandbox? Or are you on Windows 11’s Home edition? Don’t worry; there are plenty of alternatives out there.
My foolproof plan is to use Windows 10 until 2030, with the latest security updates.
Not Linux, not Windows. Something better.
Goodbye sending links via other apps.
Who asked for these upgrades?
Every squeak is your PC’s way of crying for help.
