Error 0x8007045D: Hyper-V Won't Start — Fixes

What Error 0x8007045D Means

Error 0x8007045D (or ERROR_SERVICE_NOT_ACTIVE) occurs when Windows cannot start the Hyper-V Virtual Machine Management service. The system reports: "Failed to start the virtual machine because the 'Hyper-V Virtual Machine Management' service is not running". This issue blocks the creation and startup of any virtual machines, rendering Hyper-V functionality completely unavailable.

The error may appear when:

• Attempting to start a virtual machine in Hyper-V Manager.
• Enabling the Hyper-V component via Windows Features.
• Running PowerShell commands to manage Hyper-V.

Causes

1. The Hyper-V service is disabled or stopped. The startup type is set to "Manual" or "Disabled", or the service has been stopped unexpectedly.
2. Conflict with other virtualization software. Installed VirtualBox, VMware Workstation, or Docker Desktop (with WSL2) can conflict with the Microsoft hypervisor.
3. Corruption of Windows system files. An OS update or a failed update installation may have damaged files related to Hyper-V.
4. Hypervisor disabled in firmware. Virtualization technology (Intel VT-x / AMD-V) is disabled in BIOS/UEFI.
5. Insufficient permissions. Running Hyper-V from a user account without administrator rights.
6. Driver conflicts. Outdated or incorrect hardware drivers (especially chipset or graphics card).
7. Registry corruption. Invalid entries in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmms key.

Solutions

Solution 1: Restart and Configure the Hyper-V Service

Most often, the issue is resolved by simply restarting the service and resetting its startup parameters.

1. Press Win + R, type services.msc, and press Enter.
2. Find Hyper-V Virtual Machine Management in the list.
3. Right-click → Properties.
4. On the General tab:
   • Set Startup type to Automatic.
   • Click Start.
   • If the service is already running, first click Stop, wait for it to stop, then click Start.
5. Click Apply → OK.
6. Try starting the virtual machine again.

⚠️ Important: If the service fails to start, click Log On on the "Log On" tab in the properties window and ensure the Local System account is selected.

Solution 2: Resolve Conflict with Other Virtualization Software

Hyper-V is incompatible with most third-party hypervisors. If VirtualBox, VMware, or Docker Desktop (with WSL2) are installed, they must be disabled.

1. Disable components in Windows:
   • Control Panel → Programs and Features → Turn Windows features on or off.
   • Uncheck:
     • Hyper-V
     • Windows Hypervisor Platform
     • Windows Subsystem for Linux
   • Click OK and restart your computer.
2. Uninstall/disable third-party software:
   • Uninstall VirtualBox/VMware via Programs and Features.
   • Or disable their services (e.g., VMware Authorization Service).
3. Disable virtualization in BIOS/UEFI (if you do not plan to use Hyper-V):
   • Restart the PC, enter BIOS (Del/F2/F10 key).
   • Find CPU/Processor settings (Intel VT-x, AMD-V, SVM) and disable them.
   • Save changes and exit.
4. After restarting, re-enable Hyper-V via Windows Features.

Solution 3: Repair System Files

Corruption of Windows system components often causes this error.

1. Open PowerShell or Command Prompt as an administrator.
2. Run sequentially:

   sfc /scannow
   

   This command scans and repairs protected system files. The process will take 10-20 minutes.

3. After completion, run:

   DISM /Online /Cleanup-Image /RestoreHealth
   

   DISM repairs the Windows image using update sources.

4. Restart your computer and check the Hyper-V service.

Solution 4: Complete Reinstallation of the Hyper-V Component

If the previous steps did not help, reinstall the component from scratch.

1. Open Turn Windows features on or off.
2. Uncheck all boxes in the Hyper-V section:
   • Hyper-V
   • Hyper-V Management Tools
   • Hyper-V Platform
3. Click OK and wait for the removal to complete.
4. Restart your computer (mandatory!).
5. Open Windows Features again and check the same boxes.
6. Click OK and wait for the installation.
7. After the restart, check if the Hyper-V service starts.

Solution 5: Check and Configure Windows Bootloader

Sometimes the hypervisor does not load at system startup.

1. Open Command Prompt as an administrator.
2. Check the current state:

   bcdedit /enum {current}
   

   Look for the hypervisorlaunchtype parameter. It should be Auto.
3. If the value is Off or missing, set it:

   bcdedit /set hypervisorlaunchtype auto
   

4. Restart the PC.
5. Check the Hyper-V service—it should start automatically.

Prevention

• Do not install Hyper-V and other hypervisors (VirtualBox, VMware) simultaneously. Use them alternately, disabling the unnecessary component.
• Regularly update Windows and hardware drivers (chipset, graphics card) via Windows Update.
• Create restore points before installing Windows updates or virtualization software.
• Check BIOS/UEFI after resetting settings—sometimes BIOS updates disable virtualization.
• Avoid manually editing the registry in the SYSTEM\CurrentControlSet\Services\vmms key without a backup.

Frequently Asked Questions

Can Hyper-V and WSL2 be used simultaneously?
Yes, starting with Windows 10 version 2004+ and Windows 11. However, WSL2 also uses Hyper-V, so conflicts with other hypervisors remain the same. Ensure that Windows Hypervisor Platform and Windows Subsystem for Linux are enabled in Windows Features.

Does the error return after a restart?
If the service starts manually but does not retain the 'Automatic' startup type, check your antivirus or system optimization programs (e.g., Advanced SystemCare), which may forcibly stop services.

What to do if the 'Hyper-V Virtual Machine Management' service is missing?
This means the Hyper-V component is not installed or is corrupted. Reinstall it via Turn Windows features on or off (Solution 4). If the service is still missing after reinstallation, run sfc /scannow.