No hypervisor was found; Error 0xc0351000
If you’re faced with this issue when running Windows Sandbox, you can try our recommended suggestions to resolve the issue: Let’s take a look at the description of the process involved concerning each of the listed solutions.
1] Make Sure Virtualization is Enabled
To check CPU Virtualization, you need to open the Task Manager first by right-clicking the Start button and choosing Task Manager from the menu. In the pop-up window, click the Performance tab and you can see the status of Virtualization. If Virtualization is shown as disabled here, go ahead to enable it in BIOS or UEFI setting. You also need to enable Hyper-V on your computer. Also, make sure that you have the SLAT or Second Level Address Translation support enabled on your CPU.
2] Turn on Windows Features
Windows Sandbox can run successfully with the help of some operating system-based features. Do the following:
Type Windows Feature in the search box.Choose Turn Windows features on or off among the listed apps to open it.Locate the features labeled Virtual Machine Platform and Windows Hypervisor Platform, and select the check boxes beside them.Click OK button to save changes.
Reboot your computer to see if the No hypervisor was found with error code 0xc0351000 issue has been resolved.
3] Ensure hypervisor is configured to run automatically at computer startup
This solution requires you to ensure the hypervisor is configured to run automatically at computer startup. In order to make this configuration, you need to add an entry to the Boot Configuration Data (BCD) in Command Prompt. Do the following:
Press Windows key + R to invoke the Run dialog.In the Run dialog box, type cmd and then press CTRL + SHIFT + ENTER to open Command Prompt as admin.In the command prompt window, type the command below and press Enter.
Reboot your computer and run Command Prompt again as above.Now type the command below and press Enter.
In the output, ensure the item hypervisorlaunchtype status is showing Auto. This means that hypervisor has been set to run at computer startup. Restart your computer. The issue should now be resolved. Hope this helps!
