# Windows on Arm in 2026: Arm64, Prism, 26H1 and 26H2

> What Windows on Arm is, how native Arm64 and Prism emulation differ, why 26H1 and 26H2 are separate branches, and how to check whether your apps and games actually run.

**Tested on**

- Build: 26H1 / 26H2
- Edition: Arm64
- Architecture: arm64
- Evidence: E1
- Risk: R0
- Verified: 2026-10-28

## The short answer

Windows on Arm is **full Windows 11 compiled for Arm64**, not a mobile OS and not “Windows Lite”. It runs the same desktop, the same browsers and the same Microsoft Store. The question that decides whether it works for you is not “is Arm fast?” but **“does my specific software run, and does it need a kernel driver?”**

Three things explain almost every surprise:

1. **Native Arm64 vs Prism emulation.** Most apps run; some run translated; a small set cannot run at all.
2. **Drivers are native-only.** Prism emulates user-mode code, not kernel drivers. VPNs, endpoint security, printers and some game anti-cheat are the usual blockers.
3. **26H1 and 26H2 are different branches.** 26H1 is a chip-enablement release for new Arm devices; 26H2 is the annual update for existing PCs on 24H2/25H2.

> **Note: No Arm hardware in this lab**
>
> This page is **E1**: Microsoft documentation plus the OnArm.net compatibility database. The lab has x64 PVE VMs, not a Snapdragon or RTX Spark device, so there is no E2 performance, battery or install claim here. Treat the page as a buying and compatibility guide, not a benchmark.

## What is actually different

| Layer | x64 PC | Windows on Arm |
|---|---|---|
| CPU instruction set | x86-64 | Arm64 |
| Windows build | x64 Windows 11 | Arm64 Windows 11 |
| Native apps | x64 | Arm64 |
| Old x86/x64 apps | Run directly | Run through **Prism** emulation |
| Kernel drivers | x86/x64 drivers | **Arm64 drivers only** |
| Firmware | UEFI + TPM 2.0 | UEFI + TPM 2.0 (device-specific) |

“Arm64” is the 64-bit Arm architecture. The Windows desktop, Store, Win32 APIs and most of the management stack are the same; the machine code underneath is not. That is why an Arm laptop can feel like Windows one minute and like a compatibility project the next.

## Native, emulated, or blocked

| Bucket | What it means | What it feels like |
|---|---|---|
| **Native Arm64** | The app ships a build compiled for Arm | Best speed and battery; no translation warm-up |
| **Emulated (Prism)** | An x86/x64 build is translated at runtime | Usually fine for office, chat and bursty tools; sustained work costs more |
| **ARM64EC hybrid** | Arm64 core plus x64-compatible parts in one process | Common during a vendor’s migration; Task Manager shows “ARM64 (x64 compatible)” |
| **Blocked** | Kernel driver, kernel anti-cheat, or unsupported dependency | No emulation trick fixes it; choose different software or hardware |

Prism is **user-mode** emulation. It cannot load an x86 kernel driver into an Arm kernel. That single rule explains most “the app installs but the VPN/anti-cheat/printer utility does not work” reports.

## 26H1 vs 26H2: don’t read the number as “newer”

Microsoft split the 2026 releases. They are not two versions of the same upgrade path.

| | Windows 11 26H1 | Windows 11 26H2 |
|---|---|---|
| What it is | Arm-focused chip-enablement release | Annual feature update for existing PCs |
| Who gets it | Select new Arm devices; Snapdragon X2 at launch | Devices on 24H2 / 25H2, including older Snapdragon X Elite |
| How it arrives | Preinstalled on new hardware | Small enablement package, usually one restart |
| Upgrade path | Cannot update in place to 26H2; Microsoft says a path to a future release is coming | Normal annual update path |
| Compatibility model | Same native Arm64 + Prism model | Same native Arm64 + Prism model |
| Pick it because | You are buying a device that ships with it | You are updating an existing Arm PC |

Microsoft’s 26H1 post is explicit: 26H1 is **not** a feature update for 25H2, is **not** offered as an in-place update from 24H2/25H2, and devices on it **will not be able to update to the next annual feature update in the second half of 2026** because it is based on a different Windows core. That is a platform branch, not a quality ranking.

So:

- **Do not avoid a 26H1 device because “26H2 is newer”.** Check the device’s support path and your app list.
- **Do not expect a 26H1 laptop to upgrade to 26H2.** It will keep receiving monthly security, quality and feature updates on its branch.
- **Do not call 26H2 “the Arm version”.** Both branches are Arm64 on Arm hardware.

## Drivers are the hard boundary

Before buying, check these in order:

