Hypervisor is not running ошибка

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.

Below is the full text of the error:

Hyper-V Manager

An error occurred while attempting to start the selected virtual machine(s).

VMname failed to start.

Virtual machine VMName could not be started because the hypervisor is not running.

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 service status using the command:

Get-Service vmcompute,vmms

In our case, both services are in the Stopped state. Try starting them manually with the PowerShell command:

start-Service vmcompute,vmms

However, the services did not start with the error:

start-Service : Service ‘Hyper-V Host Compute Service (vmcompute)’ cannot be started due to the following error: Cannot start service vmcompute on computer ‘

For Hyper-V services to run on a computer, your device must meet the following requirements:

1. Hardware virtualization support must be enabled in BIOS/UEFI settings. This option may have different names depending on the BIOS version and CPU model. For example, Intel Virtualization Technology (VT-X), AMD-V, Virtualization Extensions, Vanderpool. Change the option value to Enable. Also, enable Intel VT-d or AMD IOMMU options if available in your BIOS;
   On AMD devices, you need to additionally check if the SVM mode option is enabled in the BIOS. SVM support (Support Vector Machine) allows you to enable the AMD SVM (Secure Virtual Machine) private group.
   On HP servers, also check if the following BIOS options are enabled: Intel(R) Virtualization Tech and No Execute Memory Protection. The last option provides support for Data Execution Prevention (DEP).
2. Your CPU should be SLAT compatible (Second Level Address Translation). Check your processor’s specification on the vendor’s website and make sure it supports SLAT. On Intel processors, support for SLAT is provided by EPT (Extended Page Table) technology. On AMD CPUs it’s being provided by RVI (Rapid Virtualization Indexing). On Windows, you can check if your computer has SLAT support with the command:

   systeminfo|find “Second Level”

   It should return the string:

   Second Level Address Translation: Yes.

   You can also use a free utility to determine the capabilities of the processor Microsoft Sysinternals:

   coreinfo.exe –v

   

3. Check if DEP is enabled in BIOS and Windows settings. Data Execution Prevention (DEP) is system-level memory protection. Press Win+Pause > Advanced System Settings > Performance > Settings > Data Execution Prevention tab. Make sure the option Turn on DEP for essential Windows programs and services only is enabled.

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:

Hyper-V Requirements: VM Monitor Mode Extensions: Yes

Virtualization Enabled In Firmware: Yes

Second Level Address Translation: Yes

Data Execution Prevention Available: Yes

Configure Hyper-V to start automatically with the command:

bcdedit /set HypervisorLaunchType auto

This 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.

1. Go to the Search bar and type Windows Features > Turn Windows features on or off;
   
2. Go to Hyper-V > Hyper-V Platform section and disable Hyper-V Hypervisor and Hyper-V Services features. Restart your computer and then re-enable these features.

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-Hypervisor

Restart your computer:

Restart-Computer

Then enable the Hyper-V features:

Enable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform,Microsoft-Hyper-V-All,Microsoft-Hyper-V,Microsoft-Hyper-V-Hypervisor

On Windows Server 2019/2016/2012R2, use the following commands to re-install the Hyper-V role:

Remove-WindowsFeature -Name Hyper-V

Install-WindowsFeature -Name Hyper-V

Fix: Virtual Machine could not be started because the hypervisor is not running on Windows Server 2012 R2

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.

Referer. Check our post on how to set up Hyper-V replication.

The following errors appeared in the System Event Logs:

Error ID: 80
Hypervisor launch failed; The operating systems boot loader failed with error 0xC00000BB.

Error ID: 15350
The virtualization infrastructure driver (VID) is not running.

Error ID: 15160
‘MACHINE NAME’ failed to restore virtual machine state.

Error ID: 20148

Virtual machine ‘SVR1’ could not be started because the hypervisor is not running The following actions may help you resolve the problem: 1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization. 2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer.  (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on.  Resetting the physical computer is not sufficient.) 3) If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.

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:5009624

wusa /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.

1. Go to https://www.catalog.update.microsoft.com/Search.aspx?q=KB5010794
2. Download the MSU update file for your version of Windows;
3. Install the MSU update using the Windows Update Standalone Installer by double-clicking on it;
4. Restart your Hyper-V host.

by Milan Stanojevic

Milan has been enthusiastic about technology ever since his childhood days, and this led him to take interest in all PC-related technologies. He’s a PC enthusiast and he… read more

Updated on March 22, 2022

by Milan Stanojevic

