The editorial frames the quiet page update as a tacit admission that Microsoft's original ESU friction — Microsoft account requirement, Rewards points, or $30 fee — was politically unsustainable after EU DMA pressure carved out the EEA. With Windows 10 still at ~53% of desktop Windows share and a TPM 2.0 hardware wall blocking in-place upgrades, forcing the installed base off-patch was never viable, so Microsoft collapsed consumer friction to zero without a press release.
The piece highlights that enterprise ESU pricing still doubles annually starting at $61/device, while consumers — including indie devs and small shops not on volume licenses — now get a free year. This preserves Microsoft's commercial revenue stream while defusing the consumer backlash, shifting the calculus dramatically for anyone running a handful of Windows 10 machines outside a corporate license.
The Neowin headline 'Windows 10 quietly gets one more year of support and updates' emphasizes that Microsoft updated the ESU enrollment page with no press release, blog post, or Ignite-stage moment. The framing suggests Microsoft wants the concession to reach users who need it without publicly admitting the original paid/account-gated program was a misstep.
Microsoft updated its Windows 10 Extended Security Updates (ESU) enrollment page with a change it conspicuously did not announce: consumers in the EEA — and, per the current wording, effectively anyone enrolling through the consumer flow — can now receive ESU through October 13, 2026 at no cost, with no requirement to sync settings to a Microsoft account, redeem 1,000 Microsoft Rewards points, or pay the previously advertised $30 one-time fee.
The official Windows 10 end-of-support date hasn't moved — October 14, 2025 is still the line — but the cost and friction of staying patched for another year just collapsed to zero. When the consumer ESU program was first detailed in mid-2024, Microsoft made enrollment deliberately annoying: a Microsoft account requirement, a Rewards-points alternative, or cash. EU regulators leaned on the account requirement under the Digital Markets Act, and Microsoft initially carved out the EEA. The quiet page update appears to extend that carve-out's spirit much further, without a press release, blog post, or Ignite-stage moment.
The enterprise ESU pricing — which doubles each year, starting at $61 per device for year one — is unchanged. So is the commercial cliff. What changed is the consumer track, and by extension the calculus for indie devs, small shops, and anyone running a handful of Windows 10 machines that aren't on a volume license.
Windows 10 is not a rounding error. StatCounter still puts Windows 10 at roughly 53% of desktop Windows installs globally as of mid-2026 — more than Windows 11, despite four years of upgrade nags and a TPM 2.0 hardware wall that left a meaningful fraction of the installed base unable to upgrade in place. That hardware wall is the whole story here. Microsoft can ship all the upgrade prompts it likes; it cannot retroactively put a TPM 2.0 chip in a 2017 Dell. Forcing 500M+ devices to either e-waste or run unpatched was always going to be a political problem, and the EU made it an actual one.
The pattern is familiar to anyone who watched Windows 7's ESU saga: stated end-of-life, paid extension for enterprise, eventual quiet softening for the long tail. The interesting wrinkle this time is the speed. Windows 7 ESU ran a full three years (2020–2023) and was enterprise-only on day one; consumer ESU for Windows 10 is one year and started free in practice before the cutoff even hit. The EU regulatory environment, plus a market where Apple and ChromeOS are credible alternatives in ways they weren't in 2020, is doing real work here.
The community reaction on HN has been notably unsentimental. The top comments aren't celebrating; they're asking the obvious operational question: what does Microsoft do in October 2026, when the same TPM-locked hardware is still in the field and the same regulators are still watching? The base case is another quiet extension. The bear case is that Microsoft uses the extra year to ship a more aggressive AI-PC upsell — Copilot+ requirements, on-device NPU floors — and treats the eventual cutoff as a feature, not a bug. Neither base case nor bear case argues for migrating in panic.
There's also a developer-tooling angle that's underdiscussed. Electron, Tauri, .NET, Python — every framework that ships a Windows installer has a 'minimum supported Windows version' policy, and those policies were quietly being rewritten around the October 2025 EOL date. Node 22's Windows 10 support story, the Edge WebView2 runtime's deprecation timeline, .NET 10's TFM targeting — all of it was calibrated to a world where Windows 10 was unsupported by end of 2025. That calibration is now wrong by a year for a majority of the Windows install base.
If you ship a desktop app to consumers or SMB on Windows: your 'we're dropping Windows 10' deadline just moved from Q4 2025 to Q4 2026, and your users now have a free, official path to stay patched in between. Pulling Windows 10 support in 2025 was defensible six months ago. Pulling it now, while Microsoft itself is shipping security updates for free, will look hostile to a meaningful chunk of your install base. Re-check your minimum-version policy before the next release notes.
If you run a small fleet — startup laptops, lab machines, your parents' computer — enroll them in consumer ESU now, while the free path is documented. The mechanism is a settings-page toggle that backfills a Microsoft license entitlement; it costs nothing, requires no account-binding, and buys a year of CVE patches. The downside is zero. The upside is not having to do an emergency hardware refresh in January when some Patch Tuesday CVE goes public.
If you run an actual enterprise fleet: nothing changed for you. ESU pricing is still $61/device/year, doubling annually. The consumer extension does not bleed into volume licensing. But the deadline pressure on your migration project just got quieter, and that's exactly the moment migration projects start slipping. If your Windows 11 rollout was running on the 'October 2025 or we're unpatched' narrative, you need a new narrative this week, or your steering committee will defer the project into 2027 and you'll inherit the resulting hairball.
The interesting question isn't whether Microsoft extends again in October 2026 — they probably will, in some form, because the math hasn't changed and the regulators haven't gone away. The interesting question is whether 'Windows 10' becomes the new 'Windows 7': officially dead, practically immortal, quietly patched, and a stable target for desktop developers for the rest of the decade. Bet accordingly when you set your installer's minimum version.
What even is Microsoft's strategy? Windows 11 requiring TPM, Secure Boot and being all react wasn't great. Now we have a hardware shortage and ai in everything. I miss the time when it was "My computer" and not "This PC". I just hope they keep Windows 10 around till 203
I was a ubuntu user and work forced me to use a windows machine. Over the years I've accumulated so much software that I have no intention of leaving behind (photoshop cs2). In the past year though, I've been transitioning back to Ubuntu. So many software now offer Linux support, there
I wish there was a security-only-updates channel for Windows in general. I basically want no new features, I just want something that doesn't change and doesn't brick on random tuesdays.
Windows 10 for me until new games won't run on it
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
Anyone who still needs to run Windows 10 for whatever reason should switch over to Windows 10 IoT Enterprise LTSC 2021 (version 21H2) which will continue to receive security updates up through 2032.https://learn.microsoft.com/en-us/windows/release-health/rel...