Still on Windows 10? Enroll in free ESU before next week’s Patch Tuesday

Brownie2019

Level 23
Thread author
Verified
Well-known
Forum Veteran
Mar 9, 2019
969
4,663
2,168
Germany
With the first Patch Tuesday following Windows 10’s end of support approaching next week, users who continue to run the operating system should enroll in the Extended Security Updates (ESU) program to remain protected against newly discovered security vulnerabilities.

On October 14, 2025, Windows 10 reached the end of support, meaning that Microsoft will no longer provide technical assistance, feature updates, or security updates for the operating system unless you are running a Windows LTSC version.

For those who are unable to upgrade to Windows 11, whether because they don't want to, are on older hardware, or run incompatible applications, Microsoft offers extended security updates (ESUs) that allow them to continue receiving security updates for a limited time.
Full Story on:
 
  • HaHa
Reactions: simmerskool
Full Story on:
Thanks for sharing this, Brownie2019. It's a timely reminder as we're heading into that first post-EOL Patch Tuesday. For anyone still on Windows 10 (and I know there are plenty of valid reasons to stick with it), enrolling in the ESU program is definitely the way to go if you want to keep those critical security patches coming. Microsoft has priced it at $30 for the first year for consumers, which isn't too bad for peace of mind against emerging threats.

Just a heads up: ESUs only cover security fixes—no new features or non-security updates. And remember, this is a temporary bridge; it's set to run for three years max. If upgrading to Windows 11 isn't feasible, it's worth exploring options like Linux distros or even virtual machines for incompatible apps in the long term.

Has anyone here already signed up for ESUs? How's the process been?
 
non-functional here, I got 0patch_pro instead. very happy with 0patch so far... :D
That's interesting, simmerskool! I've heard good things about 0patch Pro from a few folks who've gone that route for extending support on older systems. It's a solid alternative for those who prefer third-party micropatching over Microsoft's ESU program—especially since it covers not just Windows 10 but other EOL software too. Glad to hear you're happy with it so far; mind sharing what made you choose it over ESU? Was it the pricing, the ease of use, or something else?

For anyone else reading this, just a quick note: While 0patch is reputable (run by ACROS Security), it's always smart to do your homework and ensure it fits your setup. Security patching is crucial post-EOL, no matter which path you take.
 
; mind sharing what made you choose it over ESU? Was it the pricing, the ease of use, or something else?

For anyone else reading this, just a quick note: While 0patch is reputable (run by ACROS Security), it's always smart to do your homework and ensure it fits your setup. Security patching is crucial post-EOL, no matter which path you take.
I already posted somewhat extensively here about MS ESU Enroll Now "spinning" failure over several days with no clear timeline from MS. (@Bot is not staying current even inside MT!) Cost had nothing to do with choosing 0patch -- it just works and it is a slightly less cost, but not enough to make a difference one way or the other.
 
I already posted somewhat extensively here about MS ESU Enroll Now "spinning" failure over several days with no clear timeline from MS. (@Bot is not staying current even inside MT!) Cost had nothing to do with choosing 0patch -- it just works and it is a slightly less cost, but not enough to make a difference one way or the other.
Ah, fair point, simmerskool—my bad for not catching your earlier posts on the ESU enrollment woes. I must've skimmed past that thread amid all the EOL chatter lately. Sounds frustrating dealing with that "spinning" issue and no solid ETA from Microsoft; I've seen similar reports popping up elsewhere, so you're not alone. Good on you for pivoting to 0patch instead—reliable functionality is king when it comes to patching, especially post-support. If it's working smoothly for you without the hassle, that's a win.

Out of curiosity, have you run into any compatibility quirks with 0patch on your setup, or has it been seamless across the board? Always interesting to hear real-user experiences for those weighing options.