Milan has been enthusiastic about technology ever since his childhood days, and this led him to take interest in all PC-related technologies. He’s a PC enthusiast and he… read more

Updated on March 22, 2022

Many users use virtualization, but sometimes they might encounter Hypervisor is not running message on their PC.

This message will prevent you from using virtualization, but in today’s article, we’ll show you how to properly tackle this issue.

Virtualization is a useful feature, but sometimes problems with it can occur. Speaking of virtualization issues, here are some common problems that users reported:

• Hypervisor is not running Windows 10 Pro, BIOS – This problem can occur if virtualization isn’t enabled in BIOS, so be sure to find this feature and enable it.
• Hypervisor launch has been disabled through the hypervisorlaunchtype bcdedit setting – Sometimes Hyper-V feature can be disabled, but you should be able to start it simply by running a single command in Command Prompt.
• Hyper-V failed to start Hypervisor is not running – This problem can occur if your BIOS is out of date. To fix the issue, update your BIOS and check if that solves the problem.
• Virtual machine error Hypervisor is not running – Sometimes this problem can occur due to problematic updates, and in order to fix the issue, it’s advised to find and remove these updates manually.
• Hypervisor is not enabled, present, working – These are some common problems that can occur with Hyper-V, but you should be able to fix them using one of our solutions.

How do I fix the Hypervisor not running error on Windows 10?

1. Make sure that virtualization is enabled in BIOS
2. Update your BIOS
3. Update the drivers to the latest version
4. Reinstall HyperV feature
5. Remove problematic updates
6. Use bcdedit command
7. Use DISM command
8. Check if your CPU supports virtualization
9. Use third-party applications

1. Make sure that virtualization is enabled in BIOS

If you’re getting Hypervisor is not running message, perhaps the problem is related to your BIOS settings. As you know, in order to use virtualization, this feature needs to be actually enabled in BIOS.

To check if virtualization is enabled, just enter BIOS and look for this feature.

How to enable virtualization in BIOS:

1. Access your BIOS (If you need a hand, here’s how to enter BIOS on a Windows 7, 10 or 11 PC).
2. Then, click on Advanced Mode, and go to the Advanced tab.
3. Select CPU Configuration and set the Intel Virtualization Technology option (for Intel) or the SVM Mode (for AMD) to Enabled.
4. Make sure you save the changes before you exit this screen.

That is how to enable Hyper-V Hypervisor in Windows 10. However, note that enabling virtualization can be different according to your CPU, PC model, chipset, and of course, motherboard.

To see how to properly access BIOS and find this feature, we advise you to check your motherboard manual for more information.

Once you enable this feature, go back to Windows and check if the problem is still there.

2. Update your BIOS

The problem with virtualization can be your BIOS, so if you’re getting the Hypervisor is not running message on your PC, the problem might be an outdated BIOS.

Several users reported that they fixed this problem by updating their BIOS to the latest version.

This is an advanced process, and if you don’t perform it properly you can cause permanent damage to your PC, so we advise you to be extra cautious.

We already wrote a short guide on how to flash your BIOS, but if you know how to properly update BIOS on your motherboard, check your motherboard manual for detailed information.

3. Update the drivers to the latest version

If you’re unable to use virtualization due to Hypervisor is not running message, perhaps the problem is related to your drivers.

If you want to update all drivers on your PC fasts, perhaps using a third-party solution might be the best choice.

Using our recommendation, you can automatically update all your drivers with just a couple of clicks.

⇒ Get DriverFix

4. Reinstall the HyperV feature

1. In the Search bar type windows features, and choose Turn Windows features on or off from the list of results.
   
2. Locate the HyperV feature and uncheck it. Now click OK to save changes. If you’re asked to restart your PC, be sure to do so.
   
3. Once your PC restarts, go back to Windows Features window and enable the Hyper-V feature. You might be asked to restart your PC once again, so be sure to do that.

According to users, if you’re getting this error, perhaps there’s a glitch with HyperV feature.

Sometimes various Windows glitches can occur, but you can fix most problems with HyperV simply by reinstalling it.

Once your system restarts, the problem with Hyper-V should be resolved and everything will start working again.

In addition, the Task Manager can detect if it’s running on a physical or virtual machine. Under the Performance tab, the label Virtual machine: Yes is listed if a hypervisor has been detected.

Tip

The best virtual machines for Windows 10 are VMware Workstation, VirtualBox, Hyper-V, and Citrix Hypervisor. For more information about each machine, check out our in-depth guide.

