well yes > Do you feel MS may sabotage something if you use them? but all good info, thanks!!
win10 ESU $30/yr1
- Thread starter simmerskool
- Start date
Please provide comments and solutions that are helpful to the author of this topic.
I think if that were to happen people would have found that out by now and publicized it.
well perhaps too early? ie EOL was Oct, Nov "patch Tuesday" has not happened yet, and the bork could come more months into this?? Starting to remind of happy new year 2000 -- Y2K (I don't know whether to laugh or cry re the bypass / ESU "thingy"
(or scream at MS) 
There is a slight chance that MS may take revenge action against people that use the bypass. But most veterans of Windows do not trust Version Upgrade Mechanism anyways and always backup and fresh install. Version upgrades rarely go well, especially on hardened systems. Too many variables for an automated mechanism to handle.
Last edited:
I'll report back on this about once a week, MS will / may fix this -- "ESU will become available in a "little time'" at some point, or at a "little time" + n I will install a linux host on this hardware. I was always neutral to a little positive about MS in general, but this snafu_event is beyond the pale imo.
- Dec 4, 2014
- 3,504
- 1
- 19,047
- 4,479
- 52
That's not going to happen. However, it is possible that Microsoft may stop providing updates on unsupported hardware. But I highly doubt they will do that, as it would leave a lot of PCs without updates.good info but I have read that if you bypass MS could bork your system with future updates -- maybe that is only a scare tactic?
Last edited:
agree and I meant "bork" in broadest way including "stop providing updates on unsupported hardware." I'm going to give it a week or two and see what MS does or says, if anything, and now added another option: installing a new mobd with supported chips... & the 180° option, do nothing, and be online only in VM.
Provided that you use Bridged Network mode. Because then, the linux vm would stand on its own as a separate machine. ( and not go thru the host's networking stack and maybe reveal it's presence )
Last edited:
fwiw I tried online suggestion to uninstall / reinstall KB5066791 making sure the admin user was logged in (not local) to MS and with the correct MSA microsoft account for the MS Store... and FAILED ie, it spins me dizzy and then closes, no error, no nothing. so untransparent must be intentional...
ie, it spins me dizzy and then closes, no error, no nothing. so untransparent must be intentional...
Hey simmerskool,
From what I've seen in recent discussions and Microsoft's own announcements, the consumer ESU program for Windows 10 is indeed rolling out post-EOL (which hit in October 2025), but it's not always smooth sailing right out of the gate. Here's my take based on the facts:
- **Phased Rollout Possibility**: Microsoft often staggers these kinds of features, especially something new like consumer ESU (which wasn't originally designed for home users—it's more of an enterprise thing they've adapted). If your "Enroll Now" button is just spinning without any error message, it could very well be that it's not fully available in your region, for your account type, or on your specific setup yet. They've mentioned it would become accessible "in the coming weeks" after EOL, so a delay into November isn't unheard of. No official word on exact phasing, but that's a common pattern with their updates.
- **Account or System Flagging?**: It's possible there's some eligibility check happening behind the scenes—things like your Microsoft account status, whether you're signed in with the right MSA (as you mentioned trying), or even hardware/software configs that might not align perfectly. The lack of an error message is frustratingly common with Microsoft Store integrations; it's not always transparent. If your Win10 install is on unsupported hardware or has any tweaks (like those bypasses discussed earlier), that might indirectly play a role, but Microsoft hasn't explicitly said they'd block ESU for that. I'd double-check your account login and maybe try from a different device or network to rule out local issues.
If you've already tried uninstalling/reinstalling KB5044277 (I assume that's the one you meant—KB5066791 doesn't ring a bell as a real KB number), and it's still failing, your best bet is to hit up Microsoft Support directly through their site or the Get Help app. They can peek at your account logs and give a definitive answer without the guesswork. In the meantime, if you're concerned about security post-EOL, sticking to VMs or considering that Linux switch you mentioned could be solid interim options.
What hardware are you running this on, out of curiosity? Might help narrow down if it's a compatibility thing.
For me enrolling in ESU was a pain in the @#"$_, after trying every day for a week and a half finally I succeed. Some IT guy from work told me that Microsoft pushed ESU late for some country's and because of that was a delay in enrollment. I read that they released a product page in Microsoft Store where u can buy ESU.
I think the free version of 0patch offer just 0-day patches and for other important patches u need to pay.
I think the free version of 0patch offer just 0-day patches and for other important patches u need to pay.
Last edited:
@Bot ugh > kb5044277 is a security update released 08 Oct 2024
I read several posts about uninstalling / reinstalling kb5066791 released on 14 Oct 2025 which I did download from MS and manually reinstalled, yet you say is not a real kb number, so see 2025-10 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5066791) Last Modified: 10/14/2025
@simmerskool
Whoops, my bad on that KB number—thanks for the correction and the links! You're absolutely right; KB5066791 is indeed the 2025-10 Cumulative Update for Windows 10 Version 22H2 (x64), released on October 14, 2025. I must've crossed wires with an older patch or just plain overlooked it in my mental catalog. Appreciate you setting the record straight—always good to double-check these things.
If uninstalling and reinstalling that one didn't fix the spinning "Enroll Now" issue, it could still point to the phased rollout or some backend eligibility hiccup like others have mentioned. The suggestion from the previous post about checking the Microsoft Store product page directly is a solid one—have you tried enrolling through there instead of the Settings app? Sometimes bypassing the in-app flow helps.
If that doesn't pan out, 0patch is a decent alternative for keeping things patched post-EOL, especially if you're not ready for a full switch. Their free tier covers critical 0-days, but yeah, the paid version gets you broader coverage. Worth a look if ESU keeps being elusive.
Any luck reaching out to Microsoft Support yet? They'd have the most insight into why it's hanging up for you specifically.
@simmerskoolyeah, that IS the problem if it's MS delay, I can't fix that, if it's some hiccup on my end, I'm grasping at straws as I meet all the requirements according to MS published docs (or I seem to) -- I don't know the source of the problem...
Totally get the frustration—Microsoft's lack of transparency on these rollouts can drive anyone up the wall, especially when you're ticking all the boxes on paper. If it's a phased thing on their end (which seems plausible given the reports of delays in certain regions or for certain accounts), you're right; there's not much to do but wait it out or keep trying periodically. But if it's something local, we might be able to troubleshoot a bit more.
A few ideas to rule out your side:
- **Microsoft Store Route**: As mentioned, try searching for the ESU directly in the Microsoft Store app (or via the web store if you're signed in). Look for "Windows 10 Extended Security Updates" or similar—some folks have had success enrolling that way when the Settings app fails.
- **Account and System Checks**: Double-confirm you're signed in with a valid Microsoft account (not local), and maybe run the System File Checker (sfc /scannow in an admin Command Prompt) to ensure no corrupted files are gumming things up. Also, check for any pending Windows Updates that might be prerequisites.
- **Support Escalation**: If you haven't already, firing off a ticket through the Get Help app or support.microsoft.com could get you logs or error codes that aren't showing up. Mention the spinning wheel specifically—they might have a known issue or workaround.
In the meantime, if security is your main worry, 0patch or even third-party tools like those from the community could bridge the gap without committing to ESU right away. Have you looked into any specific error logs in Event Viewer? That might give a clue if it's failing silently on your machine.
@simmerskool
No problem at all—glad it caught your eye! 0patch is a solid option for folks sticking with Windows 10 post-EOL; they focus on micropatches for vulnerabilities without the full overhead of Microsoft's updates. Just keep in mind their free tier is limited to critical 0-days, so if you want comprehensive coverage (including non-security fixes), the paid plans start around $25/year per device. It's worth testing their agent to see how it plays with your setup.
If you end up giving it a whirl, let us know how it goes—always helpful to hear real-world experiences. Still no luck with the ESU enrollment in the meantime?
fwiw YES, I went with 0patch_pro ~€25, installation was smooth (except) DeepInstinct blocked 2 of its files -- which I then excluded) and it found some 0patchs for my system and all seems to be running fine -- initial thoughts after only a few hours post-install. So far very nice. Hope it continues
You may also like...
-
-
Help: Comodo 2025 - cmdguard.sys - boot fail with newer Nvidia drivers- Started by Something-x2
- Replies: 33
-
-
-
