Windows 10 extended security updates now require a Microsoft account

[Skye Jacobs]

What just happened? Microsoft has clarified the details of its Extended Security Updates initiative for Windows 10, announcing that every enrollment method – whether paid or free – now requires users to sign in with a Microsoft Account. This move applies to all pathways, including the straightforward $30 purchase, redeeming Microsoft Rewards points, or enrolling via OneDrive settings backup.

This clarification addresses confusion from earlier announcements, which left some users with the impression that they could pay the $30 fee without registering for a Microsoft Account. However, Microsoft now confirms that an account is necessary to bind ESU licenses and ensure users can receive ongoing security updates after Windows 10's official support ends on October 14, 2025. The ESU program extends critical updates until October 13, 2026.

The program offers several enrollment options. Users may purchase an ESU license for $30, redeem 1,000 Microsoft Rewards points, or opt in for free by syncing their PC settings to OneDrive. In a shift that many will welcome, the $30 license, when tied to a Microsoft Account, will now cover up to ten Windows 10 devices rather than requiring a separate purchase for each one. This is helpful for people with several PCs, but each computer still has to be enrolled individually.

Some people may not like that they now have to use a Microsoft Account. For those already using one – especially users with several PCs and laptops – the expanded device coverage provides a considerable benefit. The claimed reason for the account requirement is to enable Microsoft to track and apply a user's ESU license across multiple devices under the same account.

Consumers looking to participate in the program must be running Windows 10, version 22H2, and have the latest update installed. The enrollment process, available through the Windows Update settings, is rolling out in waves and may not be visible on all devices immediately. Eligible users will eventually see an "Enroll now" prompt under the Windows Update section and must sign in with a Microsoft Account to proceed. After completing enrollment, covered devices will continue to receive important security updates for another year.

The ESU program is designed to offer a bridge for those unable or unwilling to upgrade to Windows 11 by the end-of-support deadline. Having to use a Microsoft Account adds an extra step for some people, but covering several PCs with one license makes the ESU program easier and more affordable for those with more than one device.

Permalink to story:

Windows 10 extended security updates now require a Microsoft account

 

[candle86]

I don't know who thought it wouldn't. Microsoft has to have a way to track it; with Enterprise customers, it's fairly easy, but home users aren't running server, and they don't have all the stuff on the back end. So anybody that thought this was going to be without a Microsoft account was engaging in hyper wishful thinking.

 

[seeprime]

I don't know who thought it wouldn't. Microsoft has to have a way to track it; with Enterprise customers, it's fairly easy, but home users aren't running server, and they don't have all the stuff on the back end. So anybody that thought this was going to be without a Microsoft account was engaging in hyper wishful thinking.

They can still use 0patch until 2030. It's a great service.

 

[Str8Shot]

I recently discovered you can use Windows 11 without being signed in/offline mode. Last thing we need is more surveillance, tracking, updating, and all this BS. Until about 2 years ago my main computers, ran everything on Windows 7, zero updates, zero issues. This obsession with being plugged into the hive is alarming to say the least.

 

[GeoffreyA]

Technically, it's implemented at the computer level, in the Windows Trusted Store based on a key and confirmation ID, as Tsforge has shown.

 

[techstrike]

The WORST news ever read for long time...

We were "ok" for the employees that MS fired.
We were "ok" for the stupid HW reqs to upgrade to W11.

But this?
What's next evil MS?

We are Microdoomed.

 

[candle86]

They can still use 0patch until 2030. It's a great service.

Its a second rate service that is a stop gap for emergencies not for day to day viability

 

[Lew Zealand]

I recently discovered you can use Windows 11 without being signed in/offline mode. Last thing we need is more surveillance, tracking, updating, and all this BS. Until about 2 years ago my main computers, ran everything on Windows 7, zero updates, zero issues. This obsession with being plugged into the hive is alarming to say the least.

Install Win 11
At starting screens, Shift-F10 to get cmd
oobe\bypassnro
W11 will restart and at the sign in screen, there will be a "I don't have Internet" option

Click that and enjoy a "normal" windows experience and don't forget to do all the typicals like turning off telemetry, etc.

 

[seeprime]

Its a second rate service that is a stop gap for emergencies not for day to day viability

Wow, you are so wrong. I've used it since Windows 7 mainstream support ended. Its fast, and uses hotpatch tech that Microsoft only uses in Enterprise servers for an extra fee.

I presume you don't use it, but decided to slam 0patch anyway.

 

[hahahanoobs]

MS account makes things so much easier.

 

[captaincranky]

