Windows 9 Akamai analytics reveal which features users actually open

When Microsoft pushed an unfinished build of its next operating system to Windows Update servers in October 2014, the leak spread across the globe within hours. Telemetry hosted through Akamai quietly recorded how testers interacted with the preview build, painting an unusually candid picture of feature engagement. By the time Microsoft confirmed the slip and began the formal Insider programme, the data already offered a window into user behaviour that official surveys would never match.

Australian testers were among the quickest to grab the build due to curiosity and the country's eager enthusiast community. Downloads spiked in Sydney and Melbourne as users east of Perth woke to news shared across forums. Local participants across Australia, New Zealand and the wider Asia-Pacific region helped shape the early telemetry pool simply by clicking through menus faster than many other regions.

The build itself carried references to Akamai's content delivery network, and the resulting analytics script reported back which dialogs, settings panels and applets were actually opened by end users. While Microsoft scrubbed the build from its servers, the data captured during that brief window became a talking point for anyone watching the road to Windows 10. The picture it painted was less flattering than the marketing videos suggested.

How the Akamai build leaked through Windows Update servers

The Technical Preview that surfaced in October 2014 was meant to remain private. It appeared as an optional update through Windows Update for users enrolled in an undisclosed developer ring. Akamai's role was incidental; the build referenced content delivery endpoints that allowed Microsoft to track download counts, but the same infrastructure also logged telemetry from the running operating system.

Once installed, the preview phoned home using a familiar pattern of beacon requests routed through Akamai's edge servers. Each feature opened in the new Start menu, every settings page visited, and even certain Control Panel applets generated a small analytical ping. Insiders running the build in Brisbane coffee shops and Adelaide home offices contributed to the dataset without realising their clicks were being catalogued.

The official Windows 9 Insider programme launched shortly afterwards, formalising the telemetry relationship. Microsoft noted the pattern of feature use in the leaked build and prioritised polish on the most popular surfaces. Analysts studying the leaked dataset could see which corners of the new interface users visited first.

Features Australians actually opened in the leaked build

Among the dozens of surfaces in the preview, only a handful accounted for most user interactions. The Start menu overhaul, the modernised Settings app and the virtual desktop controls were the three clear winners. Users spent proportionally little time with the returning Start screen tiles or the new task view animations, suggesting Microsoft had misjudged which elements would feel fresh.

The Continuum-style tablet mode toggle drew attention from hybrid device owners who switched between laptop and tablet postures. Australians who tested the build on Surface Pro devices and similar convertibles used the toggle far more often than their American counterparts, likely because the local market has embraced 2-in-1 hardware for university and design work. Action Centre and the notification system ranked surprisingly low despite being heavily marketed in the preview footage.

The data also revealed that users opened File Explorer far more often than the new OneDrive-centric file picker, suggesting that despite Microsoft's push toward cloud storage, local file management remained dominant. Searches through the charms bar were heavily used in the first hour but dropped sharply within a day.

Most opened surfaces in the leaked build

Tracking through Akamai's CDN and what it meant for privacy

Akamai's role in the leak was technical rather than editorial. The company operates caching points of presence, including nodes across Sydney, Melbourne and Perth that serve Australian customers with reduced latency. When the preview build phoned home, those requests landed on Australian Akamai edges before being aggregated and forwarded to Microsoft's backend systems.

The underclass blog coverage noted that telemetry pings were unencrypted on certain code paths, raising eyebrows among privacy researchers in Australia and abroad. Local commentators pointed out that even minimal feature-usage telemetry, combined with IP addresses, could fingerprint individual households. Microsoft responded by tightening encryption on subsequent Insider builds and clarifying its data retention policy.

For ordinary users, the episode was a reminder that preview software rarely behaves like a finished product. Every click, settings panel visit and accidental keystroke in the new search charm contributed to a dataset Microsoft engineers used to shape the final release. Australians who care about digital sovereignty watched closely, mindful of pending data retention legislation.

Local patterns in Australian test behaviour

Australian testers behaved differently from the global average in several measurable ways. They spent more time per session in the Settings app, partly because of regional setting differences. Melbourne and Sydney accounted for the largest share of Australian telemetry, with Perth contributing a smaller slice.

Time zone differences mattered. Australian testers in AEST woke to the leak several hours ahead of the US East Coast, giving them a longer window of uninterrupted exploration before Microsoft pulled the build. Australian data points therefore dominated the first eight hours of telemetry. The pattern showed up clearly in Akamai's hourly aggregation graphs.

Local ISPs such as Telstra, Optus and TPG peered with the Akamai edges used for the telemetry endpoints, keeping latency low and ensuring that the Australian sample was not skewed by connectivity issues. This made the Australian dataset unusually clean and representative of how a well-connected household would use the operating system.

Distinct Australian patterns in the leaked telemetry

What the data predicted for the final Windows 10 release

The leaked telemetry offered a rough blueprint for the final release. The Start menu redesign survived largely intact, the modernised Settings app became the default gateway for most configuration tasks, and virtual desktops were showcased in marketing material. Features that attracted little attention, such as the new task view animations, were quietly downplayed.

Microsoft also used the data to retire ignored features. The traditional desktop tile mode, which had appeared as an option in the leaked build, was eventually removed. The notification system received a quiet redesign based on observed usage patterns, with quick action buttons repositioned after telemetry showed they were rarely clicked.

The episode remains a case study in how inadvertent analytics can shape a software release. For readers following Windows 9 coverage, the leak offered a rare moment of transparency in an industry that usually guards usage data closely. Australian testers, who had contributed disproportionately to the early dataset, could claim a role in shaping the operating system that eventually shipped as Windows 10.