How to Fix Hypervisor Error Windows 11

The HYPERVISOR_ERROR in Windows 11 can be frustrating because it often appears as a blue screen with the stop code HYPERVISOR_ERROR or 0x00020001. It can happen when Windows is using Hyper-V, Windows Subsystem for Linux, Windows Sandbox, virtualization-based security, or another feature that depends on the Windows hypervisor.

Microsoft identifies 0x00020001 as a fatal error encountered by the hypervisor. The stop code itself does not tell you exactly which driver, hardware component, or virtualization feature caused the failure, so troubleshooting needs to focus on the configuration around the hypervisor rather than treating the error as a single software problem.

The good news is that several common causes can be checked without immediately resetting Windows. Start with the simplest checks, then move toward BIOS, virtualization features, drivers, system-file repair, and crash-dump analysis if the error continues.

What Does HYPERVISOR_ERROR Mean in Windows 11?

HYPERVISOR_ERROR is a Windows blue screen stop error with bug check value 0x00020001.

The Windows hypervisor is the virtualization layer that allows Windows and compatible applications to create and manage isolated virtual environments. Hyper-V, WSL 2, Windows Sandbox, and some security features can depend on this virtualization architecture.

When Windows reports HYPERVISOR_ERROR, the hypervisor has encountered a fatal condition.

The important point is that the error does not automatically mean Hyper-V itself is damaged.

Possible causes include:

• A faulty or incompatible device driver
• BIOS or UEFI virtualization problems
• Outdated chipset or processor-related drivers
• Unstable RAM
• CPU or memory overclocking
• Conflicts between Hyper-V and third-party virtualization software
• Corrupted Windows system files
• A Windows update or driver change
• Problems with virtualization-based security
• A hypervisor configuration problem
• Firmware compatibility issues

Microsoft’s documentation for bug check 0x20001 recommends analyzing the crash dump with the Windows debugger when deeper diagnosis is required because the stop code alone does not identify the underlying component.

Before You Start

If Windows is still usable, back up important files before making major virtualization or firmware changes.

Also think about what changed before the first crash.

For example:

• Did you install VMware Workstation or VirtualBox?
• Did you enable Hyper-V?
• Did you start using WSL 2?
• Did you enable Windows Sandbox?
• Did you update Windows?
• Did you install a chipset or graphics driver?
• Did you update your BIOS?
• Did you install new RAM?
• Did you enable XMP or EXPO?
• Did you change CPU settings?
• Did you enable Memory Integrity?

A recent change can provide a useful starting point.

1. Restart Windows

Start with a normal restart if the error happened only once.

A temporary virtualization or driver problem can disappear after Windows reloads the hypervisor and its dependent components.

If Windows is frozen, press Ctrl + Alt + Delete and use the power menu when possible.

Avoid immediately changing BIOS settings or disabling security features after a single isolated crash.

If the HYPERVISOR_ERROR returns after restarting, continue with the checks below.

2. Check Whether Virtualization Is Enabled

Hardware virtualization is important for Hyper-V and other virtualization features.

Open Task Manager:

1. Press Ctrl + Shift + Esc.
2. Select Performance.
3. Select CPU.
4. Look for Virtualization.

You should see:

Virtualization: Enabled

If it says Disabled, Windows may not be able to use hardware virtualization correctly.

You may need to enter BIOS or UEFI and enable the appropriate processor virtualization setting.

Common names include:

• Intel Virtualization Technology
• Intel VT-x
• AMD-V
• AMD SVM
• SVM Mode
• Virtualization Technology

The exact name depends on the manufacturer and motherboard.

Do not change unrelated firmware settings while looking for virtualization.

If you need to access the firmware interface, see How to Open BIOS in Windows 11.

3. Check the Hypervisor Status in System Information

Windows includes a useful diagnostic through System Information.

Press:

Windows + R

Enter:

msinfo32

Press Enter.

In System Summary, look through the information for a message about the hypervisor.

You may see:

A hypervisor has been detected. Features required for Hyper-V will not be displayed.

That message means the Windows hypervisor is already running.