1. **VPN client** — corporate VPNs are the classic Arm trap. The client installs a kernel driver, so it needs an Arm64 build.
2. **Endpoint security / antivirus** — Windows Defender is native; a company-mandated third-party agent may not be.
3. **Printers, scanners, audio interfaces, dongles** — standard printing often works through Windows’ built-in stack; vendor utilities and exotic peripherals need Arm64 drivers.
4. **Games with kernel anti-cheat** — Easy Anti-Cheat and BattlEye have Arm64 clients, but each game must enable them. Kernel-level anti-cheat is the blocker to verify per title.
5. **Your one weird tool** — the bank security plug-in, the time tracker, the legacy ERP client. That is the one to test before the return window closes.

Windows Update can supply some drivers, but it is not a guarantee. If the vendor only ships an x86 driver, the device is not supported on Arm, regardless of how well the app itself emulates.

## Games: check the anti-cheat, not just the frame rate

Emulated games can run, but competitive titles are a separate question. The catalog record should tell you:

- whether the game launches at all;
- whether it is native Arm64 or x86/x64 under Prism;
- whether its anti-cheat has an Arm64 client **enabled for that game**;
- when the result was last verified.

A “works on Arm” video for a single-player game does not transfer to a kernel anti-cheat shooter. Check the specific title and the anti-cheat status before buying.

## Development and creative work

Native builds matter most under sustained load: large compiles, video encoding, 3D rendering, local AI. Many developer tools have Arm64 builds, but the long tail is real:

- **Native:** mainstream editors, Git, runtimes and many CLI tools.
- **Emulated:** older toolchains, vendor-specific SDKs, x64-only plug-ins.
- **Blocked:** tools that install kernel drivers, virtualisation components or hardware dongle drivers.

If your workflow depends on a specific VM stack, GPU compute stack or audio plug-in, verify that exact version on Arm before switching. “The app runs” is not the same as “the plug-in runs inside the app”.

## Buying checklist

| Check | Why it matters |
|---|---|
| Must-have apps, by exact name | “Most apps run” is not a compatibility statement for your apps |
| VPN and security agents | Driver-based; the most common hard blocker |
| Printer/scanner/audio interface | Vendor utility may be x64-only even if basic printing works |
| Games and anti-cheat | Per-title enablement, not a platform-wide yes |
| Dev toolchain and VM stack | Emulation is fine for bursty tools, painful for sustained workloads |
| RAM and SSD | Many Arm laptops solder RAM; buy the capacity you will need |
| Display, keyboard, ports | You cannot upgrade most of it later |
| Return window | The only real test is your software on the device |

NPU TOPS and “Copilot+ PC” labels are **not** compatibility guarantees. They describe AI acceleration, not whether your VPN client or printer driver exists.

## Installing Windows on Arm

Use the **Arm64 ISO**, not the x64 ISO. Microsoft publishes Windows 11 Arm ISO files for virtual machines, in-place setup and bootable media. In practice:

