Windows 11 Pro 24H2 will not boot after enabling Hyper-V

Question

Just upgraded from Windows 11 Home to Pro. I want to enable Hyper-V on my PC. I have verified that it does support it via "msinfo32". My PC is a Dell Inspiron 5593, Intel Core i5 10th Gen with 16GB of memory.

After Hyper-V installs and reboots, my brand new upgrade will not boot. The only way to recover was to restore the PC which I did. Then tried Hyper-V again, same result. Have attempted to search Google for solutions without much success. There has to be a Microsoft process for resolving this issue.

Answer 1

Hi Jack,

Go into the bios and tell us what settings there are under advanced? Not much information regarding this in the Dell manual.

I run Hyper-V on three computers.

try this https://www.dell.com/support/kbdoc/en-us/000195978/how-to-enable-or-disable-hardware-virtualization-on-dell-systems

Answer 2

I have this problem and could not solve it.
However instead of having to restore the PC, I was able to recover by rebooting in safe mode.
When I did that, it detected the update to enable Hyper-V (and previously Sandbox) in the same way it detects an update or feature-pack update failure and reverted back to having the Hyper-V/Sandbox turned off.

Hope this added information lessens panic after the system goes into a boot loop, trying to repair and avoids having to do a restore from backup.

Answer 3

Hi Jack,

Thanks for your post. Before enable the Hyper-V, please make sure you have done the following actions.

1. Check if virtualization is enabled:

• Search for Command Prompt in Windows Start Menu and open it.
• Type systeminfo and press Enter. Wait for the process to finish
• Once the results appear, search for the Hyper-V Requirements section which is usually the last one.
  • If it says A hypervisor has been detected. Features required for Hyper-V will not be displayed. that means Hyper-V is already enabled and there is no reason following this guide anymore.
    • Otherwise, check for Virtualization Enabled in Firmware:.

      - If its Yes, [click here](https://gist.github.com/HimDek/6edde284203a620745fad3f762be603b#Enable-Hyper-V).
      
            - If its No, [click here](https://gist.github.com/HimDek/6edde284203a620745fad3f762be603b#Enable-virtualization).
      

2. Enable virtualization

The process of enabling virtualization can vary a lot depending on the motherboard manufacturer, but it can be summarized in a few steps:

• Completely Shutdown you Computer.
• Turn on the computer and while it is booting up, keep pressing the key to open the BIOS (usually it is Del, F1, F2, F4, F11, or F12). This key depends on the Motherboard manufacturer. You can easily google it out.
• Once you get into the BIOS, it may look very scary or intimidating, but don't worry, you will get it right. Mouse may not work in BIOS so you might have to use the Directional or Arrow keys and the Enter key of the Keyboard to navigate.
  • Search for the CPU configuration section, it can be called CPU configuration, processor, Northbridge or Chipset and may be under an advanced or advanced mode tab or menu.
    • Now you need to look for the virtualization option and enable it, it can have different names such as Hyper-V, Vanderpool, SVM, AMD-V, Intel Virtualization Technology or VT-X.

Once its enabled, save and reboot your pc. If this part did not help you, you can specifically go the Website of the Mother Board Manufacturer of your Computer and ask for help there.

Best Regards,

Ian Xue

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 4

Thanks to all of you for trying, but I have had enough. I was told that Broadcom has made VMware available for home use without having to worry about a license. I obtained a copy of version 17, installed it and it works perfectly without having any issues with my PC booting. Too bad I had to go that way since Microsoft supposedly had it baked in.

Answer 5

Is Microsoft going to fix this? Yes I have virtualization turned on in the Bios.
Yes System Info confirms it.
Sandbox used to work before 24H2 and with it enabled, caused Oct 2024 and subsequent updates to fail to install. Finally found that Sandbox feature being enabled was the reason why.