Is Microsoft Doing Enough to Push IE Upgrades?

While analyzing recent client analytical data, I noticed some intriguing trends regarding browser versioning. Unlike other metrics which remain relatively stable across projects, browser adoption tells a story of fragmentation. The majority of the market is split between Internet Explorer 6 and 7, with Firefox trails as a strong alternative.

However, the most telling data comes from breaking down the versions within each browser family.

The Adoption Data

In a sample set of 1,000 unique visitors, here is the breakdown of specific version usage within each browser’s user base:

• Firefox:
  • 85.75% are on Version 2.0.0.14 (Current Stable)
  • 5.75% are already on Version 3.0 (Released just last week)
• Internet Explorer:
  • 62.27% are on Version 7.0
  • 36.17% are still on Version 6.0
• Safari:
  • Fragmented across 525.18, 419.3, etc.

The “Update Gap”

The disparity in adoption rates is stark.

• IE6 was released in August 2001.
• IE7 was released in October 2006.

Despite being available for over 18 months, IE7 has only managed to convert about 62% of the IE user base. A massive 36% are still clinging to a browser from 2001, despite its well-documented security holes and lack of standards support.

Contrast this with Firefox. Firefox 2 was released around the same time as IE7 (Oct 2006). It holds an 85% share of its user base. Firefox 3, released just days ago, has already captured nearly 6% of the base.

The Strategy Flaw: System vs. Application

Why is Microsoft failing to upgrade its users? I believe the issue lies in how the update is presented.

Since Microsoft treats IE as a core component of Windows, updates are delivered via Windows Update. This frames the new browser as a “System Patch” or an “Operating System Change.” Users are often wary of system updates—they fear breaking their OS, piracy checks (WGA), or forced reboots. The prompt “There is a new browser available, would you like to install it?” feels like a sales pitch coming from the OS kernel.

Key competitors treat the browser as a standalone application. When Firefox says, “I have a new version, would you like to update?”, it feels like a natural evolution of the tool. It’s an active, friendly request from the application itself, promising better features and security, rather than a heavy system overhaul.

Rethinking Distribution Strategy

Microsoft needs to rethink its distribution strategy. Treating the browser as an inextricable part of the OS (a legacy of the “Browser Wars”) is now hindering their ability to keep users secure and up-to-date.

Bill Gates has shifted strategies frequently, but one principle should remain constant: User Centricity. If the update process is seamless and beneficial to the user, adoption will follow. If it feels like a bureaucratic system mandate, users will stagnate on legacy versions—holding back the entire web in the process.

Update: LinuxInsider recently published a similar analysis discussing the browser update dilemma.