Share via

Hyper-V on Microsoft Surface failed to boot

Safet P 0 Reputation points
2026-03-04T23:07:44.3366667+00:00

Good afternoon, everyone! I am working with a Surface Laptop 7, which has the new Snap Dragon 64-bit ARM-based processor, and I upgraded to Windows 11 Professional in order to enable Hyper Visor. I have enabled HyperVisor, virtual machines, however, every time I try and run a Windows 10, it automatically attempts to load over PXE over IPv4, ignoring the boot sequence that I have programmed. Additionally, I have tried to adjust the firmware to ignore secure boot, and I am still running into the same issue on all the distributions I am using. Looking to see if anyone else has experienced the same issues or recommends any fix actions. Thanks!

Surface | Surface Laptop | Install and update
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. S.Sengupta 29,426 Reputation points MVP Volunteer Moderator
    2026-03-04T23:36:34.46+00:00

    On ARM-based Windows hosts (like the Snapdragon X processors), Hyper-V VMs behave differently compared to Intel/AMD hosts. A common symptom reported by others is that the VM never boots from ISO/VHD/VHDX and jumps directly to PXE boot because it doesn’t detect a valid bootable device or isn’t using a compatible boot media.

    Make sure the ISO or VHDX is an ARM64 build (either Windows on ARM or a Linux ARM64 release). x86/x64 ISOs won’t boot on an ARM Hyper-V host.

    On Hyper-V Manager for ARM machines, you must use a Generation 2 VM (UEFI) — ARM Hyper-V doesn’t support Generation 1 on these devices.

    Firmware > Boot Order: DVD drive / Virtual hard disk first, network adapter last.

    Secure Boot: Try both on and off.

    You may consider alternatives like WSL2 or ARM-friendly hypervisors for Linux needs.

    0 comments No comments

  2. Q&A Assist
    2026-03-04T23:08:01.6866667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    On Surface Laptop 7 with Snapdragon (Windows on Arm), Hyper-V can run only Arm-based guest operating systems. x64 Windows 10 or other non-Arm distributions cannot boot as VMs and will typically fall back to PXE/network boot, which matches the behavior described.

    Key points and actions:

    1. Guest OS architecture
      • Windows on Arm hosts support only Arm/Arm64 guest OS images.
      • A standard x64 Windows 10 ISO will not boot as a Hyper-V guest on this device, regardless of boot order or Secure Boot settings.
      • Use a Windows 11 on Arm ISO instead of Windows 10 x64 if testing Windows guests. See the Windows on Arm ISO guidance for creating media.
    2. Use correct Windows on Arm media
      • Obtain a Windows 11 Arm ISO as described in the Windows 11 Arm ISO overview.
      • Attach that ISO to the Hyper-V VM and boot from it.
      • For devices with Snapdragon X Series processors (such as Surface Laptop 7), the VM can boot from the ISO without additional drivers, but full functionality in a physical install requires drivers from Windows Update.
    3. Secure Boot and firmware
      • Surface Laptop 7 supports Secure Boot and virtualization out of the box; virtualization is already enabled on Surface devices and Secure Boot is supported on Arm-based Surface.
      • Disabling Secure Boot in firmware is not required to run supported Hyper-V guests and will not make x64 guests work on an Arm host.
    4. Deployment/boot tooling notes
      • Surface Laptop 7 supports Network Boot (PXE) and Operating System Deployment, but those apply to physical deployment, not to bypassing the Arm-only limitation for Hyper-V guests.

    To resolve the issue, create new Hyper-V VMs using Arm-compatible operating systems (for example, Windows 11 on Arm) instead of Windows 10 x64 or other non-Arm distributions. The PXE-over-IPv4 fallback will persist as long as the attached boot media is not a valid Arm64 boot image.


    References:

    0 comments No comments

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.