Windows on Arm in 2026: 26H1, 26H2 and what actually runs
Arm64 Windows in 2026: the 26H1 new-device branch, 26H2 annual release, Prism x86/x64 emulation, kernel-driver limits and a buying checklist.
- Build
- 28000.1 / 26300
- Edition
- 26H1 / 26H2
- Architecture
- arm64
- Support
- Documentation (E1)
- Evidence
- E1Official documentation
- Verified
- 2026-10-28
- Page type
- Platform
The short answer
Section titled “The short answer”Windows on Arm is a real Windows 11 platform, not a tablet side branch. It runs native Arm64 apps, x64 apps through Prism, and x86 apps through the WOW64 layer. It does not run x64 kernel drivers. That single sentence decides most compatibility questions.
The version story is also easy to get wrong in 2026:
| Version | Build | GA | Role |
|---|---|---|---|
| 26H1 | 28000 | 2026-02-10 | New devices that shipped in early 2026; not an in-place update from 24H2/25H2 |
| 26H2 | 26300 | 2026-09-29 | The 2026 annual update for existing PCs |
| 25H2 | 26200 | 2025-09-30 | Previous annual release; still supported |
Do not tell a Snapdragon X owner to “upgrade to 26H1” as if it were the next annual release. 26H1 is a device-scoped branch. Check the device’s supported release before comparing build numbers.
What Prism does
Section titled “What Prism does”Prism is the emulator that ships with Windows 11 24H2 and later. It translates x86/x64 user-mode instructions to Arm64, caches translated blocks, and is tuned for Qualcomm Snapdragon processors. It is available on supported Arm devices, but some optimisations need Snapdragon X hardware features.
What that means in practice:
- Most browsers, Office, media apps and many games run under emulation.
- Performance varies by app. A native Arm64 build is the best case; an x64 build under Prism is the common case; a kernel driver is the failure case.
- Anti-cheat is the usual blocker. If the anti-cheat ships a kernel driver, it must have an Arm64 build. “The game is x64” is not enough.
- Printers, VPNs, capture cards and audio interfaces may have no Arm64 driver. Check the vendor, not the Windows compatibility list alone.
Compatibility checklist
Section titled “Compatibility checklist”| Question | Why it matters | Where to check |
|---|---|---|
| Is there a native Arm64 build? | Best performance and battery life | Vendor download page / app manifest |
| Is it x64 under Prism? | Usually runs; performance may be lower | App vendor, Windows-on-Arm compatibility lists |
| Does it install a kernel driver? | Kernel drivers must be Arm64 | Anti-cheat, VPN, hardware vendor |
| Does it need a browser extension or Store component? | Some components are x64-only | Vendor support page |
| Is the device driver available for this exact model? | Arm devices are less standardised | OEM support page |
The community-maintained OnArm.net database is useful for a first pass, but it is not a vendor guarantee. A “works” entry can be months old and tied to a different driver or game patch.
Buying an Arm laptop in 2026
Section titled “Buying an Arm laptop in 2026”Ask these before paying:
- Which apps are mission-critical? Check each one for an Arm64 build or a credible x64-under-Prism report.
- Which peripherals? Docking station, printer, capture card, MIDI interface, security key.
- Which games? Check anti-cheat vendor support, not just the game’s system requirements.
- How much RAM? Emulation and a browser plus WSL can make 16GB feel small; 32GB is the safer developer configuration if it is soldered.
- Which Windows release does the OEM support? 26H1 vs 26H2 matters for driver packages and support.
What this page does not decide
Section titled “What this page does not decide”- Whether a specific game runs: check the anti-cheat vendor and the game’s Arm statement.
- Whether an x64 app is “fast enough”: only a measured run on the exact device answers that.
- Whether Arm is better than x64: it depends on the workload, the native app availability and the drivers.