Share via

Hyper-V on Microsoft Surface Laptop 7

Safet P 0 Reputation points
2026-03-04T23:03:56.7033333+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

1 answer

Sort by: Most helpful
  1. Q&A Assist
    2026-03-04T23:04:10.67+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 (Arm64), the behavior is expected: PXE/network boot is supported at the device/firmware level, but Hyper‑V guest OS support is limited by Windows on Arm and by what the Arm platform is intended for.

    Key points from the platform capabilities:

    1. Surface Laptop 7 is an Arm-based Surface device
      • It uses a Snapdragon Arm64 processor and runs Windows 11 on Arm.
      • Windows on Arm is primarily designed to run native Arm64 apps, emulated x86/x64 apps, and to host Arm64-based workloads.
    2. Hyper‑V and PXE behavior on this device
      • Network Boot (PXE) is supported on Surface Laptop 7 at the hardware level, which is why PXE over IPv4 appears as a boot path.
      • However, the Windows on Arm platform and Arm-based Surface devices are documented and validated mainly for:
        • Windows Autopilot and image-based deployment
        • Management via Intune/Configuration Manager
        • Security features (BitLocker, Secure Boot, Defender, etc.)
      • There is no documented support in the provided material for running general-purpose Linux VMs under Hyper‑V on Windows 11 on Arm on Surface Laptop 7.
    3. What this implies for Linux VMs
      • The documentation focuses on deployment and management of the Arm-based Surface device itself, not on guest OS support in Hyper‑V.
      • Linux distributions would need Arm64 Hyper‑V integration and boot support tailored for Windows on Arm Hyper‑V, which is not covered or guaranteed here.
      • The repeated PXE boot attempts and ignoring of the configured boot order are consistent with a guest that cannot find a valid bootable medium/bootloader in a supported format, so the VM falls back to network boot.
    4. Practical guidance
      • For Arm-based Surface devices such as Surface Laptop 7, supported and recommended scenarios are:
        • Use Windows Autopilot or image-based deployment for the host OS.
        • Use Windows Subsystem for Linux (WSL) for Linux workloads instead of full Hyper‑V Linux VMs.
      • WSL is explicitly supported and is the preferred way to run Linux userland on these devices.

    Given the documented scope, the reliable path for Linux on Surface Laptop 7 (Snapdragon/Arm64) is WSL rather than Hyper‑V Linux VMs. The PXE‑only behavior seen when starting Linux VMs is a limitation of guest support on this platform, not something that can be corrected by changing Secure Boot or VM boot order.


    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.