5. Remove problematic updates

1. Press the Windows Key + I to open the Settings app.
2. Navigate to the Update & Security section, and select View update history.
   
3. You should now see a list of recent updates. Pay attention to the recent updates and memorize them or write them down. Now click Uninstall updates.
   
4. List of recent updates will appear in the new window. To remove an update, double-click it and follow the instructions on the screen.
   

If the error started appearing recently, the problem might be a problematic Windows update.

As you know, Windows installs updates automatically, and if the problem started appearing recently, it’s possible that the update is causing it.

To fix the problem, it’s advised that you find the problematic update and remove it, by following our above steps.

Once the update is removed, check if the problem is resolved. You might have to repeat this step a couple of times before you find the update that is causing the problem.

Once you find the problematic update, be sure to write its name down.

Windows tends to install the missing updates automatically, so in order to prevent this problem from reappearing, we advise you to block this update from installing automatically.

Read more about this topic

• Fix Hypervisor_Error BSOD in Windows 10/11
• How to disable Hyper-V in Windows 11
• Seeing the Hyper-V Assembly not found error?
• How to fix the Hyper-V ran out of memory error
• Can’t Install Hyper-V in Windows 10

6. Use the bcdedit command

1. Press the Windows Key + X, and select Command Prompt (Admin) or PowerShell (Admin) from the menu.
   
2. When Command Prompt opens, run the following command: bcdedit /store c:BootBCD /set hypervisorlaunchtype Auto

After the command is executed, check if the problem with virtualization is resolved. Alternatively, you can also use the bcdedit /set hypervisorlaunchtype auto command.

If you’re having problems with virtualization, perhaps you can fix the problem simply by running a single command in Command Prompt.

7. Use the DISM command

1. Start Command Prompt as an administrator.
2. When Command Prompt starts, run this command: dism /online /enable-feature /featurename:Microsoft-Hyper-V -All

Sometimes you might get this error because certain components aren’t working properly. To fix this problem, it’s advised that you run the DISM command in order to enable the HyperV feature.

Once the command is executed, Hyper-V feature should be enabled and the problem with virtualization should be resolved.

8. Check if your CPU supports virtualization

In order to use native virtualization in Windows 10, it’s necessary that your processor supports certain features. If it doesn’t have these features, you won’t be able to use the built-in virtualization.

To see if your processor supports virtualization, you’ll need to check its specifications on the manufacturer’s website.

Alternatively, you can use third-party tools in check if your processor supports virtualization.

Many users reported that virtualization won’t work on their PC since the processor doesn’t support SLAT feature.

If your processor doesn’t support the necessary features, you might have to change it in order to use built-in virtualization.

9. Use third-party applications

If you didn’t manage to fix Hypervisor is not running error, perhaps you might want to try using a third-party solution as a workaround.

Even if your processor doesn’t support the virtualization features, you should be able to create a virtual machine in Windows using our recommendation software.

This tool specializes in virtualization, and it offers all the necessary features for both advanced and first-time users alike, so we strongly suggest that you try it out.

⇒ Get WMware Workstation 16

The hypervisor is not running error can cause problems, but we hope that you managed to fix it using one of our solutions. For more suggestions, please access the comments section below.

I had the very same error when using Macrium Reflect’s viBoot with Hyper-V on Windows 11, but the other answers did not apply. We are not using Windows Server, bcdedit hypervisorlaunchtype was already set to auto, everything was working until we installed Virtualbox (after already disabling Hyper-V) and we had rebooted both the VM & the host OS.

We had previously used Virtualbox, but that had been uninstalled and the bcdedit was returned to normal (i.e., auto) so that we could return to Hyper-V.

The solution was a somewhat lengthy set of shut downs / boots:

1. Disable Hyper-V via the Features Add / Remove panel.
2. Shut down the PC.
3. Boot the PC.
4. Enable Hyper-V
5. Shut down the PC.
6. Boot the PC.

While Windows recommended restarting, for some reason that did not work for us even after a few hours of trying fixes & rebooting. The error message in Macrium noted that some BIOS option changes required a shutdown + fresh boot (and not a reboot), so we wondered if that applied to Hyper-V changes, too? We tried it and it worked.

Throughout all these procedures, hypervisorlaunchtype remained auto which is the most common solution I believe.

Tested on

• Windows 11 Pro (22000.556)
• Macrium Reflect v8.0.6635 viBoot w/ Hyper-V

With this, we were finally able to boot into a Windows XP 32-bit guest OS.