Windows 10 is gone. What the ESU invoice is really telling you

The bill isn't the problem. It's a message about how the decision got deferred — and a preview of the next one.

Somewhere in your January accounts payable, there may be a new line item: Microsoft Extended Security Updates for Windows 10. If it's there, it's worth a closer look — not because of what it costs this year, but because of what it says.

Windows 10 support ended October 14, 2025.1 Machines still running it can stay patched through Microsoft's ESU program at $61 per device for the first year. The price doubles each year after that — $122, then $244 — for a maximum of three years.2 After October 2028, there is no fourth year at any price.

For a company with 400 devices still on Windows 10, that's roughly $24,000 this year, $49,000 next year, $98,000 the year after. About $170,000 total — to stand still.

Here's the thing: paying for ESU is not a failure. In plenty of situations it's the right call — a fleet refresh that couldn't land before Q4, an application that certifies late on Windows 11, an acquisition that arrived with 200 unexpected laptops.

ESU is a bridge. The question — the only question — is whether there's a plan on the other side of it.

If your team can tell you which devices are covered, why each one is still on Windows 10, and the quarter each one exits the program, then the invoice is just the cost of a deliberate schedule. If the answer is "we'll get to it," the invoice is rent on a decision nobody has made yet. And the rent doubles annually — that pricing isn't an accident; it's Microsoft telling you the bridge has an end.

The pattern behind most ESU invoices is simple: the project was scheduled from the front. "We'll start the Windows 11 migration when the team has capacity." Capacity never came; the date did anyway.

The discipline that prevents this is working backward from the published date. Every migration has a real duration — procurement, imaging, application testing, the long tail of stragglers. Subtract that from the end-of-support date and you get a start-by date. Miss the start-by date and the outcome is already determined; everything after that is just choosing which penalty to pay.

That's the methodology we built into EOL Radar: the products mid-market stacks most commonly run, their retirement dates, and the date you'd need to start by to exit cleanly. (If the vocabulary itself is fuzzy — EOL versus EOS versus end of extended support — the plain-English guide covers what actually stops at each date.)

If a board member asks "why are we paying Microsoft for an operating system they've discontinued?", here's the honest version:

If your team can't fill in that bracket, that's the real finding — and it applies to a lot more than Windows 10. SQL Server 2016, Windows Server 2016, and a long list of other platforms have their own dates already published and their own start-by dates approaching.

The invoice was the reminder. The calendar is the fix.