Microsoft outlines limitations of Windows 10 on ARM compared to on x86: no initial support for 64-bit apps, Hyper-V, or certain app classes, and no x86 drivers
For over a year we've been treated to the fantasy that Windows 10 on ARM was the same as Windows 10 on x86. But it's a bit more nuanced than that.
Context & Ripple Effects
Thurrott's piece punctures the marketing line that Windows on ARM devices run 'the same' Windows as x86 machines: at launch they lack 64-bit app support, Hyper-V, certain app classes, and any x86 drivers, so compatibility depends entirely on what has been recompiled or emulated. The related coverage shows how long the gap took to close — Microsoft began accepting 64-bit ARM apps into the Store and updated Visual Studio for native recompiles within months of this piece, but full x64 emulation was only promised in late 2020.
The endgame matters more than the gap itself: when Microsoft finally shipped an x64 emulation preview for Insiders, it also decided that only Windows 11 would get x64 emulation on ARM, leaving Windows 10 devices permanently behind. This 2018 limitations list is therefore the origin point of a split that still defines ARM PCs today.
First-order effects
- Early ARM PC buyers get a machine that cannot run 64-bit Win32 apps, Hyper-V VMs, or peripherals needing x86 drivers — the practical burden falls on them to check app-by-app compatibility before purchase.
- Developers targeting these devices must recompile Win32 apps natively via the updated Visual Studio toolchain or ship 32-bit versions, since nothing else runs.
Second-order effects
- The missing 64-bit story forces Microsoft down the emulation path it resisted at launch — first native ARM64 Store acceptance, then the x64 emulation commitment — making emulator quality the de facto compatibility contract for ARM hardware.
- Peripheral and driver vendors gain a new porting requirement: without x86 driver support, ARM laptops are effectively locked to hardware with ARM-native drivers, narrowing the accessory ecosystem around those devices.
Third-order effects
- If the pattern holds, ARM/x86 feature parity becomes a version-gating lever rather than a given — as happened when only Windows 11 was granted x64 emulation, turning OS upgrades into the price of full compatibility on ARM silicon.
- Structurally, Windows splits into two tiers of device capability — fully compatible x86 machines and increasingly capable but perpetually caveat-carrying ARM machines — with Microsoft's toolchain and emulator roadmap deciding which tier each generation lands in.
The trend: Windows on ARM is converging toward x86 parity through native recompiles and emulation, but Microsoft is reserving each new compatibility layer for its latest OS version, making ARM readiness a reason to upgrade rather than a baseline.