Rufus is the go-to tool for bootable USB drives, and it handles ARM64 Windows 11 media just fine — when everything is set correctly. But “Rufus made my USB and the Snapdragon laptop ignores it” is a common complaint, and the causes are almost always in the settings or the source ISO rather than in Rufus itself.

The failure modes are specific: wrong architecture ISO, wrong partition scheme, a dying USB stick, or Secure Boot rejecting the result. Each produces a slightly different symptom, and this guide maps symptoms to fixes across six sections.

Why this happens

  • x64 ISO selected instead of ARM64: Rufus happily writes whatever ISO you give it. An x64 Windows ISO on the USB will never boot on ARM hardware, and nothing in Rufus warns you about the mismatch.
  • MBR partition scheme on a UEFI-only laptop: ARM laptops boot UEFI exclusively. A USB written as MBR/BIOS is invisible to the boot menu.
  • Failing or counterfeit USB drive: Cheap or worn-out flash drives develop bad blocks mid-write. The USB appears to complete but the data is corrupt, failing unpredictably during boot or install.
  • Secure Boot policy conflicts: The official ARM64 ISO is signed and boots with Secure Boot on. Third-party or modified images may be rejected — a sign the image is not what it claims to be.
  • Rufus write mode confusion: For Windows ISOs Rufus uses its standard ISO mode; picking DD mode or the wrong options can produce unbootable media on some systems.
  • USB port or hub issues during writing: Writing through a flaky hub or a loose port corrupts the image. The write “succeeds” but verification would fail.
  • Antivirus interfering with the write: Overzealous security software can quarantine Rufus’s boot files mid-write, leaving half-written media — the same class of interference that makes launchers crawl on ARM .

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Confirm you have the ARM64 ISO

Before blaming Rufus or the USB, verify the source image. This single check resolves the majority of “won’t boot on Snapdragon” reports.

  1. Locate your ISO file, right-click it, and check the filename for an ARM64 marker — if it says x64 or amd64, it is the wrong image.
  2. If wrong, download the correct ARM64 ISO from Microsoft’s Windows 11 download page , selecting ARM64 as the architecture.
  3. Verify the download with Get-FileHash -Algorithm SHA256 against Microsoft’s published hash — a corrupt ISO wastes every subsequent step.
  4. For the full walkthrough of getting the right image, see the ARM64 ISO download guide .
  5. Only open Rufus once the verified ARM64 ISO is on disk. Everything below assumes the image is correct.

Fix 2: Use the correct Rufus settings for ARM64 UEFI

With the right ISO, the settings are simple — but each one matters. One wrong dropdown produces unbootable media.

  1. Insert your USB drive (8GB minimum, USB 3.0+ recommended) and open Rufus — run it as administrator to avoid permission issues during writing.
  2. Under Device, select your USB drive. Double-check the drive letter — Rufus will erase the selected drive completely.
  3. Click SELECT and choose your verified ARM64 ISO.
  4. Set Partition scheme to GPT and Target system to UEFI (non CSM). Do not use MBR.
  5. Leave File system and Cluster size at Rufus’s defaults for the ISO, keep Quick format checked, click START, and wait for the green “READY” bar — do not remove the drive early.

Fix 3: Rule out the USB drive itself

When correctly-configured media still fails, suspect the flash drive. Bad drives are more common than people think, especially older ones.

  1. In Rufus, enable the Check device for bad blocks option (click the arrow next to Format Options to reveal it) and set it to at least 1 pass before your next write.
  2. If bad blocks are found, retire the drive — do not try to work around them for OS installation media.
  3. Try a different USB drive, preferably a known-good USB 3.0+ stick from a reputable brand, and rewrite the image.
  4. Write the USB plugged directly into the computer — not through a hub or dock — to eliminate connection issues during the write.
  5. After writing, test-boot the USB on any available UEFI machine (even an x64 one will show the Windows Setup screen from ARM64 media? No — it won’t boot on x64. Instead, verify by booting the target ARM laptop). The real test is always the target machine.

