Share via

HYPERVISOR_ERROR (0x20001) on Windows 11 Host when Starting Specific VMware Workstation Virtual Machine

Ivan Martin Diez 0 Reputation points
2026-06-09T06:10:01.6966667+00:00

Environment

  • Host OS: Windows 11 (issue started after a recent Windows Update in June 2026)
  • Hypervisor: VMware Workstation Pro
  • Hardware: Intel-based laptop
  • Guest OS: Windows 10 x64
  • VMware virtual hardware version: 14
  • Guest firmware: UEFI
  • Secure Boot: Enabled
  • Guest memory: 8 GB
  • Guest CPUs: 4 vCPUs

Problem Description

Since a recent Windows Update, I am experiencing a reproducible host crash when starting one specific VMware virtual machine.

The host system crashes with a Blue Screen of Death and displays:

Stop Code: HYPERVISOR_ERROR (0x20001)

After the BSOD, the host system automatically restarts.

Important Observations

  1. The affected virtual machine previously worked without any issues.
  2. The problem started only after a recent Windows Update.
  3. Other VMware virtual machines continue to run normally on the same host.
  4. The affected virtual machine runs successfully on another laptop using VMware.
  5. The issue therefore appears to be related to the interaction between the updated Windows host hypervisor and this specific VM configuration.
  6. The virtual machine itself is not corrupted and its virtual disk is functional.
  7. The crash occurs on the host operating system, not inside the guest operating system.

VM Configuration

Relevant VMX settings:

  • virtualHW.version = "14"
  • firmware = "efi"
  • uefi.secureBoot.enabled = "TRUE"
  • guestOS = "windows9-64"
  • numvcpus = "4"
  • cpuid.coresPerSocket = "4"
  • memsize = "8000"
  • mks.enable3d = "TRUE"

No TPM device is configured.

No nested virtualization settings are enabled.

No VMware VBS support is enabled.

Troubleshooting Already Performed

  • VMware updated to latest available version.
  • Hyper-V Windows features disabled.
  • Virtual Machine Platform disabled.
  • Hypervisor Platform disabled.
  • Tested with multiple other VMs (working normally).
  • Restored VM from backup.
  • Copied VM again from another system.
  • Verified VM starts correctly on another laptop.
  • Issue remains reproducible only on this Windows host.

Request

Please investigate whether a recent Windows update introduced a compatibility issue between the Windows hypervisor and VMware Workstation that could trigger HYPERVISOR_ERROR (0x20001) when starting specific virtual machine configurations.

I would also appreciate guidance on additional diagnostics, dump analysis, or known hotfixes related to this stop code.Environment

  • Host OS: Windows 11 (issue started after a recent Windows Update in June 2026)
  • Hypervisor: VMware Workstation Pro
  • Hardware: Intel-based laptop
  • Guest OS: Windows 10 x64
  • VMware virtual hardware version: 14
  • Guest firmware: UEFI
  • Secure Boot: Enabled
  • Guest memory: 8 GB
  • Guest CPUs: 4 vCPUs

Problem Description

Since a recent Windows Update, I am experiencing a reproducible host crash when starting one specific VMware virtual machine.

The host system crashes with a Blue Screen of Death and displays:

Stop Code: HYPERVISOR_ERROR (0x20001)

After the BSOD, the host system automatically restarts.

Important Observations

  1. The affected virtual machine previously worked without any issues.
  2. The problem started only after a recent Windows Update.
  3. Other VMware virtual machines continue to run normally on the same host.
  4. The affected virtual machine runs successfully on another laptop using VMware.
  5. The issue therefore appears to be related to the interaction between the updated Windows host hypervisor and this specific VM configuration.
  6. The virtual machine itself is not corrupted and its virtual disk is functional.
  7. The crash occurs on the host operating system, not inside the guest operating system.

VM Configuration

Relevant VMX settings:

  • virtualHW.version = "14"
  • firmware = "efi"
  • uefi.secureBoot.enabled = "TRUE"
  • guestOS = "windows9-64"
  • numvcpus = "4"
  • cpuid.coresPerSocket = "4"
  • memsize = "8000"
  • mks.enable3d = "TRUE"

No TPM device is configured.

No nested virtualization settings are enabled.

No VMware VBS support is enabled.

Troubleshooting Already Performed

  • VMware updated to latest available version.
  • Hyper-V Windows features disabled.
  • Virtual Machine Platform disabled.
  • Hypervisor Platform disabled.
  • Tested with multiple other VMs (working normally).
  • Restored VM from backup.
  • Copied VM again from another system.
  • Verified VM starts correctly on another laptop.
  • Issue remains reproducible only on this Windows host.

Request

Please investigate whether a recent Windows update introduced a compatibility issue between the Windows hypervisor and VMware Workstation that could trigger HYPERVISOR_ERROR (0x20001) when starting specific virtual machine configurations.

I would also appreciate guidance on additional diagnostics, dump analysis, or known hotfixes related to this stop code.

Windows for home | Other | Performance and system failures
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. DYARI BARHAM 34,856 Reputation points Independent Advisor
    2026-06-11T07:53:55.8433333+00:00

    Thanks for sharing the minidump files.

    The minidump files indicate intelppm.sys, which is Intel Processor Power Management driver.

    Please update your Chipset driver from the manufacturer's official website.

    If it does not help, close the VM completely > Open File Explorer and navigate to where your VM is stored. By default it's usually here: C:\Users\YourName\Documents\Virtual Machines\YourVMName\

    Inside that folder you'll see a file called something like YourVMName.vmx > Right-click the .vmx file > Open with > Notepad > Scroll to the very bottom of the file and add this on a new line:

    cpuid.hypervisor.v0 = "FALSE"

    Save the file then close Notepad > Open VMware and try starting the VM to see if the issue is fixed.

    Was this answer helpful?

    0 comments
  2. DYARI BARHAM 34,856 Reputation points Independent Advisor
    2026-06-09T06:47:26.07+00:00

    Hi ,

    I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

    Please go to C:\Windows\Minidump and copy any minidump files you find to your desktop. Afterward, share these files through OneDrive or Google Drive so we can analyze them and identify the specific file that's causing the crash.

    Was this answer helpful?

  3. AI answer

    2026-06-09T06:10:28.0533333+00:00

    The HYPERVISOR_ERROR bug check (0x00020001) indicates that the Windows hypervisor encountered a fatal error. The available documentation describes this as a generic hypervisor failure and does not list VMware-specific compatibility issues or Windows 11–specific hotfixes.

    For this stop code, the documented next step is to analyze the crash dump with the Windows debugger and the !analyze extension to determine the root cause. This is the only supported way in the provided material to move from the generic 0x20001 code to a specific failing component or interaction.

    Recommended diagnostics based on the context:

    1. Ensure that memory dump collection is enabled so that each crash produces a dump file that can be analyzed.
    2. Use WinDbg (from the Windows SDK) to open the memory dump created by the HYPERVISOR_ERROR.
    3. Run the !analyze extension in the debugger. This is explicitly recommended for bug check 0x20001 and is the primary method to identify the underlying cause.

    The documentation also notes that not all 0x20001 stop errors share the same cause, and the parameters are reserved, so the dump analysis is essential.

    If further assistance is required after collecting and analyzing the dump, provide the analysis output to Microsoft Support so they can correlate it with any internal fixes or known issues.

    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.