That is useful because it tells you that the hypervisor is loading rather than simply failing to start.

If you are trying to run a virtualization application that requires the hypervisor to be disabled, this message can also explain why the application behaves differently from what you expect.

4. Check the Hypervisor Boot Setting

Windows uses the Boot Configuration Data store to control whether the hypervisor launches during startup.

Open Windows Terminal or Command Prompt as administrator and run:

bcdedit /enum

Look for:

hypervisorlaunchtype

It can be set to:

Auto

or:

Off

Microsoft documents hypervisorlaunchtype as the BCDEdit setting that controls the hypervisor launch option.

If you need the Windows hypervisor for Hyper-V, WSL 2, or another dependent feature and the setting is Off, you can enable automatic launch with:

bcdedit /set hypervisorlaunchtype auto

Restart Windows afterward.

Do not change this setting simply because you saw the word “hypervisor” in the error. If you are experiencing HYPERVISOR_ERROR crashes, the correct setting depends on what virtualization software and Windows features you actually use.

5. Disable Hypervisor-Dependent Features Temporarily

If the crashes began after enabling virtualization features, temporarily disabling them can help determine whether one of those components is involved.

Press:

Windows + R

Enter:

optionalfeatures

Press Enter.

Depending on your Windows installation, you may see features such as:

• Hyper-V
• Windows Hypervisor Platform
• Virtual Machine Platform
• Windows Sandbox
• Windows Subsystem for Linux

Do not disable everything permanently just to test the problem.

Instead, identify what you actually use.

For example, WSL 2 depends on virtualization components, so disabling Virtual Machine Platform can stop WSL 2 from working until the feature is enabled again.

If you use VMware or VirtualBox, Microsoft’s documentation explains that third-party virtualization applications can conflict with Hyper-V and Hyper-V-based features or operate in a slower compatibility mode.

6. Check for Conflicts With VMware or VirtualBox

This is especially important if you installed third-party virtualization software.

Hyper-V, Memory Integrity, Credential Guard, Windows Hypervisor Platform, and other Windows virtualization components can affect how VMware Workstation and VirtualBox access hardware virtualization.

Microsoft documents that third-party virtualization applications may not work normally alongside Hyper-V and its dependent features.

If HYPERVISOR_ERROR started after installing or updating VMware Workstation or VirtualBox, temporarily test the system without the conflicting virtualization stack.

Do not uninstall software immediately.

First determine which environment you actually need.

For example:

If you need WSL 2, Hyper-V, or Windows Sandbox: keep the Windows virtualization stack configured correctly.

If you need a third-party virtual machine application that requires direct hardware virtualization: check its current compatibility with Hyper-V and Windows virtualization-based security.

This distinction can prevent you from disabling an important Windows feature unnecessarily.

7. Update Windows 11

Open:

Settings > Windows Update

Select Check for updates.

Install available updates and restart the computer.

A virtualization-related crash can sometimes be connected to a Windows component, driver, or compatibility issue that has already been addressed by a newer update.

If the HYPERVISOR_ERROR started immediately after a particular update, do not automatically assume that the update is the cause.

Check whether the problem continues after restarting and installing subsequent updates.

If the crash began after a major Windows change, also note the exact Windows version and build. That information can be useful when searching Microsoft support documentation or analyzing crash dumps.

8. Update Chipset and Processor-Related Drivers

The chipset is important to the interaction between Windows, the processor, memory, PCIe devices, and other motherboard components.

A virtualization crash can sometimes involve low-level drivers rather than Hyper-V itself.

Visit the official support page for your computer or motherboard.

Look for current versions of:

• Chipset drivers
• Intel chipset or management components
• AMD chipset drivers
• Processor-related platform drivers
• BIOS or UEFI firmware
• Storage-controller drivers

Avoid downloading chipset drivers from random driver websites.

Use the manufacturer of your exact laptop, desktop, or motherboard whenever possible.

If you have an Intel system, check Intel’s official support resources where appropriate. For AMD systems, use AMD’s official driver and support resources.

9. Update Your BIOS or UEFI

