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

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.

• How to enable hardware acceleration with Android emulators (Hyper-V & AEHD)
• How to enable hardware acceleration with Android emulators (Hyper-V & AEHD)
• Android emulator troubleshooting
• Enable Virtualization on Windows
• Virtualization applications don't work together with Hyper-V and Hyper-V-based features