Problem solve Get help with specific problems with your technologies, process and projects.

Windows XP end of support: What are the risks for users?

As the Windows XP end of support nears, see what IT admins should do to prepare for the end of life of Microsoft's venerable OS.

In 2010, Dimensional Research surveyed more than 950 IT professionals about their plans for Windows XP after Microsoft...

stops supporting the operating system in April 2014. Of those who responded, 48% claimed that they would continue using the product. According to an IDC report released almost two years later, only 11% of Microsoft's commercial clients will be running Windows XP. That report, however, was sponsored by Microsoft and involved only nine organizations. Even if the IDC projections are accurate, many enterprises will still be running XP-based systems in 2014, and doing so could prove to be risky business.

Losing Microsoft's Windows XP support at the end of life

After Microsoft ends support of Windows XP, it will no longer provide software updates for the operating system (OS). Of greatest concern are the security fixes that protect against malware such as viruses and worms. According to Microsoft's Security Intelligence Report, Windows XP Service Pack 3 (SP3) -- the only version still receiving security updates -- is over twice as vulnerable to infections as the 32-bit version of Windows 7 SP1 and nearly three times as vulnerable as the 64-bit version. Without security updates, Windows XP will become increasingly vulnerable. Cybercriminals may step up their attacks after the Windows XP end of life.

And it's not just the lack of security patches that causes IT to lose sleep. Operating system updates also improve reliability and keep hardware running properly. But after April 2014, those protections are gone, along with per-incident support services and hotfix agreement support. Windows XP might seem stable today, but in just over a year that stability might be little more than a memory.

Lagging behind technology

Productivity and technology have become nearly synonymous, as seen in the trend toward consumerization. Windows XP was developed to run on hardware manufactured a dozen years ago and to interact with technologies from that same era. Software and hardware are now much faster and more efficient, but Windows XP can't take complete advantage of them. For example, XP can't fully exploit the memory capabilities of today's PCs.

More about migrating from XP to Windows 7

What to do as the Windows XP lifecycle end nears

There's still time to plan for a Windows 7 migration

Learn how to deploy Windows 7's XP Mode on a new PC

Troubleshoot errors in Windows XP

Why Windows 7 could be your last desktop migration

In addition, computers now support features such as high-resolution monitors, touchscreen functionality, faster USB ports, and integrated Bluetooth and Wi-Fi. In many cases, Windows XP doesn't natively support such features, or its support is limited. When compared with an OS that takes full advantage of hardware's capabilities, an XP-based system can translate into lost productivity, particularly for users accustomed to the modern interfaces found in their home systems and mobile devices.

By continuing to run Windows XP, enterprise IT also faces diminishing support and availability of third-party hardware and software. Before long, peripherals will not include compatible drivers, and new products or updated versions of existing products will not run in Windows XP. That might be fine for an organization planning to run its systems exactly as they exist today, without doing any software or hardware upgrades, but even this approach is nothing more than a temporary solution.

For example, Mozilla announced that Firefox 12 will be the last version of its Web browser to support Windows XP editions prior to SP3, so most XP users are safe for now. But what happens when Firefox and other browsers no longer support SP3? Internet users will be putting their systems at greater risk because the browsers won't be receiving current updates, and those users cannot take advantage of new Web technologies that require updated browser features.

Rising operating costs

The IDC report also concluded that running Windows XP can cost five times more to manage than running Windows 7, a pronouncement Microsoft happily jumped on in evangelizing a move to the newer OS. But the report makes another valid point. Windows XP usually runs on older machines, and the combination of aging hardware and a 12-year-old OS can increase the need for support resources and contribute to downtime and lost productivity.

According to the report, the annual cost to support a Windows XP-based PC averages $870, compared with $168 for a Windows 7 system. Even if the differences are not so extreme in your organization, the costs associated with supporting older systems cannot be ignored. And once Microsoft has pulled its support, those differences are likely to increase because more time will needed to protect those systems, keep them running and integrate newer technologies.

End of the line for Windows XP

Ready or not, come April 8, 2014, Microsoft will execute the Windows XP lifecycle end. By sticking with the OS, some enterprises are putting their systems at greater risk, sacrificing stability, minimizing productivity and incurring higher operating costs.

In addition, organizations that stick with Windows XP might have problems standardizing systems or addressing compliance issues that might arise as a result of running an unsupported OS.

To be sure, upgrading an enterprise to a new OS and whatever equipment is necessary to support that upgrade is no small task and could require a significant investment. Not all legacy applications and hardware can make the transition. Windows migration efforts never run as smoothly as everyone hopes, and some organizations might be able to make a case for sticking with the OS past the Windows XP end of support.

In most situations, however, holding on to the legacy OS could prove to be a liability. Carefully analyze the potential costs and risks. Careful planning for a Windows upgrade needs to happen today, not two years down the road.

Dig Deeper on Windows legacy operating systems

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

There is so little real truth in this article that I'm not surprised by the lack of reader comments to such a critical IT development. XP is everywhere from POS registers to industrial control systems to custom embedded platforms, so the end of XP support makes these highly reliable devices vulnerable simply because Microsoft can make more money by forcing these users to make unneeded & unwanted changes. This is simply IT churn, and the "native support" argument is something that one would expect from a Microsoft sales rep looking to lubricate a "deal" when the reality is that well-understood, fine tuned, and highly reliable legacy systems serve their owner's line of business interests "just fine, thank you very much". If you're car stopped working because your car manufacturer simply abandoned support for its onboard computer and insisted that you buy a new car for all of its new "features", you would be the first one to say that your current car has been working just fine and that you'd rather not invest the money & time to solve a transportation problem that was created solely by your car's manufacturer. My guess is that the hundreds of millions of XP users in the world would gladly pay a small annual premium for Microsoft programmers, who are thoroughly familiar with XP source code, to keep it security patched until their legacy devices are totally used up & decommissioned. That amount of cashflow would satisfy most businessmen who would be happy with recurring revenue from a product that was delivered a decade ago, but not Microsoft. For Microsoft, enormous profits are realized from forced market churn in lockstep with loyal hardware manufacturers, and from stonewalling the desires of its customers. When M$ needs more revenue, they simply raise CAL prices, even during a recession. Only a near monopoly can do this, and it is a testament to the lack of FTC anti-monopoly enforcement that M$ has been allowed to grow this arrogant and powerful. While the EU has become increasingly intolerant of M$ monopolistic business practices, here in America our regulators bow to the lobbying pressures and look the other way. Now that the Fiscal Cliff is looming large on the economic recovery horizon, forced IT churn spending may turn out to be a luxury that many user organization can't afford - regardless of bogus TCO reports from M$ cheerleaders.
When update support finishes I will permanently disconnect my XP machine from the internet. I will use it to play old games which do not run properly on windows 7. I still have two other machines that run 7 and 8.
Business who uses a computer for business?
The main points of this post are well-taken, but there are many more technical, operational, and management considerations. I've just published two white papers to provide more depth.

1) How To Pull The Windows Migration Trigger: Five Questions Every CIO Must Ask

A successful Windows migration is not just a technical challenge – it requires a focused management approach to get priorities, timing, and resources right. This white paper explains how to manage migration risks and act on critical success factors.

2) Windows Migration Tips, Tricks, And Gotchas
Olenick & Associates shares tips about how to plan, prepare, and conduct a Windows migration for a large number of PCs.

These reports reflect lessons learned in supporting migration of over 40,000 XP PCs.

We do have a dog in this fight - our Assured Windows Migration solution

The data sheet for this is

Hope this helps,
Bob Binder