An outdated BIOS can cause compatibility problems with virtualization.

Microsoft’s Hyper-V troubleshooting documentation identifies BIOS or UEFI configuration and firmware compatibility as possible causes of virtualization problems.

Check your current BIOS version before deciding whether to update it.

You can use:

Windows + R

then:

msinfo32

Look for:

BIOS Version/Date

You can also check the version through your motherboard manufacturer’s support software or firmware interface.

If a newer BIOS is available, read the release notes before installing it.

A firmware update can address:

• CPU compatibility
• Memory stability
• Virtualization support
• Security issues
• System stability
• Hardware compatibility

Do not install a BIOS intended for a different motherboard or laptop model.

If the system is unstable, follow the manufacturer’s recovery instructions carefully and make sure power will not be interrupted during the update.

For related BIOS troubleshooting, see How to Check BIOS Version on Windows 11.

10. Disable CPU and RAM Overclocking

Unstable hardware settings can cause low-level Windows crashes.

If you have enabled:

• CPU overclocking
• GPU overclocking
• XMP
• EXPO
• DOCP
• Manual memory timings
• CPU undervolting

temporarily return the system to its default settings.

This is particularly important if HYPERVISOR_ERROR began after a hardware upgrade or BIOS configuration change.

Virtualization can place different workloads on the processor and memory subsystem compared with ordinary desktop use.

A system that appears stable during browsing or gaming can still crash when virtualization is active.

After returning the system to default settings, test Windows again.

If the crashes stop, reintroduce performance settings one at a time rather than enabling everything again at once.

11. Test Your RAM

Unstable or defective memory can cause low-level system crashes, including crashes involving virtualization.

Windows includes a built-in memory diagnostic tool.

Press:

Windows + R

Enter:

mdsched.exe

Press Enter.

Choose the option to restart the computer and check for memory problems.

Allow the test to complete.

If Windows reports memory errors, investigate the RAM before continuing to troubleshoot Hyper-V.

If you have multiple memory modules and the system is unstable, further testing may involve testing modules individually or using a more comprehensive memory-testing utility.

If you recently installed RAM, also check that the memory kit is compatible with your motherboard and that the BIOS recognizes the expected capacity.

12. Run Windows Memory Diagnostic and Check for Hardware Instability

A memory test is only one part of hardware troubleshooting.

Also consider whether the computer has recently experienced:

• Random restarts
• Application crashes
• File corruption
• Other BSOD stop codes
• Failure to resume from sleep
• Freezing under heavy CPU load
• Problems after enabling XMP or EXPO

If HYPERVISOR_ERROR appears alongside several unrelated blue-screen codes, do not focus only on Hyper-V.

A broader hardware or driver problem may be responsible.

13. Run DISM and SFC

Corrupted Windows system files can cause virtualization and other Windows components to behave incorrectly.

Open Windows Terminal or Command Prompt as administrator.

Run:

DISM /Online /Cleanup-Image /RestoreHealth

Wait for the command to finish.

Then run:

sfc /scannow

Allow System File Checker to complete.

Restart Windows afterward.

If SFC reports that it could not perform the requested operation, see Windows Resource Protection Error: How to Fix It for additional troubleshooting.

Do not download replacement Windows system files from unofficial websites.

14. Check Windows Event Viewer

Event Viewer can provide additional information around the time of the crash.

Press:

Windows + X

Select Event Viewer.

Go to:

Windows Logs > System

Look around the time of the HYPERVISOR_ERROR.

Look for events involving:

• Hyper-V
• Hyper-V-Hypervisor
• Kernel-Power
• WHEA-Logger
• Driver failures
• Unexpected shutdowns
• Hardware errors

A WHEA event can be particularly useful because Windows Hardware Error Architecture events may point toward a hardware or firmware-related problem.

Do not assume every event around the crash is the cause. Windows can generate many secondary errors after a blue screen.

Focus on events that occurred immediately before the failure.

15. Check Device Manager for Driver Problems

Open Device Manager.

Look for devices with warning indicators or devices that were recently installed or updated.

Pay particular attention to:

