Share via

Hypervisor_error when starting X-Plane 12 simulator

Joseph C McCormick III 0 Reputation points
2026-06-03T17:46:27.2633333+00:00

After a recent upgrade, one week ago, I have started to get a black screen hypervisor_error (0x200001) and re-boot. I have tried to impliment every possible fix that I have read about. No success. I have stress tested my video and my motherboard memories and there no issues with my memory. I have updated, taken out, and re-installed all the software. I have also made a clean install of the operating system.

I have 4 computers in my home, 3 computers can run X-Plane 12, but my main development computer can not. The computers that can run my simulator all use an Intel 7-17400 CPU but my computer is running an Intel CORE Ultra2 285 and I have 64 gigabytes of memory.

I have read on some forums that driver update package might be causing this issue and I am on the verge of removing this update unless there is a better solution.

Your thoughts and ideas would be greatly appreciated.

Joe

Windows for home | Windows 11 | Performance and system failures

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ian Staines 10 Reputation points
    2026-06-10T22:19:21.27+00:00

    Microsoft just dropped this weeks security updates in KB5094126. This appears to resolve the issue caused by last weeks security update KB5089573

    Specifically, as per the readme:

    [Virtualization] Fixed: This update addresses an issue that could result in Stop errors HYPERVISOR_ERROR (0x20001) and KMODE_EXCEPTION_NOT_HANDLED (0x1E) after installing KB5089573 on some devices during system restarts, virtual machine operations, or while running some gaming applications

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Joseph C McCormick III 0 Reputation points
    2026-06-09T13:35:57.68+00:00

    I followed the offered instructionscompletely. The Dump analysis kept refering to the V settings in the BIOS. The virtualization settings are so hidden that it's almost like they don't want you to find them. It's sad that you almost have to be an IT professional in order to accomplish these simple changes, I'm too old for this. Well, to make a very long story shorter, with the help of MSI and you guys at Microsoft, I was able to contact the BIOS manufacturer. They led me through the new BIOS download and install, pointing out the areas that needed to be changed. Like a miracle my completetly overhauled rig is back to 100%, almost. That IT professional thing I mentioned, well I still have to create rules to let my programs to communicate in and out. Welcome to the new computing world security. ;-)

    Thank you for all your help!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Lychee-Ng 21,550 Reputation points Microsoft External Staff Moderator
    2026-06-04T09:06:12.31+00:00

    Hi Joseph C McCormick III,

    I’m sorry to hear that you’re experiencing crashes with HYPERVISOR_ERROR (0x200001), especially when it happened only with the newer Intel Core Ultra 285 machine. Since you already tried a lot of troubleshooting steps, including reinstalling Windows, it’s limited on what we can do. Still, there are a few things to try before attempting to remove updates right away:

    1 - Temporarily disable the Windows hypervisor features

    • Open Settings > Privacy & security > Windows Security
    • Under Device Security > Core isolation > turn OFF Memory integrity
    • Search and open Control Panel > Programs and Features
    • Choose Turn Windows features on or off > Uncheck:
      • Hyper‑V
      • Virtual Machine Platform
      • Windows Hypervisor Platform
    • Restart the PC > Right-click Start > open PowerShell as Administrator
    • Run: bcdedit /set hypervisorlaunchtype off > Restart again and test X‑Plane.

    2 - Temporarily uninstall any motherboard utility/control software, e.g.

    • ASUS AI Suite
    • MSI Center
    • Gigabyte Control Center
    • Intel XTU
    • Overlay/monitoring tools.

    3 - Update the motherboard BIOS

    Since this system uses a newer Core Ultra platform, I would definitely check for a newer BIOS version directly from the motherboard manufacturer. Early BIOS/microcode revisions sometimes cause virtualization-related crashes under heavy workloads or simulators.

    I would avoid removing Windows cumulative updates blindly, unless no others you have tried improving anything. But that can be one of the solutions.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    2 people found this answer helpful.

  4. AI answer

    2026-06-03T17:47:12.09+00:00

    The HYPERVISOR_ERROR bug check 0x00020001 indicates that the Windows hypervisor has encountered a fatal error. This is not specific to X‑Plane; the simulator is just triggering a condition in the hypervisor.

    From the available information, 0x00020001 is a generic hypervisor failure code. The detailed cause is only visible by analyzing the crash dump with the Windows debugger (!analyze), which is what Microsoft recommends for this class of error.

    Actionable steps:

    1. Collect and analyze the dump
      • Ensure Windows is configured to create at least a kernel or automatic memory dump.
      • After the next crash, open the dump in WinDbg and run !analyze -v to get more detail on the failing component, as described in the HYPERVISOR_ERROR documentation.
    2. Check for known hypervisor/CPU issues
      • 0x20001 has been seen when the hypervisor fails during early initialization of a VM or when running certain instructions on specific Intel CPUs under Hyper‑V. In those cases, the fix has been delivered via Windows updates to the hypervisor.
      • Since the issue started after a recent upgrade and only affects the newer Intel Core Ultra platform, focus on:
        • Latest Windows updates (including any optional quality updates that may contain hypervisor fixes).
        • Latest firmware/BIOS for the motherboard/CPU.
        • Latest Intel chipset and platform drivers from the OEM.
    3. Hyper‑V and virtualization settings
      • If Hyper‑V, Memory Integrity (HVCI), or other virtualization‑based security features are enabled, temporarily disable them to see if X‑Plane runs without triggering 0x20001. This can help isolate whether the crash is tied to the hypervisor path.
      • If disabling these features stops the crashes, keep them off only as a diagnostic step and then look for updated drivers/firmware that allow running with them enabled.
    4. Driver and device compatibility
      • HYPERVISOR_ERROR can be triggered by low‑level drivers that interact with virtualization (e.g., GPU, security, or system‑level drivers). Ensure all such drivers are fully up to date from the hardware vendor.
      • If the problem started immediately after a specific driver update package, roll back just that driver (via Device Manager) rather than removing the entire Windows update, and test.
    5. Avoid blind removal of system updates
      • Because 0x20001 is a hypervisor‑level failure, removing a cumulative update without knowing whether it contains critical hypervisor fixes can make stability or security worse.
      • Use the dump analysis to identify whether a particular driver or module is implicated before uninstalling updates.

    If, after updating BIOS/firmware, chipset, GPU, and other low‑level drivers, and after testing with Hyper‑V/VBS features disabled, the system still consistently hits 0x20001 only on this CPU, the next step is to provide the crash dumps and system details to Microsoft support so they can analyze the hypervisor failure path for this specific platform.

    References:

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

    Was this answer helpful?

    2 people found 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.