Hypervisor error/Blue Screen

Question

I have been getting the hypervisor blue screen error. I have attached my minidump files. I have windows 11 Home.
I get this in event viewer:
The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled.
and
Hypervisor launch failed; Either SVM not present or not enabled in BIOS.
https://1drv.ms/u/s!AiRtdYPdecBem30qaSU5FYo_g0xC?e=M45L1i

Answer 1

I have the same problem. MS treat us like we all have a second degree in IT and Programming, this is not the case. I do not want to become a 2nd level support person for my own computer. I am on the fifth reinstall of Windows, and every time you do an update I go back to scratch. My hypervisor is hyper, please MS why are you releasing dudd software. Last time I had blue screens was in 1996!

Answer 2

I just installed hyper v on my computer.

Answer 3

Hello  The error indicates the hypervisor or VSM may not be present or enabled, try below method to enable VSM:

1. Enable Secure Boot and UEFI in BIOS, as well as TPM. Both version 1.2 and 2.0 (PTT) seems to work, but on my Dell XPS 13 I had enabled 2.0.
2. Deploy Windows 10 Build 10130 with a deployment solution of your choice (MDT or SCCM). Configure the solution to join the machine to the domain (again VSM only protects domain credentials).
3. Install the Hyper-V feature in Windows 10. In my testing I had issue when adding the Hyper-V Platform and Hyper-V Management Tools at the same time. But adding the Platform first, and then Management tools fixed that problem. Adding the Hyper-V feature.
4. Enable the Virtual Secure Mode (VSM) policy setting , conveniently named “Enable Credential Guard” (was named LSA Credential Isolation in earlier Windows 10 builds). The setting is found in the “Computer Configuration / System / Device Guard / Turn on Virtualization Based Security” policy Configuring the “Turn on Virtualization Based Security” policy.
5. Finally, configure the BCD in Windows 10 to start VSM by running the following command in an elevated Command prompt and then reboot the machine: bcdedit /set vsmlaunchtype auto Best Regards, Wesley Li ============================================ If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 4

I have had this error for AAAAAAAAGGGGGEEEEES, every time i closed a game, i would get a crash, every so often a load screen in a game i would crash, sometimes just watching youtube it would crash (although that one was very rare) And i think I have finally fixed it with these steps. And if you think they look similar to ChatGPT output... its because it is! i was getting nowhere googling and scrolling through forum posts and nothing was working, so i turned to chatgpt and it seemed to have help me with my issues. And I hope it can help whever else has this issue...

---

1. Disable Hyper-V and Related Virtualization Features in Windows:
   • Open the Control Panel → Programs → Turn Windows features on or off.
     • Uncheck the following options if they are enabled:

        - **Hyper-V**
       
              - **Virtual Machine Platform**
       
                    - **Windows Hypervisor Platform**
       
                          - **Windows Subsystem for Linux**
       
                             - Click **OK** and restart your PC.
       

---

1. Disable SVM in BIOS (Optional):
   • If you're not using virtualization, you can disable SVM Mode (AMD virtualization) in your BIOS to ensure it isn’t causing unnecessary interference:
   • Restart your PC and enter BIOS.
   • Locate the SVM or AMD Virtualization option under Advanced or CPU Settings.
   • Disable it.
   • Save changes and reboot.

---

1. Ensure System Stability:
   • Update BIOS/UEFI: Check for updates on your motherboard manufacturer’s website to ensure the latest fixes for CPU or virtualization-related issues are applied.
   • Update Drivers: Update chipset and other critical drivers via AMD's official site or your motherboard's support page.
   • Run System File Checker: Open Command Prompt as Administrator and run:

          sfc /scannow
     

     This will repair corrupted system files
2. Stop Hypervisor Launch Attempts:
   • Open a Command Prompt as Administrator and run the following command to disable Hypervisor launch:

          bcdedit /set hypervisorlaunchtype off
     

   • Restart your computer

Answer 5

OK, I had the same issue.. And what finally did it was this:

In Windows-Security > Device Security > Core Isolation

Core Isolation was disabled due to incompatible drivers.

I had to uninstall all the relevant Programs/Drivers to be able to enable Core Isolation

Once Core Isolation was enabled (and all the other things that are mentioned above, like BIOS settings), then I was able to satisfy the VSM policy and I could install virtualization services without constant Boot failures.