Microsoft Moved the Windows 10 Deadline in a Footnote. Even We Missed Four Pages.

By Scott Bissett  ·  Published: September 9, 2026  ·  EOL Watch — news analysis  ·  Verified against Microsoft's Extended Security Updates page and end-of-support page on September 9, 2026

Yesterday Microsoft shipped the largest Patch Tuesday it has ever released. BleepingComputer's count for September 8, 2026 was 966 fixes, 105 of them rated Critical, including two vulnerabilities already being exploited: CVE-2026-81963 in the Windows Update Stack and CVE-2026-85880 in the Advanced Local Procedure Call subsystem, both added to CISA's Known Exploited Vulnerabilities catalog on September 8, 2026. A Windows 10 PC received every one of those fixes, or none of them, depending on a single question: is it enrolled in Extended Security Updates.

Which makes the second fact matter. The date most people still quote for the end of Windows 10 consumer ESU is wrong. The program was announced as a single year, ending in October 2026. On June 25, 2026 Microsoft extended it to October 12, 2027, and did so not with a press release but with an editor's note appended to a Windows Experience Blog post published the day before, and a quiet edit to the ESU page. We caught it that week. We corrected most of our pages. Four of them kept saying the opposite, in the present tense, for 76 days, until this morning. This is the story of how a lifecycle date drifts, told on the one site whose entire job is to stop that happening.

What actually changed

Microsoft's ESU page now carries two sentences that settle it. “You can enroll in ESU any time until the program ends on October 12, 2027,” and “Windows 10 devices enrolled in the ESU program will continue to receive critical and important security updates through October 12, 2027.” The three enrollment routes are unchanged and each covers the whole program: syncing PC settings at no cost, redeeming 1,000 Microsoft Rewards points, or a one-time purchase of US$30. Devices already enrolled do nothing; the extension applies to them automatically.

The dates in the lifecycle-table rows are rewritten from the data layer at every build. The consumer date is not in any lifecycle table, which is the whole problem, and the next section explains what we did about that.

How a lifecycle date drifts

A date moves when a vendor changes its mind. It drifts when the change is made somewhere the copies do not look. Microsoft's Windows 10 end-of-support date is in its lifecycle table, in endoflife.date, in every tracker, and in ours; when it moves, everything downstream moves with it. The consumer ESU date lives in none of those places. It is a marketing-page fact: it appears on the ESU page and the end-of-support page, and Microsoft's Learn lifecycle table, which does carry the commercial ESU years, does not list the consumer program at all. So when the extension arrived as a footnote, there was no feed to carry it. Every copy of the old date that had been typed by a person stayed exactly where that person left it.

That includes ours. We track more than 500 products, and for the dates that come from a vendor table or from endoflife.date we do not type anything: the build reads the source, rewrites the number on the page, and fails if a sentence disagrees with the data. The consumer ESU date was the exception. It had been typed into prose, in the present tense, on the pages that most needed it to be right.

What we got wrong, specifically

We had the fact. The Windows 10 decision guide carried a dated correction from July; the migration guide, the Surface article, the Office article and the mid-year report all stated October 12, 2027. The pages that were missed were the ones written before the change and never re-read, plus one written after it by copying an older page's framing. A sweep run the night after the record Patch Tuesday flagged them, because it compared what our pages said against what Microsoft's pages said that day. They were corrected within the hour. That is the honest version, and it is the reason this article exists rather than a quiet edit.

The fix that outlasts the fix

Correcting four pages is not a fix; it is the same hand-typing that failed. The fix is that the consumer ESU date now exists in exactly one place in our data, and three things hang off it.

• Every sentence that states the date is registered. Seven claims across the corrected pages are checked at each build against that single value. A sentence that drifts from the data fails the build.
• The value is checked against Microsoft at each build. The build fetches Microsoft's ESU page and requires it still to say “October 12, 2027.” If Microsoft moves the date again, whether by press release or by footnote, the next build fails loudly instead of the site serving a stale date for another 76 days.
• The page you are reading is under the same rule. Every consumer ESU date in this article is one of those claims. If you are reading it after Microsoft has changed the program and it still says October 12, 2027, the build is red and we are working on it.

This is the pattern we apply to every number on the site: never state a date that nothing checks. How we verify our dates describes the rest of it.

What to do today

Home or small-office Windows 10 PC, not enrolled: enroll. Settings, Update & Security, Windows Update carries the enrollment prompt on 22H2. The free route is to sync your PC settings; the alternatives are 1,000 Rewards points or the one-time US$30 purchase. Until you enroll, yesterday's 966 fixes, two of them for flaws already being exploited, are not on your machine. After you enroll, Critical and Important updates arrive through October 12, 2027.

Enrolled already: nothing to do. Microsoft's page says enrolled devices continue to receive updates through October 12, 2027. Check Windows Update shows the September updates installed; if it does not, the enrollment did not complete.

Organizations: the extension is for personal devices. Commercial ESU still runs a year at a time. The first year ends in October 2026, on the same Patch Tuesday that Windows 11 24H2 Home and Pro reach end of support (October 13, 2026), and year two must be bought. The October 13 article lays out the three clocks that day, now with the consumer clock removed from it.

Anyone quoting a Windows 10 date: check it against our Windows page, where the lifecycle-table dates are reconciled at every build, and against the Windows 10 guide, whose consumer date is now bound to Microsoft's page. If a source still says the consumer program ends in 2026, it was written before June 25 and never re-read. We know the feeling.

Frequently Asked Questions

Related

• Windows — every version and servicing channel with live status, reconciled against Microsoft's lifecycle table
• Windows 10 End of Life: the migration guide — the ESU table, prices, and how to tell which build you are on, now corrected
• Windows 10 after end of life: upgrade, buy time, or replace — the decision guide, which carried the July correction
• October 13, 2026: three Windows support clocks — the commercial deadlines that day, with the consumer clock now removed
• How we verify our dates — the rules every number on this site is held to