- Many Arm laptops ship with a recovery image; use the OEM recovery path first.
- A clean install needs Arm64 storage, network and input drivers; if Setup cannot see the disk, load the OEM driver.
- An ordinary x64 PC cannot natively boot the Arm64 image. Arm virtual machines need an Arm host or an emulated environment, which is outside this page.
- Do not follow the x64 [clean install guide](https://winbook.fyi/en/windows/install/clean/) on an Arm device. The partitioning concepts are similar; the media and drivers are not.

## How to check a specific app

The fastest path is a compatibility database, not a forum thread. On Windows itself, Task Manager can tell you how a running app is executing:

1. **Ctrl + Shift + Esc** → **Details**.
2. Right-click a column header → **Select columns** → **Architecture**.
3. Read **ARM64**, **x64**, **x86**, or **ARM64 (x64 compatible)**.

That tells you what is running now. It does not tell you whether a different app will work before you buy. For that, use the per-title database below.

## OnArm.net: the per-app answer

[OnArm.net](https://onarm.net/) is a separate, independent Windows on Arm compatibility database. Its About page describes one job: answer **“does this Windows app or game run on an Arm PC?”** It is not Microsoft, and it is not this site’s lab data; it is a third-party reference we link to for title-level checks.

At the time of writing (2026-10-28), its public counts are:

| OnArm.net | Value |
|---|---|
| Titles tracked | **9,215** (7,768 apps, 1,447 games) |
| Native Arm64 | **2,319** |
| Runs on Arm | **9,177** |
| Publishers | **3,390** |
| Languages | **9** (en, zh, zh-Hant, ja, ko, es, pt, fr, de) |
| Data source | Linaro `works-on-woa` (MIT), plus official package facts and reviewed community reports |

Counts change with every refresh. Check [onarm.net/stats](https://onarm.net/stats) for the current numbers rather than quoting these forever.

### What it is good at

- **Pre-purchase checks.** Search the exact app or game; see native/emulated/no and the minimum version with Arm support.
- **Anti-cheat.** A dedicated [anti-cheat page](https://onarm.net/anti-cheat) tracks per-game EAC/BattlEye/Vanguard status, which is more useful than a generic “games run” claim.
- **Devices and chips.** [Devices](https://onarm.net/devices) and [chips](https://onarm.net/chips) map the Snapdragon X/X2 and NVIDIA RTX Spark landscape.
- **Guides.** Practical pages on [native vs emulated](https://onarm.net/guides/native-vs-emulated), [buying checklist](https://onarm.net/guides/arm-pc-buying-checklist), [Prism](https://onarm.net/guides/prism-emulation-explained) and the [26H1/26H2 split](https://onarm.net/guides/windows-arm-history).
- **Machine-readable data.** A public [JSON API](https://onarm.net/api/projects.json), [llms.txt](https://onarm.net/llms.txt) and RSS feeds; useful if you want to build your own checklist or monitor changes.

### How to read a record

Do not stop at the green “works” badge. Read four fields:

1. **Runtime verdict** — native, emulated, or no.
2. **Last tested** — a dated device report. If it is empty, there is no dated test; that is not the same as “verified today”.
3. **Build evidence** — the package architecture, source, version and observation date. A Store listing that is architecture-neutral is not proof of an Arm64 build.
4. **Scope** — the Windows version, device and app version. A result for one Snapdragon generation is not a guarantee for every Arm PC.

OnArm.net is explicit that package availability does not override a runtime failure, and that discovery dates are not release dates. That is the right level of caution for a compatibility database.

### What it is not

- **Not a benchmark.** “Runs” does not mean “runs at your frame rate” or “matches native battery life”.
- **Not a warranty.** Drivers, app versions and Windows builds change; a record can age.
- **Not this site’s E2 evidence.** We link to it; we do not relabel its data as our lab result.
- **Not a substitute for the return window.** For a expensive machine, test your own must-have software.

> **Tip: Use the two pages together**
>
> This page explains the platform trade-offs and the 26H1/26H2 branch. OnArm.net answers the per-title question. A good buying flow is: read this page → list your must-have apps → check each one on OnArm.net → test the device before the return window closes.

## What this page does not claim

| Claim | Status |
|---|---|
| 26H1 is Arm-focused chip enablement; 26H2 is the 24H2/25H2 annual update | E1, Microsoft 26H1 post + 26H2 Learn |
| Prism is user-mode emulation; kernel drivers need Arm64 builds | E1, Microsoft Learn + OnArm guides |
| Per-title compatibility counts | E1/third-party, OnArm.net as of 2026-10-28 |
| Battery life, frame rate, compile time | **Not measured**; no Arm device in the lab |
| Clean install on a specific Arm laptop | **Not tested**; OEM recovery/drivers vary |

## Related pages

- [Which Windows 11?](https://winbook.fyi/en/windows/start/versions/) — 26H2, 25H2, LTSC and ARM64 at a glance.
- [Clean install Windows 11 26H2](https://winbook.fyi/en/windows/install/clean/) — x64 clean install; not the Arm media path.
- [First 10 minutes](https://winbook.fyi/en/windows/start/first-hour/) — applies to Arm too, but check Arm64 drivers first.
- [Gaming measurement](https://winbook.fyi/en/windows/gaming/measure/) — measure before trusting a “fast on Arm” claim.

## Sources

- [Microsoft Tech Community — What to know about Windows 11, version 26H1](https://techcommunity.microsoft.com/blog/windows-itpro-blog/what-to-know-about-windows-11-version-26h1/4491941)
- [Microsoft Learn — What's new in Windows 11, version 26H2](https://learn.microsoft.com/en-us/windows/whats-new/whats-new-windows-11-version-26h2)
- [Microsoft Learn — Arm64EC for Windows 11 apps on Arm](https://learn.microsoft.com/en-us/windows/arm/arm64ec)
- [Microsoft Learn — Windows 11 Arm ISO files](https://learn.microsoft.com/en-us/windows/arm/iso)
- [Microsoft Learn — Adjust emulation settings on Arm](https://learn.microsoft.com/en-us/windows/arm/apps-on-arm-program-compat-troubleshooter)
- [OnArm.net — Windows on Arm compatibility database](https://onarm.net/)

---

Source: https://winbook.fyi/en/windows/platform/arm64/