The First ARM-Based Windows RT Devices Arrive

Windows RT devices went on sale October 26, 2012 alongside Windows 8, led by Microsoft’s Surface RT ($499 for 32GB, $599 for 64GB, with the Type Cover keyboard sold separately at $129). ASUS, Dell, Lenovo, and Samsung also launched Windows RT tablets the same day. All ran on ARM processors — primarily the NVIDIA Tegra 3 quad-core at 1.3 GHz in most devices including Surface RT — rather than the x86 CPUs that had defined Windows PCs since the early 1980s. The ARM chips offered better power efficiency: Surface RT quoted ten hours of battery life vs. roughly five to six hours on contemporary x86 Windows 8 ultrabooks.

Windows RT included a touch-optimized version of Office 2013 Home & Student (Word, Excel, PowerPoint, OneNote) — a significant inclusion — and a locked desktop that ran only Microsoft-signed software. Third-party developers could ship applications through the Windows Store as WinRT apps compiled for ARM, but the existing catalog of hundreds of thousands of x86 Windows applications would not install or run. This was not a limitation Microsoft communicated clearly in retail stores: the Surface RT looked almost identical to the Surface Pro announced the same day, which ran full Windows 8 on an Intel Core i5 and could run any existing Windows software.

Microsoft took a $900 million inventory write-down on unsold Surface RT tablets in July 2013, acknowledged poor sales, and dropped the price from $499 to $349 the same month. Windows RT 8.1 shipped in October 2013 but without the ability to upgrade from Windows RT — a logistical problem that further alienated early buyers. Microsoft discontinued Windows RT with no successor; the platform’s successor was Windows 10 on ARM, not launched until 2017 on Qualcomm Snapdragon hardware. The episode presaged Apple’s M1 transition in 2020, which succeeded where Windows RT had failed by maintaining full x86 application compatibility through the Rosetta 2 translation layer.

Why This Moment Mattered

The topic is useful because it captures a broader shift in how people build, use, and understand technology. In the short term, it gave users and developers something concrete to react to. In the longer term, it became part of a larger pattern in software, programming, and computing history: hardware, software, services, and user expectations were all changing at the same time.

A good technology milestone usually matters for more than one audience. Enthusiasts notice the specifications or the interface first. Developers ask what new assumptions they can make. Companies look at cost, compatibility, and strategy. Ordinary users mostly notice whether the result makes their devices faster, easier, safer, or more useful.

The Broader Context

This period of computing was shaped by several overlapping transitions: faster networks, more capable mobile devices, cloud infrastructure, stronger security expectations, and software that changed continuously after release. Against that background, the milestone was not an isolated headline. It was one piece of a much larger movement away from static products and toward connected platforms.

That context helps explain why some announcements that looked modest at the time became important later. A browser feature, processor change, development tool, or platform policy can alter what future products are able to assume. Once enough users, developers, and vendors adapt, the new assumption becomes normal.

Looking Back

The value of revisiting the moment is that it shows how technology history is built from many medium-sized steps. Some are celebrated immediately, while others become meaningful only after the ecosystem catches up.

Looking back also keeps the story balanced. Progress usually brings tradeoffs: performance against power use, openness against consistency, convenience against control, and speed against stability. The most interesting milestones are the ones that reveal those tradeoffs clearly. This one belongs in that category because it helps explain not just what changed, but why the direction of computing kept moving the way it did.