Fix 4: Handle Secure Boot and boot-menu issues

Correct media that the laptop ignores is usually a boot-configuration issue, not a media issue.

  1. Plug in the USB and power on while tapping the boot-menu key (F12 on many models; Esc/F9 or Volume Down + Power on others).
  2. Look for the USB entry with a UEFI: prefix and select it. If no USB entry appears, enter UEFI setup (F2/Del) and confirm USB boot is enabled in the boot options.
  3. Leave Secure Boot enabled — the official Microsoft ARM64 image is signed and boots fine. Disabling Secure Boot is not the fix and weakens the machine’s security posture.
  4. If Secure Boot rejects the media with a security violation, the image is almost certainly not the official Microsoft ISO — return to Fix 1.
  5. As a sanity check, try the USB in a different port — preferably a direct laptop port rather than a dock or hub port.

Fix 5: Deal with antivirus and permission interference

If Rufus throws errors mid-write or the resulting USB is missing files, something on the writing machine is interfering.

  1. Temporarily disable real-time protection in your antivirus during the Rufus write, then re-enable it immediately after.
  2. Always run Rufus as administrator — right-click the executable and choose Run as administrator.
  3. Close other disk tools (partition managers, other USB writers) that might lock the drive.
  4. If Windows shows “access denied” on the drive, open Disk Management, confirm the drive is online and has no strange partition locks, then retry.
  5. After a clean write with interference removed, re-verify by booting the target ARM laptop — do not assume the previous failure mode persists.

Fix 6: Alternative tools and final verification

If Rufus itself seems to be the problem — rare, but possible with very new or very old versions — alternatives exist, and a final verification pass catches anything missed.

  1. Update Rufus to the latest version from its official site — USB and ISO handling improves regularly, including ARM64 edge cases.
  2. As an alternative, try balenaEtcher or the Windows Media Creation Tool’s ARM64 path; different tools have different failure modes, and one may succeed where another stalls.
  3. After creating media with any tool, boot the ARM laptop from it and confirm the Windows Setup screen appears — that is the only verification that matters.
  4. If setup starts but fails during installation, the issue is no longer the USB — check the target disk’s health and the ISO verification from Fix 1.
  5. Keep the working USB labeled and stored safely; and remember that driver issues after installation — like AMD Adrenalin/Ryzen AI driver problems or AMD XDNA2 NPU driver issues on Ryzen AI laptops, or heavy apps crashing — are post-install concerns, not USB-creation problems.

Closing

Rufus ARM USB failures are configuration failures, not tool failures: the wrong ISO architecture, the wrong partition scheme, or a bad flash drive. Verify the ARM64 image, use GPT/UEFI settings, write directly to a healthy USB 3.0+ drive as administrator, and the Snapdragon laptop will boot it.

Frequently asked questions

Why won't my Rufus USB boot on my Snapdragon laptop?
The three usual causes are: the ISO is x64 instead of ARM64, the partition scheme is MBR instead of GPT/UEFI, or Secure Boot is rejecting the media. Verify the ISO architecture first — it’s the most common mistake.
Which Rufus settings should I use for ARM64 Windows 11?
Select the ARM64 ISO, set Partition scheme to GPT and Target system to UEFI (non CSM). Rufus handles the rest automatically, including splitting the large install.wim if the USB is FAT32.
Does Rufus work on ARM64 Windows itself?
Yes — Rufus runs on Windows 11 on ARM (via ARM64 or emulated x64 builds) and can create ARM64 bootable media. You can build the USB drive directly on the Snapdragon laptop if needed.
What USB drive size do I need?
At least 8GB for the Windows 11 ARM64 ISO. Use a reputable USB 3.0+ drive — slow or counterfeit drives cause write errors and corrupt media that fails halfway through installation.