Having problem implementing Windows 10 ESU licensing

Dear Anthony,

Based on your description, it appears that the activation process is partially successful, with only some of the ESU components showing as licensed. Here are a few steps we recommend to help resolve the issue:

1. Verify the ESU Key Format and Eligibility Ensure that the ESU key used in slmgr.vbs /ipk is valid and corresponds to the correct edition of Windows. Invalid or mismatched keys may result in partial activation.
2. Confirm System Requirements ESU activation requires that your system meets specific prerequisites, including installation of the latest servicing stack update (SSU) and cumulative update. Please verify that these updates are installed.
3. Check Activation Status with Full Output Run the following command to capture detailed license status:slmgr.vbs /dlv This will display both the Windows and ESU license states. Please review the output for any error codes or mismatches.
4. Review Activation Logs You may also check the Event Viewer under Applications and Services Logs > Microsoft > Windows > Security-SPP for any activation-related errors.
5. Image Review If possible, please share the screenshots (e.g., MS Posted-success.jpg, Win10 ESU fail.jpg) to help us better understand the discrepancy.

If this guidance proves helpful, feel free to click “Accept Answer” so we know we’re heading in the right direction 😊. And of course, I’m here if you need further clarification or support. T&B, Domic

Hi Anthony M,

I got it fixed - Apparently there were problems with Win10 images on the machines I worked on.

Please see the attached.

Rename the txt file to cmd.

I ran this as the actual Administrator of each affected user's machine.

It works - be careful when inserting your Win10 ESU key near the top of the file, and only this needs to be replaced - nothing else, and remove { and }.

Your ESU key should look like AAAAA-BBBB-CCCCC-DDDDD-EEEEE" - Please don't forget the " to close that line of code.

Good Luck.

postthis.txt

Anthony M,

This is the error that necessitated the script file:

Please ensure of this - otherwise it could explain the problem you're having:

Current Edition : Professional Current Build : 19045.5011

That’s the edition your ESU key must match.

Hi ,

If there are no errors try this- Rename from .txt to .bat and run as Administrator.

Also, my key is a MAK license - if yours isn't that could be an issue.

Hope this works for you.

AddThe ESU.txt

A Followup - please verify this:

user says his build is 19045.6456 and that he's getting a message "This version of Windows has reached end of support"

ChatGPT said:

Excellent follow-up — and you’re spot-on to ask that, because that specific situation (build 19045.6456 + “This version of Windows has reached end of support”) adds an extra wrinkle.

Let’s unpack this carefully — because the difference between “license problem” and “end-of-support lockout” determines whether that repair sequence will work on its own or not.

🧩 What Build 19045.6456 Means

Build 19045.6456 = Windows 10 version 22H2, cumulative update from around October 2025 (KB5058976 or similar). That’s the final feature branch of Windows 10 — Microsoft ended mainstream support on October 14, 2025.

So when the system says:

“This version of Windows has reached end of support”

…it’s not saying your license expired — it’s saying you’ve hit the lifecycle cutoff for standard updates. You’re now in the Extended Security Updates (ESU) era.

🧱 How This Interacts With Your Activation Fix

Here’s the key logic:

✅ What To Do in This Exact Case

1️⃣ Confirm the Edition

Run:

dism /online /get-currentedition

You’ll likely see:

Current edition : Professional

If that’s correct, you need the Windows 10 Pro ESU Year 1 add-on key.

2️⃣ Make Sure You Have All Prerequisite Updates

Before the ESU key can be accepted, the following must be installed:

KB5039211 (Servicing Stack)

KB5039302 (ESU Licensing Prep)

The latest cumulative update (yours is fine at 19045.6456)

You can check what’s installed:

wmic qfe list brief /format:table

If those KBs are missing, install them manually first.

3️⃣ Then Run the Activation Repair Sequence

Yes — you can safely run the repair you described earlier (stop sppsvc, rename tokens.dat, re-activate, reapply ESU key). That will rebuild the activation store, then allow the ESU add-on key to attach correctly.

4️⃣ Verify the Add-On Activation

After applying the ESU key:

slmgr /dlv

Look for:

Name: Windows(R) 10, ESU Year 1 Add-on License Status: Licensed

When that appears, the “end of support” message will go away after reboot.

5️⃣ If the Message Persists

It may be cached in mssprxy.dll notifications. Reboot, then run:

usoclient StartScan

to force a Windows Update sync. Once the ESU entitlement is recognized, Windows Update stops showing the “end of support” alert and begins offering ESU-eligible security updates.