The Windows Hypervisor Platform fails to be enabled on my Microsoft Surface Laptop 4, why is that??

Stanleon Exaud 0 Reputation points
2026-08-25T23:13:49.37+00:00

I have tried creating a virtual device in my Android studio but once installed the Windows Hypervisor Platform shows its not enabled, when trying enabling it, it prints out an error as follows " Failed to enable WHPX: Unknown error (code: -2147018095). Please consult the IDE log (Help | Show Log). "

I have tried with the Windows features on or off, but whenever trying to turn on the Hyper V , Virtual Machine Platform, windows hypervisor platform, they all print out the same error as follows " Transaction support within the specified resource manager is not stated or was shut down due to an error Error code; 0x80071A91 "

how can i fix this so i can proceed with my android studio?

Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
0 comments

2 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Hoang Le 4,580 Reputation points Independent Advisor
    2026-08-26T02:41:15.3733333+00:00

    Hello Stanleon Exaud,

    The error 0x80071A91 indicates corruption in the Windows Transaction Manager (TxF) resource manager, which prevents enabling features like Hyper‑V, Virtual Machine Platform, and Windows Hypervisor Platform. This is not an Android Studio issue but a Windows subsystem failure. The supported fix is to reset the Transaction Manager state. Run an elevated command prompt and execute:

    fsutil resource setautoreset true C:\

    This forces Windows to reset the TxF log on the system drive. After reboot, retry enabling the Hyper‑V and WHPX features via OptionalFeatures.exe or PowerShell (Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All). If the error persists, check sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair component corruption. Only once the Transaction Manager is healthy will WHPX load correctly and Android Studio’s emulator be able to use hardware acceleration.

    If my answer is useful for you, please hit Accept the answer to support me.

    Thank you,

    HL.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

  2. AI answer

    2026-08-25T23:14:15.82+00:00

    For Android emulators on Windows, WHPX/Hyper-V is the recommended acceleration path on supported x64 Windows systems. On a Surface Laptop 4, virtualization is already enabled on Surface devices at the firmware level, so the practical checks are in Windows features and Hyper-V state.

    Use this sequence:

    1. Verify the device is supported
      • Android Emulator requires x64 and is not supported on Windows ARM devices.
      • Surface Laptop 4 is not in the Windows ARM examples listed in the documentation, so the main issue is likely Windows feature state rather than device architecture.
    2. Check whether Hyper-V support is available
      • Open Command Prompt and run: 
             systeminfo
      • If all Hyper-V Requirements show Yes, the device can support Hyper-V.
      • If the output says a hypervisor is already running, Hyper-V is already enabled.
    3. Check whether Hyper-V and WHPX are actually enabled in Windows
      • Open Windows PowerShell as Administrator.
      • Run: 
             Get-WindowsOptionalFeature -FeatureName Microsoft-Hyper-V-All -Online
     Get-WindowsOptionalFeature -FeatureName HypervisorPlatform -Online
      • If either feature shows State : Disabled, enable them with: 
             Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
     Enable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform -All
      • Reboot after the commands complete.
    4. Confirm Android Emulator acceleration prerequisites
      • The emulator uses hardware acceleration only when:
        • hardware acceleration is available and enabled, and
        • the virtual device uses an x86-64 or x86 system image.
      • If the AVD was created with a different architecture, recreate it with an x86-64 image.
    5. Check emulator acceleration directly
      • Run: 
             "C:\Program Files (x86)\Android\android-sdk\emulator\emulator-check.exe" accel
      • If it reports VT feature disabled in BIOS/UEFI, that points to firmware virtualization settings. Surface devices already have virtualization enabled, so that result would indicate a broader Windows configuration problem.
    6. If another virtualization product is installed, check for conflicts
      • Third-party virtualization applications such as VMware and VirtualBox cannot run alongside Hyper-V, Memory Integrity, or Credential Guard.
      • If another virtualization stack is active, it can interfere with the Android emulator path being used.
    7. If the goal is Android Emulator with WHPX, do not disable Hyper-V
      • Disabling Hyper-V is only the workaround for running third-party virtualization apps that conflict with it.
      • For Android Emulator on Windows, the documented preferred path is WHPX/Hyper-V.

    About the specific 0x80071A91 failure: the provided documentation does not include that Windows feature servicing error code, so the supported next step is to verify feature state with the PowerShell commands above rather than relying only on the Windows Features UI.

    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.