What happens when the world’s most widely used desktop operating system runs out of road and a large share of its users simply decline to move? Microsoft is finding out in real time, and the answer is messier than any upgrade roadmap suggested. Windows 10 holdouts are not a fringe group of tinkerers clinging to old habits. They include home users with perfectly capable laptops, small offices with a handful of aging desktops, and large organizations with software tied to specific configurations.
Microsoft ended free security updates for most Windows 10 users on October 14, 2025, and plenty of PCs kept booting anyway.
That gap between a corporate deadline and what people actually do is the story. An end-of-support date works as a threat only if the threatened party believes the consequences will arrive quickly, and for most Windows 10 users nothing visibly breaks on day one. The machine still opens spreadsheets, the browser still loads, and the printer still prints. The risk is real but invisible, which makes it easy to postpone, and postponement has become the default behavior of an entire installed base.

The Hardware Wall Nobody Wanted to Climb
The core of the standoff is that Windows 11 is not a simple software swap for everyone. Microsoft set firm hardware requirements when it launched the system in 2021, including TPM 2.0 support, Secure Boot capability, and a list of supported processors that excludes a wide band of older chips. Those rules were framed as a security baseline, and the logic holds up on paper: hardware-backed protections make certain classes of attack harder. But a security baseline is also a cutoff line, and plenty of PCs landed on the wrong side of it despite running Windows 10 without complaint.
Consider the owner of a laptop bought a few years before Windows 11 appeared. It has a solid-state drive, enough memory, and a screen that still looks fine. The Windows 11 compatibility checker tells that owner the machine does not qualify, and the only official fix is to buy a new computer. From the owner’s side, nothing about the device has changed except Microsoft’s opinion of it.
That perception matters more than the technical justification. People tend to resist upgrades that feel like a bill rather than a benefit, and a forced hardware purchase is about as clear an example as exists. Workarounds that bypass the requirements circulate widely, which tells you how many people are trying to avoid the expense, but they come with their own risks, including the possibility that Microsoft declines to deliver updates to unsupported installs. The result is a population stuck between a system that is no longer maintained and one it cannot officially run. Every month that population stays large, it weakens the argument that the requirements were reasonable.
Microsoft’s Paid Lifeline Changes the Math
Microsoft did not leave holdouts entirely on their own. It offered an Extended Security Updates program that, for consumers, runs for one year past the cutoff and ends on October 13, 2026. Individuals could enroll by syncing their PC settings to a Microsoft account, by redeeming Microsoft Rewards points, or by paying a one-time fee of about $30. Businesses face a steeper structure, with per-device pricing that starts around $61 in the first year and escalates in later years for organizations that need more time.
The design of that offer is worth reading closely. The free route requires a Microsoft account and cloud backup, which means the program quietly nudges users toward services Microsoft wants them to adopt anyway. It is a bridge, but one with a toll that is paid in data and account loyalty rather than cash. Users in the European Economic Area got a version without the account-sync requirement, an exception that makes the standard terms look more like a business decision than a technical necessity.
Even so, a one-year extension is a delay rather than a resolution. A household that enrolls this year faces the same question next autumn with fewer options, and a company that pays per device is effectively renting time to finish a migration it may not have budgeted for. Some holdouts are looking elsewhere, including Linux distributions, ChromeOS Flex on older hardware, and third-party micropatching services that promise to cover gaps after official support ends. None of these is a painless swap for a user whose workflow depends on specific Windows applications. They do show that Microsoft’s grip on the installed base loosens when it asks people to pay for hardware they do not feel they need.

Enterprise IT departments carry a different kind of burden. They must weigh the cost of replacing fleets of machines against the cost of paying for extended coverage, and they must do it while testing line-of-business software that may never have been validated on a newer system. A migration that looks simple in a slide deck can stretch across many months once legacy applications, peripheral drivers, and compliance reviews are involved. Each of those delays is rational on its own, yet together they produce the very holdout population that makes Microsoft’s timeline look optimistic.

The Deadline That Comes Next
The ESU window closes on October 13, 2026, and every Windows 10 machine still in service that day will be running without a safety net, on hardware that has not gotten any newer.









