Fix: Windows 8 Stuck at the Boot Screen After Enabling Hyper-V (Historical)

Historical support note: Client Hyper-V was introduced in Windows 8 Pro/Enterprise on supported 64-bit hardware. This guide is retained for legacy Windows 8 systems.

If a PC stops booting immediately after Hyper-V is enabled, do not repeatedly toggle unrelated firmware options. First confirm the hardware and firmware meet Hyper-V requirements.

1. Check virtualization support

Hyper-V requires hardware-assisted virtualization and other CPU/firmware capabilities. On a system that still boots, run:

systeminfo.exe

Review the Hyper-V Requirements section.

Hardware virtualization should normally be enabled in BIOS/UEFI when you intend to use Hyper-V. Follow the PC or motherboard manufacturer’s documentation rather than guessing which firmware option to change.

2. If Windows can boot after Hyper-V is temporarily disabled

From an elevated Command Prompt, the boot hypervisor can be prevented from launching with:

bcdedit /set hypervisorlaunchtype off

Restart. This leaves you able to troubleshoot the Hyper-V feature or drivers without launching the hypervisor. To restore normal Hyper-V launch later:

bcdedit /set hypervisorlaunchtype auto

Only use BCDEdit from the correct Windows installation and with administrator rights.

3. If Windows cannot boot

Use the Windows Recovery Environment and try the least destructive options first, such as Startup Repair or System Restore. If you are not comfortable identifying the correct boot-loader entry from WinRE, do not edit BCD blindly.

4. Firmware updates

If the hardware meets the requirements but Hyper-V consistently fails at boot, check the system/motherboard manufacturer’s support page for a firmware update that specifically addresses virtualization or stability. Apply firmware updates only according to the manufacturer’s instructions.