Fix Hyper-V Hypervisorlaunchtype Setting Lost After 24H2 Upgrade

After upgrading to Windows 11 version 24H2, some users find that Hyper-V no longer works. The virtual machines fail to start, and the error message states that the hypervisor is not running. This happens because the 24H2 upgrade resets the hypervisorlaunchtype boot configuration data (BCD) setting from Auto to Off. The Windows 11 24H2 installer may intentionally or inadvertently disable the hypervisor to avoid compatibility conflicts during the upgrade process. This article provides the exact steps to restore the hypervisorlaunchtype setting and get Hyper-V operational again.

Why the Hypervisorlaunchtype Setting Resets After the 24H2 Upgrade

The Windows 11 24H2 upgrade process modifies the BCD store to ensure a clean transition. During the upgrade, the installer may set hypervisorlaunchtype to Off to prevent the hypervisor from interfering with driver installations or system updates. This is a safety measure, but it has the side effect of disabling Hyper-V after the upgrade completes.

The BCD store contains boot configuration parameters that the Windows Boot Manager reads at startup. The hypervisorlaunchtype entry controls whether the Windows hypervisor loads. When set to Off, the hypervisor does not load, and Hyper-V cannot start any virtual machines. The 24H2 upgrade does not always reset this setting. It depends on the system hardware, the presence of other virtualization software, and the specific build of 24H2 installed.

What the Hypervisorlaunchtype Values Mean

The hypervisorlaunchtype BCD entry accepts three values:

• Auto: The hypervisor loads automatically at boot. This is the default for systems with Hyper-V enabled.
• Off: The hypervisor does not load. Hyper-V virtual machines cannot start.
• On: The hypervisor always loads, even if no virtualization features are in use. This is rarely needed.

After the 24H2 upgrade, the value is often Off. You must change it back to Auto to restore Hyper-V functionality.

Steps to Restore the Hypervisorlaunchtype Setting After 24H2 Upgrade

Follow these steps to change the hypervisorlaunchtype BCD entry back to Auto. You need administrator privileges on the Windows 11 system.

1. Open Command Prompt as Administrator
   Press the Windows key, type cmd, right-click Command Prompt in the search results, and select Run as administrator. Click Yes in the User Account Control prompt.
2. Check the Current Hypervisorlaunchtype Setting
   In the Command Prompt window, type the following command and press Enter:
   bcdedit /enum {current}
   Look for the line hypervisorlaunchtype. If it shows Off, proceed to the next step. If the line is missing, the hypervisorlaunchtype is also effectively Off.
3. Set Hypervisorlaunchtype to Auto
   Type the following command and press Enter:
   bcdedit /set hypervisorlaunchtype auto
   You should see a message that says The operation completed successfully.
4. Verify the Change
   Run bcdedit /enum {current} again to confirm that hypervisorlaunchtype now shows Auto.
5. Restart the Computer
   Close the Command Prompt and restart your Windows 11 system. The hypervisor will load during the boot process.
6. Test Hyper-V
   Open Hyper-V Manager. Your virtual machines should now start without errors. If you see a message about the hypervisor not running, double-check the BCD setting after the restart.

Alternative Method: Using Windows Recovery Environment

If the system does not boot after changing the hypervisorlaunchtype setting, use the Windows Recovery Environment to fix it. Boot from a Windows 11 installation USB drive, select Repair your computer, then Troubleshoot, Advanced options, and Command Prompt. Run the bcdedit commands from there.

If Hyper-V Still Has Issues After the Main Fix

After restoring the hypervisorlaunchtype setting, some users may still experience problems with Hyper-V. The following issues and fixes address the most common scenarios.

Hyper-V Feature Is Disabled in Windows Features

The 24H2 upgrade may also disable the Hyper-V Windows feature itself. Open Control Panel > Programs > Turn Windows features on or off. Ensure that Hyper-V and all its sub-features (Hyper-V Management Tools and Hyper-V Platform) are checked. If not, check them, click OK, and restart.

Virtualization Is Disabled in BIOS or Firmware

The 24H2 upgrade does not change BIOS settings, but some hardware configurations may have virtualization disabled by default. Restart the computer and enter the BIOS or UEFI firmware settings. Look for options named Intel VT-x, AMD-V, or SVM Mode. Enable them, save changes, and exit.

System Integrity Check Fails After BCD Change

Changing the BCD store can trigger a system integrity check failure on the next boot. If you see a blue screen with error 0xc0000428, boot from a Windows 11 USB drive, go to Repair your computer > Troubleshoot > Advanced options > Command Prompt, and run:
bcdedit /deletevalue {default} testsigning
Then restart.

Hypervisorlaunchtype Auto vs Off: Boot Behavior and Virtualization Status

Item	Auto	Off
Hypervisor loads at boot	Yes	No
Hyper-V virtual machines start	Yes	No
Windows Sandbox works	Yes	No
Windows Defender Application Guard works	Yes	No
Boot time impact	Minimal increase	None
Compatibility with third-party virtualization software	May conflict with VMware Workstation or VirtualBox	No conflicts

After the 24H2 upgrade, your system is likely set to Off. Changing to Auto enables Hyper-V and related features but may cause conflicts with other hypervisors. If you use VMware Workstation or VirtualBox, consider whether you need Hyper-V active.

You can now restore the hypervisorlaunchtype setting to Auto and verify that Hyper-V works after the Windows 11 24H2 upgrade. If you encounter further issues, check the Windows Features panel and BIOS virtualization settings. As an advanced step, create a BCD backup before making changes by running bcdedit /export C:\bcd_backup.bcd in an elevated Command Prompt. This allows you to restore the original configuration if needed.