In this article, we will take a look at how to fix the error when starting virtual machines on a Windows host with the Hyper-V role: Virtual machine could not be started because the hypervisor is not running. Show Below is the full text of the error:
This error means that the Microsoft Hyper-V core service is not running on this host. Check the status of the two primary services that enable Hyper-V virtual machines to run — Hyper-V Host Compute Service and Hyper-V Virtual Machine Management. Open the services.msc console and check the status of the services there. Or open a PowerShell command prompt with administrator permissions and check the status of the services using the command: Get-Service vmcompute,vmmsIn our case, both services are in the Stopped state. Try starting them manually with the PowerShell command: However, the services did not start with the error:
For Hyper-V services to run on a computer, your device must meet the following requirements:
To verify if all options required for Hyper-V work are available and enabled, run the systeminfo command. Scroll down to the Hyper-V Requirements section. It should return:
Configure Hyper-V to start automatically with the command: bcdedit /set HypervisorLaunchType autoThis command adds the hypervisor autostart option to your boot configuration data file. If all the prerequisites are complete and the Hyper-V virtual machines won’t start, try reinstalling the Hyper-V role.
On Windows 10 and Windows 11, you can reinstall Hyper-V services using PowerShell cmdlets. To disable Hyper-V components: Disable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform,Microsoft-Hyper-V-All,Microsoft-Hyper-V,Microsoft-Hyper-V-HypervisorRestart your computer: Restart-ComputerThen enable the Hyper-V features: On Windows Server 2019/2016/2012R2, use the following commands to re-install the Hyper-V role: Remove-WindowsFeature -Name Hyper-VInstall-WindowsFeature -Name Hyper-V In early 2022, after installing January security updates on Windows Server 2012 R2 hosts with the Hyper-V role, they fail with the error “Virtual machine SVR1 cannot be started because the hypervisor is not running.” The issue only appeared on Hyper-V hosts with Unified Extensible Firmware Interface (UEFI) enabled. The following errors appeared in the System Event Logs:
This issue is caused by buggy security updates KB5009624 and KB5009624. To quickly fix the problem, you can simply uninstall the updates using the commands: wusa /uninstall /kb:5009624wusa /uninstall /kb:5009595 However, it is better to download and install hotfix KB5010794, which should fix this bug. This update is not distributed through Windows Update, so you must download it manually from the Microsoft Update Catalog.
I enjoy technology and developing websites. Since 2012 I'm running a few of my own websites, and share useful content on gadgets, PC administration and website promotion. How do you fix the virtual machine could not be started because a required feature is not installed?To enable the Virtual Machine Platform, do the following:. Search for turn windows features on or off in the Taskbar search box.. Click on the search result.. Find out Virtual Machine Platform option.. Tick the corresponding checkbox.. Click the OK button.. Let the installation be completed.. Reboot your computer.. How do you solve error 0x80370102 the virtual machine could not be started because a required feature is not installed?"Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.". Check the Hyper-V system requirements.. If your machine is a VM, please enable nested virtualization manually. ... . Please follow guidelines from your PC's manufacturer on how to enable virtualization.. Can you run docker without virtualization?Seems like now you can actually run linux docker container on windows without any virtualization. Simply use the Windows Subsystem Linux (WSL).
Do I need to enable HyperDocker requires Hyper-V enabled options for Windows 10. Without an enabled option, Docker can not run after installation. Therefore, the Hyper-V option must be enabled.
|