Surface Laptop for Business 13.8" (Snapdragon) - Windows 11 ARM64 USB won't boot

OmRam 0 Reputation points
2026-07-16T13:27:38.3233333+00:00

I am testing USB installation media on a Surface Laptop for Business 13.8" (Snapdragon).

The official Surface Recovery Image works fine. I can boot from the USB and reinstall Windows without any issues.

However, I can't get a regular Windows 11 ARM64 USB installer to work.

I have tried:

  • Official Windows 11 ARM64 ISO from Microsoft
  • Rufus-created USB
  • FAT32 USB with install.wim split into .swm files
  • FAT32/NTFS partition combinations

The USB starts booting, shows the Windows logo, and then either loops or never gets to Windows Setup.

Surface | Surface Laptop | Install and update
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. S.Sengupta 32,016 Reputation points MVP Volunteer Moderator
    2026-07-17T00:42:21.34+00:00

    Boot into Surface UEFI (Volume Up + Power) → Security → Secure Boot Control → Disable. Try the same USB again. If it suddenly works, you've confirmed it's a cert/trust issue, not a partition/media issue.

    Use a plain FAT32 whole-USB — just extract the ISO contents straight onto a single FAT32 USB with install.wim under 4GB, or split via dism /split-image the standard way and confirm \EFI\BOOT\BOOTAA64.EFI sits at the USB root's EFI\BOOT folder.

    Confirm firmware is fully up to date via Windows Update/Surface app before testing — since this device is right in the window of the 2023 CA rollout, an older firmware build may simply not trust the newer boot manager yet, and a firmware update could resolve it outright.

    Several people with this exact Surface Laptop 7/Snapdragon combo report better luck with Ventoy's native ISO passthrough than with Rufus's DD/ISO modes, though results are mixed.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-07-16T13:28:03.74+00:00

    This behavior is expected on some Arm devices when using a generic Windows 11 Arm64 installer.

    For Surface devices, the recommended path is to use the Surface Recovery Image instead of building a generic USB installer. The recovery image includes the correct drivers already tested for the specific device.

    For Windows on Arm media in general:

    1. Create the USB from the Arm64 ISO with Rufus.
    2. Do not use Media Creation Tool for Arm64 bootable media, because it does not currently support creating Arm64 bootable media.
    3. On Arm devices, boot success can depend on having the correct manufacturer drivers in the installation media.

    For Snapdragon X Series devices:

    • The device can boot from an ISO and install Windows without extra manufacturer drivers.
    • Full functionality is not available until the remaining drivers are installed from Windows Update, typically by connecting Ethernet through a dongle or dock and then rebooting.

    For earlier Snapdragon generations:

    • Drivers from the device manufacturer must be injected into the image.
    • Without those drivers, the device might fail to boot or boot into a state where input is non-functional.

    For the Surface Laptop for Business 13.8" (Snapdragon), the supported and reliable approach is the one already validated: use the official Surface Recovery Image. Since that media boots correctly and the generic Arm64 USB loops before Windows Setup, the practical conclusion is that the generic media is not providing what the device firmware or setup path needs, while the Surface recovery media does.

    If continuing to test custom media:

    1. Use Rufus with the official Windows 11 Arm64 ISO.
    2. Ensure USB boot is enabled in UEFI/BIOS.
    3. If needed, temporarily disable Secure Boot to test USB boot. This changes device security posture, so re-enable it after testing.
    4. If the image is larger than FAT32 limits, splitting install.wim into .swm files is a valid method, but that only addresses file-size limits and does not add missing device-specific drivers.

    The key point is that splitting the image or changing FAT32/NTFS layout solves media-format constraints, not Surface-specific driver requirements. On Surface hardware, the recovery image remains the recommended installation media.

    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.