HYPERVISOR_ERROR, Code 0x00020001 when booting up PC

Mika 0 Reputation points
2026-09-13T15:38:51.03+00:00

Hi, recently my PC has been having trouble booting up. It shows the error code "HYPERVISOR_ERROR, Code 0x00020001".

It makes me put in my Bitlocker recovery key and redirects me to a blue page, but before it does that the errorcode changes to C:\Windows\System32\LogFiles\Srt\SrtTrail.txt .

I used a tutorial on the internet, which makes me type into the comand promt.

I used these : bootrec /fixmbr bootrec /fixboot bootrec /scanos bootrec /rebuildbcd

After doing that, my pc turns on, and I can use it again, it seems to not be a permenant fix, so I tried to figure out how to fix this permenantly.

I tried going into the Control Panel and turning off Hyper-V (Programs/Freatures-> turn Windows features on/off) and it turns out I do not have Hyper V.

Could that be the root of the Problem?

If yes, does that mean i should just install Hyper V?

I really don't want this PC to break, since I've only had it for about a year. Help is appreciated!!

Windows for home | Windows 11 | Performance and system failures
0 comments No comments

2 answers

Sort by: Most helpful
  1. DaveM121 929.7K Reputation points Independent Advisor
    2026-09-13T16:12:09.7+00:00

    Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

    Please do not upload a very large Memory.dmp file.

    Open Windows File Explorer.

    Navigate to C:\Windows\Minidump

    Copy any minidump files onto your Desktop, then zip those up.

    Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

    Then post the link here to the zip file, so I can take a look for you.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-09-13T15:39:10.3566667+00:00

    HYPERVISOR_ERROR (0x00020001) means the hypervisor encountered a fatal error. It does not mean Hyper-V must be installed.

    Since bootrec /scanos, bootrec /rebuildbcd, bootrec /fixmbr, and bootrec /fixboot let Windows start again, the immediate boot issue is consistent with recovery steps for boot configuration problems. If the system later falls back to recovery again, installing Hyper-V is not the recommended fix.

    Try this path:

    1. Do not install Hyper-V just to fix this error.
      The stop code indicates a hypervisor failure, but the available guidance does not say that installing Hyper-V resolves it.
    2. If the PC is back in Recovery, repeat the WinRE command path only as a recovery step:
      Troubleshoot > Advanced options > Command Prompt
      Then run:
      • bootrec /scanos
      • bootrec /rebuildbcd
      • bootrec /fixmbr
      • bootrec /fixboot
    3. After Windows starts, install the latest Windows updates.
      Go to Start > Settings > Update & Security > Windows Update > Check for Windows updates.
    4. If the problem keeps returning, use the standard blue-screen checks:
      • Remove any newly added hardware.
      • Start in Safe Mode if normal boot is unreliable.
      • Open Device Manager and check for devices with an exclamation mark; update, disable, or uninstall the affected device if needed.
      • Make sure the system drive has enough free space; 10% to 15% free space is a good target.
    5. If Windows still fails to start repeatedly, use recovery options.
      The documented next step is to use Windows recovery options or system restore if the basic troubleshooting does not help.
    6. Do not edit the registry as a workaround.
      That is specifically warned against for restart/setup-related issues because it can cause later problems.

    About the SrtTrail.txt message: the context only shows that bootrec commands are used from recovery when Windows is stuck on recovery/BCD-related startup problems. It does not identify SrtTrail.txt itself as the root cause.

    If the same stop code continues after updates and recovery steps, the supported guidance is to continue with Windows blue-screen troubleshooting and recovery rather than enabling Hyper-V.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.