I have two new PCs, one (Intel i3-12100) built, and another in the works, (Intel i5-12600K) that I'll get around to putting together one of these days. Frankly, I'm waiting til after October to do anything with them, so M$ won't be bothering me with updates. That's assuming I connect them to the internet al all, ever. All I need to do is elude M$ update until I install software which requires online activation, and I'm done.

This 11 YO i3-540 Windows 7 rig I'm using works just fine for making a nuisance out of myself online, thank you very much.

FWIW: M$ trashed Windows 7 with their "final cumulative security update" for Win 7. It was "so secure", I couldn't even navigate to Walmart, without getting security warnings blowing up in my face.

I do have a M$ account, from which I've just been notified that, "if I don't use my One Drive account, I'm going to lose it". I say, "good riddance". Like I really intend to upload maybe 10 TB of porn to "the cloud". I'd rather enjoy it, "in the privacy of my own home". If you know what I mean.

I know what y'all are thinkin', but the truth is, I could have had a petabyte of "erotic art", if my tastes weren't so refined and selective..

 

[candle86]

Wow, you are so wrong. I've used it since Windows 7 mainstream support ended. Its fast, and uses hotpatch tech that Microsoft only uses in Enterprise servers for an extra fee.

I presume you don't use it, but decided to slam 0patch anyway.

No, I'm saying it's not a good idea because it doesn't have access to the actual backend code like Microsoft does. They take guesses—sometimes have been good—but even they will tell you: only use it for mission-critical appliances that can't be upgraded, and work on migration. I'm so tired of people advertising it as a one-size-fits-all solution. It is an emergency tool for systems that can't be migrated because of critical software, but you still need it on the network.

And to be frank the average enthusiast is incompetent about their own cyber security, 0patch is an enterprise tool, it's expected that every unnecessary port for the function of that legacy system to be blocked to and from it, for it to be 100% on its own segmented vlan, and for it not to be a day to day used system. Anyone still using 10 without being the ESU after October is choosing to risk their personal details to every cybercriminal, and they love guys like you and captain cranky, because your easy targets. I've gotten two people fired before because they blocked updates because they were convinced it caused them issues, I found what was happening, again they were enthusiast's that knew just enough, and didn't listen when we said stop, so they got fired. Don't be like them.

As for giving the advice, I earnestly think anyone who follows such advice and then gets compromised should be able to hold the person who gave such advice criminally negligent as they represented themselves as an expert while lacking zero expertise.

 

[captaincranky]

As for giving the advice, I earnestly think anyone who follows such advice and then gets compromised should be able to hold the person who gave such advice criminally negligent as they represented themselves as an expert while lacking zero expertise.+

I would seem you sadly lack reading interpretation skills. I, in no way, suggested anyone follow my approach to "computer security". I simply stated that my way, works for me.

Unfortunately, we pray to different gods, both in the religious and corporate sense. M$ has turned itself into an omnipresent nuisance, and a threat, in and of itself, to user's online data security, and personal privacy.

I have in no way the needs of any corporate entity for security. I live alone. I don't need a password to enter my computer(s). My computers are not in any way, networked. I don't frequent such sites as Pirate Bay. I can identify a scam email quite easily. Nor do I sit around crapping my pants because I haven't updated my computer in the last ten minutes.

Point being, I don't sit around biting my nails, or quaking in my boots, or contributing any of my machines to Ewaste, because mother M$ commands it.

At the end of the day, any machine I own with Windows 10 installed will be air gapped. And Linux will happen for me, before I ever install M$'s Malware 11.

So, I'm not disposed to giving "advice", nor am I likely to ever accept any from you. That's even if you were the "last expert", on Techspot. Here's hoping, (but not praying). that never comes to pass.

 

[Win7User]

With, friends like Microsoft, who needs enemies.

 

[GeoffreyA]

I have two new PCs, one (Intel i3-12100) built, and another in the works, (Intel i5-12600K) that I'll get around to putting together one of these days. Frankly, I'm waiting til after October to do anything with them, so M$ won't be bothering me with updates. That's assuming I connect them to the internet al all, ever. All I need to do is elude M$ update until I install software which requires online activation, and I'm done.

This 11 YO i3-540 Windows 7 rig I'm using works just fine for making a nuisance out of myself online, thank you very much.

FWIW: M$ trashed Windows 7 with their "final cumulative security update" for Win 7. It was "so secure", I couldn't even navigate to Walmart, without getting security warnings blowing up in my face.

Recently, I performed a clean installation of 10, using the July 2025 ISO, after an honest attempt switching to 11 left me with less-than-positive feelings about it. Then, I used the excellent MAS, which is open source and safe if used from the correct URL, to turn on three to six years of ESU. 10 is working like a charm; only, I worry about the Arc drivers because Intel grows hesitant to implement features on 10, such as HAGS.