• Chipset devices
• Storage controllers
• Network adapters
• Graphics adapters
• Processor-related components
• USB controllers
• Motherboard devices

If the crash began after a driver update, consider updating to a newer version or rolling back to the previous stable driver when appropriate.

Microsoft’s documentation on Memory Integrity also warns that incompatible kernel-mode drivers can cause problems when virtualization-based security is active.

16. Check Memory Integrity

Memory Integrity is part of Windows virtualization-based security and uses the Windows hypervisor to create an isolated environment for protected code-integrity operations.

Open:

Windows Security > Device security > Core isolation details

Check Memory integrity.

Do not automatically turn it off.

Memory Integrity is a security feature, and Microsoft recommends keeping security protections enabled when compatible with the system.

However, if the HYPERVISOR_ERROR started after a driver or security configuration change, this setting is worth investigating.

If Windows reports an incompatible driver, identify that driver first.

You can also review Memory Integrity Can’t Be Turned On? How to Fix It for related Windows 11 troubleshooting.

Microsoft warns that some applications and hardware drivers can be incompatible with Memory Integrity and that such incompatibilities can cause software problems or, in rare cases, boot failures.

17. Check Virtualization-Based Security

Virtualization-Based Security, or VBS, uses the Windows hypervisor to create an isolated environment for security functions.

This means you can have a hypervisor running even when you never manually installed Hyper-V.

Security features such as Memory Integrity can depend on the Windows hypervisor.

This is why disabling one virtualization feature does not always mean that every hypervisor-related component has disappeared.

If your problem is caused by an interaction between VBS and a driver, identify the incompatible driver before making broader security changes.

If you are troubleshooting a third-party virtualization application, check the software vendor’s current compatibility guidance before disabling Windows security features.

18. Try a Clean Boot

A third-party service or startup component can interfere with virtualization software.

A clean boot starts Windows with a limited set of startup software and services.

Press:

Windows + R

Enter:

msconfig

Press Enter.

Open the Services tab.

Select:

Hide all Microsoft services

Then disable the remaining third-party services for testing.

Next, review startup applications through Task Manager and disable unnecessary third-party startup programs.

Restart Windows.

If HYPERVISOR_ERROR stops occurring, re-enable services gradually until you identify the conflicting component.

Do not permanently disable Microsoft services just to troubleshoot this problem.

19. Reinstall or Repair Hyper-V Features

If Hyper-V components appear damaged or behave unexpectedly, you can temporarily disable and re-enable the relevant Windows feature.

Open:

Turn Windows features on or off

Then identify the Hyper-V components installed on your system.

Disable the relevant feature, restart Windows, and then enable it again.

This can refresh the Windows feature configuration.

However, do this only if you actually need Hyper-V.

If your goal is to run WSL 2, remember that WSL 2 depends on Windows virtualization components. Disabling the wrong feature can create a different problem.

For related virtualization use, see How to Run Linux on Windows 11 With WSL.

20. Check the Hypervisor Launch Configuration Again

After changing Windows features, verify the boot configuration.

Run:

bcdedit /enum

If you need the Windows hypervisor, check that:

hypervisorlaunchtype

is not set to:

Off

To enable automatic launch:

bcdedit /set hypervisorlaunchtype auto

Restart Windows.

If you are deliberately trying to run Windows without the hypervisor because a specific application requires that configuration, the appropriate value may instead be:

bcdedit /set hypervisorlaunchtype off

Do not use the second command simply as a generic fix for every HYPERVISOR_ERROR.

Turning off the hypervisor can prevent Hyper-V, WSL 2, Windows Sandbox, and other dependent features from working.

21. Analyze the Minidump if the BSOD Keeps Returning

If Windows continues to crash with HYPERVISOR_ERROR, stop guessing and examine the crash dump.

Microsoft identifies 0x00020001 as a generic hypervisor fatal error and recommends using the Windows debugger and the !analyze extension to investigate the underlying cause.

Crash dumps are commonly stored under:

C:\Windows\Minidump

You can analyze them with WinDbg.

