Share via

How to fix ESU error "We can’t enroll you in Extended Security Updates right now" when trying to enroll?

Eri 60 Reputation points
2025-10-08T01:44:27.89+00:00

I'm trying to enroll to ESU (Extended Security Updates) as the updates are ending and I cant yet update to Windows 11 because its not available even though my PC meets the requirements. The process is very straight-forward, I click "enroll now" on the windows updates page and go through the process until the last page where I get told I'm eligible (first image attached), I click "Enroll" and after I do I get redirected to a page with the title "Something went wrong" and alongside that "We can’t enroll you in Extended Security Updates right now" (second image attached). This happens regardless of when or how many times I try. I've tried going through live support, but after a 30 minute wait, all I got told was to post on the forums. So here I am, with windows 10 updates ending and not being able to update to windows 11, it feels a bit more urgent. Any help appreciated.Capture2

Capture1

Windows for home | Windows 10 | Windows update

14 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Raymond Caswell 150 Reputation points
    2025-10-13T17:17:50.79+00:00

    I had this very same annoying issue UNTIL I hit on the left side in settings under "Find my device." It was turned "off" and then I changed it to "on." As soon as I turned it to "on" I was able to "enroll" the very next time. Hopefully this works for someone else as well.

    Capture

    25 people found this answer helpful.
  2. John DeV 152.5K Reputation points Independent Advisor
    2025-10-08T02:22:09.8233333+00:00

    Hi, good day!

    Are you logged into Windows using a local or Microsoft Account?

    Please try the following methods below.

    If your computer can connect to Wi-Fi, please try connecting to a different network such as your phone's mobile hotspot then try again.

    Make sure Microsoft Account Sign-in Assistant and Credential Manager services are available and running.

    Press Start then search Services

    Find Microsoft Account Sign-in Assistant in the list then double click it

    Select Automatic (Delayed Start) on the Startup Type and click on Start

    Click Apply and OK.

    Do the same with Credential Manager service

    I look forward to receiving your update and I'm willing to collaborate with you till we resolve the issue. Do keep me informed by clicking "Add comment" below.

    4 people found this answer helpful.
  3. Roger Keay 5 Reputation points
    2025-10-15T20:37:02.3866667+00:00

    To Donna Hilbert and anyone else having that problem, this might be your issue. I just went through the ESU hell and did all the registry hacks to no avail. I also downloaded a script on GitHub and ran that with no joy. However, it DID report that my device was INELIGIBLE because it was a COMMERCIAL_DEVICE. After messing around and looking through many documents, I found what my problem was. I have a small home network running Active Directory. I found a page that enumerated that scenario as ineligible. Actually, if any machine is part of an Active Directory network it is considered a COMMERCIAL_DEVICE and be marked as INELIGIBLE.

    Here's what I did to fix my issue. It's messy but works.

    I went to this url, "https://github.com/abbodi1406/ConsumerESU". This page has a zip file of scripts and directions as to how to use the scripts. Once there I clicked on the "Code" button and downloaded the zip to a directory on my C drive in a new folder I named ESUFix. I extracted the zip file to that folder. I then made sure I was logged into my Microsoft account as an administrator and then logged in as an Administrator on my machine. Then I opened the Command Prompt window running as an Administrator and nav'd to the ESUFix folder. Then I ran the script. That's when it came back with the info my device was INELIGIBLE, and it was a COMMERCIAL_DEVICE. That's when I went looking for more info and found that it won't work on any machines that are part of an Active Directory Domain. So, I removed my machine from my Active Directory and joined the WORKGROUP default. I logged in with a WORKGROUP Administrator account I had, opened cmd as an Administrator, nav'd to the ESUFix directory and ran the script and it finally worked. After that I went to the Update & Security Settings and there it showed I had enrolled. Then I checked a few of my other WORKGROUP accounts and they showed the same thing.

    The big caveat with this scenario is that I have to be on the Active Directory Domain to utilize my pc effectively. I understand that Microsoft sends out their updates around the beginning of the month, on a monthly basis, so... Once a month I will have to jump out of the Domain into the WORKGROUP, manually search for updates and apply them, then jump back into the Domain. a PITA, but this is only a stopgap anyway. Until I can build my next machine and get my programs and data on the new machine.

    1 person found this answer helpful.
  4. aSoCKreply001 85 Reputation points
    2025-10-17T17:42:43.4633333+00:00

    Hello Eri. I had a similar issue. But after clicking on the 'enroll' button in the Windows 10 update menu (under "Settings/update&security/Windows Update") I did not even get to the next step where I would be able to choose one of the options for ESU. In my case a black popup window opened and then closed immediately.

    I was able to resolve that issue by uninstalling and then reinstalling the October 14, 2025—KB5066791 update. After that I was able to continue with the ESU steps with no problems.

    Hope this helps!

    1 person found this answer helpful.
  5. Kapil Arya 36,426 Reputation points Volunteer Moderator
    2025-10-08T09:44:06.7466667+00:00

    Make sure your system meets primary requirements mentioned here:

    https://www.microsoft.com/en-us/windows/extended-security-updates

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.