(Regarding the conversation in the other article, regrettably, I wrote a long response to your comment but the article got locked.)

 

[Win7User]

Recently, I performed a clean installation of 10, using the July 2025 ISO, after an honest attempt switching to 11 left me with less-than-positive feelings about it. Then, I used the excellent MAS, which is open source and safe if used from the correct URL, to turn on three to six years of ESU. 10 is working like a charm; only, I worry about the Arc drivers because Intel grows hesitant to implement features on 10, such as HAGS.

(Regarding the conversation in the other article, regrettably, I wrote a long response to your comment but the article got locked.)

I read your reply, on my Acer Aspire laptop running Windows 7 Pro. At the end of November 2025, it will be 14 years, this beautiful machine has been running problem free. I also have an HP desktop almost three years old, running Windows 11 Pro 23H2. I tried to install the update to 24H2, but the machine wouldn't reboot. I rolled it back. Typical of Microsoft these days.

 

[GeoffreyA]

I read your reply, on my Acer Aspire laptop running Windows 7 Pro. At the end of November 2025, it will be 14 years, this beautiful machine has been running problem free. I also have an HP desktop almost three years old, running Windows 11 Pro 23H2. I tried to install the update to 24H2, but the machine wouldn't reboot. I rolled it back. Typical of Microsoft these days.

My grandfather is still running Windows 7 on his old Vostro laptop, despite having a newer Inspiron with 10. I think he enjoys using the Vostro more. It will be 14 years old. The only upgrade it had was a new WD 500 GB hard drive in 2014 to replace the failing Samsung.

Though I have a Zen 2 system, my old Pentium 4 Willamette still works, and I occasionally use it to copy disc images from the optical drive. It has Windows XP.

 

[captaincranky]

Recently, I performed a clean installation of 10, using the July 2025 ISO, after an honest attempt switching to 11 left me with less-than-positive feelings about it. Then, I used the excellent MAS, which is open source and safe if used from the correct URL, to turn on three to six years of ESU. 10 is working like a charm; only, I worry about the Arc drivers because Intel grows hesitant to implement features on 10, such as HAGS.

(Regarding the conversation in the other article, regrettably, I wrote a long response to your comment but the article got locked.)

Ah yes, drivers for Intel GPUs. It's kind of sad that Intel is in the process of failing in practically every other facet of their business, that they don't have the time to apply themselves to the one where they're succeeding. Phooey.

As for "the padlock"; it was about time for it to click shut on that thread, don't you think?

If I might, can I offer you a suggestion? I keep "Note pad" on the taskbar. Sometimes in questionable or uncertain circumstances, I'll copy a post to it.

That way, you can re-paste it into a PM, and send to whomever you think might most benefit from your wisdom and insight.

 

[GeoffreyA]

Ah yes, drivers for Intel GPUs. It's kind of sad that Intel is in the process of failing in practically every other facet of their business, that they don't have the time to apply themselves to the one where they're succeeding. Phooey.

As for "the padlock"; it was about time for it to click shut on that thread, don't you think?

If I might, can I offer you a suggestion? I keep "Note pad" on the taskbar. Sometimes in questionable or uncertain circumstances, I'll copy a post to it.

That way, you can re-paste it into a PM, and send to whomever you think might most benefit from your wisdom and insight.

For us on Arc, we're sailing on "stranger tides" into the unknown. However, I have noticed a change of late: there's a considerable increase in commits to the open-source drivers; for example, the compute runtime and Mesa on Linux. One gets the sense that the Arc division knows they're staying and have breathed a sigh of relief.

Indeed, it was time for the padlock to click shut!

Thanks for the tip. Actually, I saved that response in Notepad because it was a lengthy one.

 

[Win7User]

My grandfather is still running Windows 7 on his old Vostro laptop, despite having a newer Inspiron with 10. I think he enjoys using the Vostro more. It will be 14 years old. The only upgrade it had was a new WD 500 GB hard drive in 2014 to replace the failing Samsung.

Though I have a Zen 2 system, my old Pentium 4 Willamette still works, and I occasionally use it to copy disc images from the optical drive. It has Windows XP.

I did change the hard drive in the Acer laptop, (500G) to an SSD a number of years ago. I forgot about that until you mention your grandfather. Wow! a Pentium 4, that still works!!

 

[GeoffreyA]

I did change the hard drive in the Acer laptop, (500G) to an SSD a number of years ago. I forgot about that until you mention your grandfather. Wow! a Pentium 4, that still works!!

Surprisingly, it's works well in XP, on the desktop. That computer actually replaced a faster, but failing, Athlon 64 back in the day.