The purpose is to determine whether the crash consistently points toward:

• A processor-related component
• A driver
• A virtualization component
• A memory problem
• A firmware issue
• Another kernel-level interaction

The stop code itself is not enough to identify the exact cause.

If you are not comfortable interpreting a minidump, preserve the dump and the exact BSOD details before deleting diagnostic files.

22. Check for WHEA Hardware Errors

If Event Viewer shows WHEA-Logger errors around the same time as HYPERVISOR_ERROR, investigate hardware stability more closely.

Potential areas include:

• CPU
• RAM
• Motherboard
• BIOS
• Power delivery
• PCIe devices

Do not automatically replace hardware because of one WHEA event.

Look for repeated errors and whether they occur at the same time as the blue screens.

If the system is overclocked, return it to default settings before making a hardware diagnosis.

23. Remove Recently Added Hardware Temporarily

If the error began after installing hardware, test the computer without that hardware where practical.

Examples include:

• New RAM
• PCIe expansion cards
• USB controllers
• Capture cards
• Network adapters
• Storage devices

A new device may introduce a driver or firmware interaction that only becomes visible when virtualization is active.

Keep the original hardware configuration available so you can reverse the test.

24. Consider a Recent Driver Rollback

If the crashes started immediately after a driver update, rolling back that particular driver can be useful.

Open Device Manager.

Find the device.

Open:

Properties > Driver

If Roll Back Driver is available, use it only when you have a reasonable reason to connect the update with the problem.

Do not roll back unrelated drivers.

A chipset or graphics driver can be important, but a problem involving the hypervisor may also involve processor, storage, network, or motherboard components.

25. Use System Restore if the Problem Started Recently

If System Restore is enabled and the HYPERVISOR_ERROR started after a recent software or driver change, a restore point may help.

Search Windows for:

Create a restore point

Open the System Properties window and select System Restore.

Choose a restore point from before the problem began.

System Restore does not normally remove your personal documents, but it can roll back system files, drivers, applications, and settings.

Review the affected programs before confirming the restore.

26. Reset Windows Only as a Last Resort

Do not reset Windows as the first response to HYPERVISOR_ERROR.

A reset may remove the symptom without telling you whether the real cause was:

• RAM instability
• BIOS configuration
• A driver
• A virtualization conflict
• A hardware fault

If you have already tested virtualization, drivers, system files, memory, and firmware and the crashes continue, Windows recovery or a clean installation can become reasonable troubleshooting options.

Back up important data first.

Why Does HYPERVISOR_ERROR Keep Happening?

Repeated crashes usually indicate that something underneath the hypervisor is consistently unstable.

Common possibilities include:

Unstable memory

XMP, EXPO, manual timings, defective RAM, or a motherboard compatibility problem can cause unpredictable kernel crashes.

Driver problems

Low-level drivers can interact with virtualization and kernel security features.

BIOS problems

Firmware controls processor virtualization and other low-level hardware functions.

Virtualization conflicts

Hyper-V and third-party virtualization applications can interact in ways that affect how virtual machines run.

Security virtualization

VBS and Memory Integrity use the Windows hypervisor, so a driver conflict can appear to be a hypervisor problem.

Corrupted Windows components

Damaged system files can prevent virtualization components from working correctly.

What If the Error Happens Only When Starting a Virtual Machine?

That pattern is useful.

If Windows is stable until you start a virtual machine, focus on:

• Hyper-V configuration
• VMware or VirtualBox compatibility
• Virtual machine configuration
• Hardware virtualization
• BIOS
• Chipset drivers
• Memory stability
• Recent Windows updates

If only one virtual machine triggers the crash while other virtual machines work normally, compare that VM’s configuration with a working VM.

If every VM causes the host to crash, investigate the host’s virtualization stack and hardware first.

What If HYPERVISOR_ERROR Started After a Windows Update?

Record the update date and Windows build.

Then check:

1. Whether Windows has a newer cumulative update.
2. Whether the PC manufacturer released BIOS or chipset updates.
3. Whether your virtualization software has an update.
4. Whether the crash happens with every VM or only one.
5. Whether Event Viewer shows related errors.
6. Whether a minidump identifies a recurring driver.

