Guide: Fix ‘Windows Sandbox No Hypervisor Was Found’ Issue
Windows Sandbox is a phenomenal addition to Windows 10, with a host of uses ranging from checking files for malware to fiddling with the operating system settings in general. However, it is also prone to a range of problems. A while ago I talked about the various solutions to the internet connectivity problems that could plague the Windows Sandbox. And today, I’m going to discuss the actions you can take if you get the ‘No hypervisor found’ error when you try to start it. The hypervisor is an essential part of the operating system required to run virtual machines, and this error is generated when the Windows Sandbox cannot access it. So below, I’m going to suggest three solutions that you can easily use to get things in the right direction. I recommend starting from the beginning and working your way down the list. The last solution helped me fix the problem when I came across it a while ago. That said, it’s always better to get rid of some of the most plausible causes first.
1. Check Virtualization
Although Windows Sandbox is a disposable environment, it functions just like any other virtual machine. Which means that the hypervisor it is supposedly running on will not work when CPU virtualization is disabled. CPU virtualization is a hardware based feature, but unless you’re using an outdated system, chances are the processor will support it. However, it needs to be enabled and there is an easy way to find out if this is the case. Start by opening Task Manager (right-click on the taskbar, then click Task Manager). On the Performance tab, click CPU and then check the status next to Virtualization – it should be Enabled. If so, skip to the next section.
If virtualization is disabled, you will need to go to your system’s BIOS or UEFI to find the featureThe catch here is that the whole procedure, while quite simple, differs from computer to computer. If you are experienced in enabling or disabling the featurethen just go ahead and do it. If not, it is a good idea to check the documentation for your computer motherboard model for the exact instructions. Once you enable CPU virtualization, try running Windows Sandbox. In my case, I have to enter the BIOS when starting the computer by pressing F2, going to the Advanced tab and then enabling the Intel Virtualization Technology option. Note: To get information about your system to help you find the relevant documentation online, type ‘msinfo32’ in the Start menu and click Open.
2. Turn on Windows Features
With CPU virtualization enabled, it would be strange to run into the error message ‘No hypervisor found’. So it makes sense to have a few operating system based ones features that help virtual machines to operate successfully. To do this, open Windows Features (type windows features from the Start menu and click Open). Follow that up by checking the boxes next to the following features
Click OK to activate them. After that, restart your computer and check if Windows Sandbox starts successfully without the resulting error message.
3. Add a BCD item
The final What you need to do is make sure that the hypervisor is configured to run automatically when the computer starts. To do that, you need to add an item to your computer’s boot configuration data (BCD) using the command prompt. Open an elevated command prompt console (type cmd from the Start menu, then click Run as administrator). Then enter the following command in the command prompt console and press Enter: BCDEDIT / Set {current} hypervisor launchtype auto
Restart your computer. Restart an elevated Command Prompt console, type BCDEDIT in the console and press Enter. On the list that appears up, the status next to hypervisor launchtype should be Auto. That means the hypervisor has been successfully configured to run at startup.
You are now ready to go. Start Windows Sandbox. And voila! It should probably load right away.
Sandbox Yourself
The disposable nature of the Windows Sandbox makes it a great tool for countless applications. And it’s always best to make sure it’s functioning properly so you can fire it up anytime you want. And hopefully the above fixes have worked to get rid of that annoying ‘No hypervisor found’ error for good.
If you are still having problems, delete third-party virtual machines from your computer (such as VirtualBox or VMWare) and check again. The hypervisors used by these platforms can conflict with the hypervisors used by Windows Sandbox, and you should be aware of that. The next up Concerned about your privacy? Here are 5 privacy settings for Windows 10 you should change right away.
Fix ‘Windows Sandbox No Hypervisor Was Found’ Issue: benefits
Faq
Final note
I hope you like the guide Fix ‘Windows Sandbox No Hypervisor Was Found’ Issue. In case if you have any query regards this article you may ask us. Also, please share your love by sharing this article with your friends. For our visitors: If you have any queries regards the Fix ‘Windows Sandbox No Hypervisor Was Found’ Issue, then please ask us through the comment section below or directly contact us. Education: This guide or tutorial is just for educational purposes. Misinformation: If you want to correct any misinformation about the guide “Fix ‘Windows Sandbox No Hypervisor Was Found’ Issue”, then kindly contact us. Want to add an alternate method: If anyone wants to add more methods to the guide Fix ‘Windows Sandbox No Hypervisor Was Found’ Issue, then kindly contact us. Our Contact: Kindly use our contact page regards any help. You may also use our social and accounts by following us on Whatsapp, Facebook, and Twitter for your questions. We always love to help you. We answer your questions within 24-48 hours (Weekend off). Channel: If you want the latest software updates and discussion about any software in your pocket, then here is our Telegram channel.