Do not immediately remove a Windows security update unless there is strong evidence connecting it to the crash and you understand the security implications.

What If You Do Not Use Virtualization?

If you never use:

• Hyper-V
• WSL 2
• Windows Sandbox
• VMware
• VirtualBox
• Android emulators
• Other virtualization software

you may not need the Windows hypervisor for your normal workload.

However, Windows 11 security features can use virtualization in the background. VBS and Memory Integrity are examples.

Therefore, do not assume that “I never created a virtual machine” means the hypervisor is not being used.

Check System Information and Windows Security before changing virtualization settings.

Frequently Asked Questions

What is the HYPERVISOR_ERROR stop code?

HYPERVISOR_ERROR is Windows bug check 0x00020001. Microsoft describes it as a fatal error encountered by the hypervisor.

How do I fix HYPERVISOR_ERROR in Windows 11?

Start by checking virtualization, BIOS or UEFI, Windows updates, chipset drivers, RAM stability, virtualization conflicts, system files, and Memory Integrity. If the BSOD continues, analyze the minidump with WinDbg rather than relying on the stop code alone.

Can RAM cause HYPERVISOR_ERROR?

Yes. Unstable or defective memory can cause low-level Windows crashes, particularly when virtualization workloads stress the system differently from normal desktop use.

Can outdated BIOS cause a hypervisor error?

Yes. Firmware can affect processor virtualization, memory stability, and hardware compatibility. Check your computer or motherboard manufacturer’s BIOS release notes before updating.

Should I disable Hyper-V to fix HYPERVISOR_ERROR?

Not automatically. Disabling Hyper-V may help diagnose a virtualization conflict, but it can also stop features such as WSL 2 and Windows Sandbox from working. Identify what you use before disabling it.

What does bcdedit /set hypervisorlaunchtype auto do?

It configures the Windows boot environment so the hypervisor is launched automatically. Microsoft documents hypervisorlaunchtype as the setting controlling hypervisor launch behavior.

Can VMware or VirtualBox cause HYPERVISOR_ERROR?

Virtualization software can be involved in hypervisor-related conflicts. Microsoft documents compatibility limitations when third-party virtualization applications run alongside Hyper-V and Hyper-V-based features.

Should I turn off Memory Integrity?

Not as a first step. Memory Integrity is a Windows security feature. If an incompatible driver is reported, investigate and update or remove the driver first. Disable security features only when there is a specific troubleshooting reason and you understand what protection you are giving up.

How do I find the cause of a HYPERVISOR_ERROR BSOD?

Check the minidump with WinDbg and run !analyze -v. The 0x20001 stop code is generic, so dump analysis can provide more useful information about the component involved.

When the Hypervisor Error Is Finally Gone

Once Windows stops crashing, do not immediately re-enable every overclock, driver tweak, and virtualization feature you changed during troubleshooting.

Instead, restore your configuration gradually.

For example:

1. Confirm Windows is stable at default hardware settings.
2. Confirm the hypervisor works if you need it.
3. Start your virtualization software.
4. Test WSL or your virtual machines.
5. Re-enable optional features one at a time.
6. Reintroduce performance settings only if necessary.
7. Keep the BIOS and chipset drivers current.
8. Create a restore point after reaching a stable configuration.

That approach makes it much easier to identify the setting or component responsible if the HYPERVISOR_ERROR returns.

A Windows 11 hypervisor crash is not necessarily a sign that the PC needs to be reset or that Hyper-V itself is broken. Because the 0x00020001 stop code is generic, the most effective troubleshooting process is to work through virtualization settings, firmware, drivers, memory stability, Windows components, and virtualization conflicts in a controlled order. When those checks do not identify the problem, the minidump is the next place to look.

Also Read:

• 0x80004005 Error Windows 11: How to Fix It
• How to Fix Error Code: Out of Memory in Chrome or Edge
• Windows Resource Protection Error: How to Fix It
• How to Check if an MSWMM File Is Corrupted