[DISCUSSION] Windows 10 ESU License: All options, Activation, and Troubleshooting

Discussion in 'Windows 10' started by Enthousiast, Sep 11, 2025.

  1. ASGL

    ASGL MDL Novice

    Jan 18, 2020
    9
    4
    0
    #261 ASGL, Nov 17, 2025
    Last edited by a moderator: Nov 20, 2025
    I hope I have correctly activated the year 2 and 3 addons. I am posting below the licensing details in the hope that they do confirm activation.
    However, I am not sure where to find ClipESU.exe.
    Code:
    ============================================================
    ===                   Windows Status                     ===
    ============================================================
    
    Name: Windows(R), Client-ESU-Year2 add-on
    Description: Windows(R) Operating System, VOLUME_MAK channel
    Activation ID: 1043add5-23b1-4afb-9a0f-64343c8f3f8d
    Extended PID: 03612-05151-178-405465-03-1033-19045.0000-3212025
    Product Key Channel: Volume:MAK
    Partial Product Key: RYC49
    License Status: Licensed
    
        The product is permanently activated.
    ____________________________________________________________
    
    Name: Windows(R), Client-IoT-ESU-Year3 add-on
    Description: Windows(R) Operating System, VOLUME_MAK channel
    Activation ID: 4dac5a0c-5709-4595-a32c-14a56a4a6b31
    Extended PID: 03612-05155-177-257490-03-1033-19045.0000-3202025
    Product Key Channel: Volume:MAK
    Partial Product Key: YBM84
    License Status: Licensed
    
        The product is permanently activated.
    ____________________________________________________________
    
    Name: Windows(R), Client-IoT-ESU-Year2 add-on
    Description: Windows(R) Operating System, VOLUME_MAK channel
    Activation ID: 7b76ee02-0a75-4f08-85d5-bd0feadad0c0
    Extended PID: 03612-05154-109-803920-03-1033-19045.0000-3202025
    Product Key Channel: Volume:MAK
    Partial Product Key: R64W3
    License Status: Licensed
    
        The product is permanently activated.
    ____________________________________________________________
    
    Name: Windows(R), Client-ESU-Year3 add-on
    Description: Windows(R) Operating System, VOLUME_MAK channel
    Activation ID: 83d49986-add3-41d7-ba33-87c7bfb5c0fb
    Extended PID: 03612-05152-008-655297-03-1033-19045.0000-3212025
    Product Key Channel: Volume:MAK
    Partial Product Key: G3FWY
    License Status: Licensed
    
        The product is permanently activated.
    ____________________________________________________________
    
    Name: Windows(R), Client-IoT-ESU-Year1 add-on
    Description: Windows(R) Operating System, VOLUME_MAK channel
    Activation ID: b8527af1-5389-447c-9a88-2d1691ea33d3
    Extended PID: 03612-05153-057-361283-03-1033-19045.0000-3202025
    Product Key Channel: Volume:MAK
    Partial Product Key: 2YYCP
    License Status: Licensed
    
        The product is permanently activated.
    ____________________________________________________________
    
    Name: Windows(R), Client-ESU-Year1 add-on
    Description: Windows(R) Operating System, VOLUME_MAK channel
    Activation ID: f520e45e-7413-4a34-a497-d2765967d094
    Extended PID: 03612-05150-218-479711-03-1033-19045.0000-3202025
    Product Key Channel: Volume:MAK
    Partial Product Key: 3DFWW
    License Status: Licensed
    
        The product is permanently activated.
    ____________________________________________________________
    
    Name: Windows(R), Client-IoT-ESU-Year6 add-on
    Description: Windows(R) Operating System, VOLUME_MAK channel
    Activation ID: f69e2d51-3bbd-4ddf-8da7-a145e9dca597
    Extended PID: 03612-05191-047-212452-03-1033-19045.0000-3202025
    Product Key Channel: Volume:MAK
    Partial Product Key: CR8MK
    License Status: Licensed
    
        The product is permanently activated.
    ____________________________________________________________
    
    Name: Windows(R), IoTEnterprise edition
    Description: Windows(R) Operating System, OEM_COA_NSLP channel
    Activation ID: b68e61d2-68ca-4757-be45-0cc2f3e68eee
    Extended PID: 03612-04363-055-033013-02-1033-19045.0000-3332023
    Product Key Channel: OEM:NONSLP
    Partial Product Key: WHXV4
    License Status: Licensed
    
        The machine is permanently activated.
    ____________________________________________________________
    
    Client Licensing Check information:
        AppId=55c92734-d682-4d71-983e-d6ec3f16059f
        LastConsumptionReason=0x4004f401
        LastNotificationId=Cleanup
        LicenseState=SL_LICENSING_STATUS_LICENSED
        PartialProductKey=WHXV4
        ProductKeyType=OEM:NONSLP
        SkuId=b68e61d2-68ca-4757-be45-0cc2f3e68eee
        ruleId=379cccfb-d4e0-48fe-b0f2-0136097be147
        uxDifferentiator=OEM_COA_NSLP
        LastActivationHResult=0x00000000
        LastActivationTime=2023/11/30:00:21:25
        IsWindowsGenuine=SL_GEN_STATE_IS_GENUINE
        IsDigitalLicense=TRUE
        SubscriptionSupportedEdition=FALSE
        SubscriptionEnabled=FALSE
    ____________________________________________________________
    
    
    Press any key to Go back...
    
     
  2. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream
    Staff Member

    Dec 21, 2012
    8,076
    10,298
    270
    You already did, one post prior.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. ASGL

    ASGL MDL Novice

    Jan 18, 2020
    9
    4
    0
    Yes, I have just run slmgr.vbs /dlv and now I see what you mean. I have also found and run ClipESU.exe. Thank you for the assistance.
     
  4. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,610
    100,025
    340
  5. dateno1

    dateno1 MDL Novice

    Sep 5, 2013
    19
    4
    0
    #266 dateno1, Nov 20, 2025
    Last edited by a moderator: Nov 20, 2025
    Someone success to merge KB5068781 on wim?

    I try to merge it on 19045.6456 x86 Core edition wim but always failed (Error: 14099)

    KB5072653 -> KB5068781

    or

    merged
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\ESU]
    "Win10ConsumerESUAY"=dword:00000009
    "Win10CommercialKeybasedESUEligible"=dword:00000001
    "Win10CommercialW365ESUEligible"=dword:00000001
    "Win10CommercialAzureESUEligible"=dword:00000001

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides]
    "3108581004"=dword:00000000
    Add KB5068781

    Same result

    I can't upload fullDISM log (It too big for MDF)
    Code:
    2025-11-20 10:41:10, Error                 CSI    00000141 (F) Matching binary Microsoft.Msmq.Activex.Interop.dll missing for component Microsoft-Windows-msmq-powershell, version 10.0.19041.6575, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}[gle=0x80004005]
    2025-11-20 10:41:11, Error                 CSI    0000014d (F) Matching binary EditionMatrix.xml missing for component Microsoft-Windows-Editions-Professional, version 10.0.19041.6575, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}[gle=0x80004005]
    2025-11-20 10:41:11, Error                 CSI    00000151 (F) Matching binary mssecflt.sys missing for component Windows-SECDriver, version 10.0.19041.6575, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}[gle=0x80004005]
    ...
    2025-11-20 10:42:00, Error      [0x018067] CSI    00000979 (F) Failed execution of queue item Installer: Extended Security Updates AI installer ({4e9a75dd-0792-460c-a238-3f4130c39369}) with HRESULT HRESULT_FROM_WIN32(1625).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
    2025-11-20 10:42:00, Error                 CSI    0000098b (F) Installer: Extended Security Updates AI installer    Binary Name: ExtendedSecurityUpdatesAI.dll    ErrorCode: 80070659    Phase: 10    Mode: Install (first install)    Component: Microsoft-Windows-Security-SPP-Component-ExtendedSecurityUpdatesAI, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS[gle=0x80004005]
    2025-11-20 10:42:00, Error                 CSI    0000098d (F) AI failure encountered during offline servicing.  Not attempting rollback.
    [gle=0x80004005]
    2025-11-20 10:42:00, Error                 CSI    0000098e@2025/11/20:01:42:00.943 (F) onecore\base\wcp\componentstore\com\store_transaction.cpp(3135): Error STATUS_ADVANCED_INSTALLER_FAILED originated in function Windows::COM::CComponentStore::ApplyTransactionNow expression: static_cast<DWORD>(14099L)
    [gle=0x80004005]
    2025-11-20 10:42:00, Error                 CSI    0000098f (F) STATUS_ADVANCED_INSTALLER_FAILED #6769062# from Windows::COM::CComponentStore::ApplyTransactionNow(...)[gle=0xd0150020]
    2025-11-20 10:42:00, Error                 CSI    00000990 (F) HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED) #6769054# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Apply(...)[gle=0x80073713]
    2025-11-20 10:42:00, Error                 CSI    00000991 (F) HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED) #6769053# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 2144, pSink = NULL, disp = 0)[gle=0x80073713]
    2025-11-20 10:42:00, Error                 CSI    00000992 (F) HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED) #6769052# 1436891 us from Windows::ServicingAPI::CCSITransaction_IC
    2025-11-20 10:42:00, Error                 CBS    Exec: Failed to commit CSI transaction to execute changes. [HRESULT = 0x80073713 - ERROR_ADVANCED_INSTALLER_FAILED]
    2025-11-20 10:42:09, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073713 - ERROR_ADVANCED_INSTALLER_FAILED]
    2025-11-20 10:42:10, Error                 CBS    Failed to perform operation.  [HRESULT = 0x80073713 - ERROR_ADVANCED_INSTALLER_FAILED]
    2025-11-20 10:42:10, Error                 DISM   DISM Package Manager: PID=8884 TID=17172 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80073713)
    2025-11-20 10:42:10, Error                 DISM   DISM Package Manager: PID=8884 TID=17172 Failed processing package changes - CDISMPackageManager::processChanges(hr:0x80073713)
    2025-11-20 10:42:10, Error                 DISM   DISM Package Manager: PID=8884 TID=17172 Failed to process package changes in unattend file. - CPackageManagerUnattendHandler::Internal_ProcessChanges(hr:0x80073713)
    2025-11-20 10:42:10, Error                 DISM   DISM Package Manager: PID=8884 TID=17172 Failed to process package changes. - CPackageManagerUnattendHandler::Apply(hr:0x80073713)
    2025-11-20 10:42:10, Error                 DISM   DISM Package Manager: PID=8884 TID=17172 Failed to Apply the unattend. - CDISMPackageManager::Apply(hr:0x80073713)
    2025-11-20 10:42:10, Error                 DISM   DISM Unattend Manager: PID=8884 TID=17172 "Error applying unattend for provider: DISM Package Manager" - CUnattendManager::Apply(hr:0x80073713)
    2025-11-20 10:42:10, Error                 DISM   DISM Package Manager: PID=8884 TID=17172 Failed applying the unattend file from the MSU package. - CMsuPackage::ApplyMsuUnattend(hr:0x80073713)
    2025-11-20 10:42:10, Error                 DISM   DISM Package Manager: PID=8884 TID=17172 Failed to apply the MSU unattend file to the image. - CMsuPackage::Install(hr:0x80073713)
    2025-11-20 10:42:11, Error                 DISM   DISM Package Manager: PID=8884 TID=17172 Discard this Windows image and try the operation again on a new Windows image. - GetCbsErrorMsg
    2025-11-20 10:42:11, Error                 DISM   DISM Package Manager: PID=8884 TID=17172 The specified image is no longer serviceable. Unmount the image and discard your changes.  Mount the original image to try the operation again. - CPackageManagerCLIHandler::ReportFailedPackage
    2025-11-20 10:42:11, Error                 DISM   DISM Package Manager: PID=8884 TID=17172 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80073713)
    Extract Error only
    
    Base wim is created by UUP
     
  6. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,610
    100,025
    340
    @dateno1
    Code:
    * Unless you integrate the ESU Suppressor, ESU updates are not supported offline for wim files 
    you cannot integrate them, they must be installed online on a live system.
    BypassESU X
     
  7. nuhuh

    nuhuh MDL Novice

    Oct 10, 2013
    45
    23
    0
    I have a PC with W10 22H2 Edu. I ran the TSforge ESU activation (version 3.9), which completed fine. But when searching WU for available updates (using WUmgr), it does not offer the 2025-11 Cumulative update.
    I tried changing the registry entries as mentioned in this post, but it made no difference.
    I can still install that update by getting the .msu file from the catalog and it installs just fine. The problem is only that it's not offered through WU.

    For testing, I installed another W10 22H2 Edu in a VM and it doesn't have this problem. I did the same ESU activation and I can see the 2025-11 Cumulative update being offered in WUmgr.
    I didn't change or add any registry values in the ESU key there, they're still like this:
    Code:
    "Win10CommercialAzureESUEligible"=dword:00000000
    "Win10CommercialKeybasedESUEligible"=dword:00000001
    "win10ConsumerESUStatus"=dword:00000001
    So, altering those values is not even necessary?
    But as I said, on the hardware W10 install changing them made no difference.

    I tried to recreate the same settings between the two systems. The VM install (the one that works) is not activated, though.
    Any ideas?
     
  8. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,610
    100,025
    340
    @nuhuh
    Is OneSettings disabled on your real machine?

    can you check if this file exists and the timestamp is not old?
    Code:
    C:\ProgramData\Microsoft\Windows\OneSettings\CTAC.json
    run this in Windows Powershell and see if the 2nd command returns True
    Code:
    $ctac = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\WindowsSelfHost\OneSettings" "TargetingAttributes" -EA 0).TargetingAttributes
    $ctac.Contains('ESUEligible')
     
  9. joshlynn

    joshlynn MDL Novice

    Sep 22, 2018
    9
    7
    0
    #270 joshlynn, Nov 23, 2025
    Last edited: Nov 23, 2025
    @abbodi1406
    Hello, I have a simple question. Just ran TSforge, and it found large number of WPA registries (like 8300+). The blue message told me to go back and fix WPA registry - yet the script continued - and I was unsure if it is a good idea to interrupt it at this stage.
    If I do the fix now, will it deactivate everything, including newly activated 3 year ESU?
    I have no idea why there are so many WPA entries, as I was using simple KMS with some public server and later manually activated Windows with HWID method.
    Thanks in advance.

    Edit:
    I don't have this file:
    Code:
    C:\ProgramData\Microsoft\Windows\OneSettings\CTAC.json
    any more after running TSforge, but there was one 2 days old just before I run the script.
     
  10. nuhuh

    nuhuh MDL Novice

    Oct 10, 2013
    45
    23
    0
    Thank you!
    Yes, that was the cause. OneSettings was disabled and there were old .json files in that folder.
    OneSettings is actually disabled on the VM system too, but the difference is that it's disabled from the start there, while on the real machine I only disabled it after some time.

    Rather than enabling OneSettings, I chose to recreate the default/blank state by deleting the .json files and the registry entries. This fixed it. Now WU shows the update, both with and without those registry changes.
    (I noted this change and backed up the files/reg, but I doubt that it will cause problems.)
     
  11. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,610
    100,025
    340
    If everything is working fine, no need to run the fix (maybe it also remove all activations too)

    this is a known bug or behavior with KMS activation
    whenever you run new activation attempt = new WPA key is created
    this does not occur for KMS auto renewals
     
  12. joshlynn

    joshlynn MDL Novice

    Sep 22, 2018
    9
    7
    0
    Okay, thanks a lot.
    Everything seems to be working fine so I won't poke it until something eventually breaks.
    Thanks again!
     
  13. rubyeye

    rubyeye MDL Novice

    May 26, 2019
    2
    0
    0
    @abbodi1406, is it possible to use ConsumerESU script to enroll and, once the "free-tier" cycle ceases, switch to BypassESU X to continue receiving updates for another year or two? Or is it better to stick with BypassESU X from the get go?
     
  14. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,610
    100,025
    340
    BypassESU X is more prefered in this case (as long as WU detection registry continue to work)
    they might change them for Year 2 & 3
     
  15. rubyeye

    rubyeye MDL Novice

    May 26, 2019
    2
    0
    0
    Thank you. Hopefully, if that ever comes to be, the MS catalog alternative will still be feasible.
     
  16. 8139david

    8139david MDL Novice

    Mar 4, 2016
    49
    20
    0
    The Windows Update pannel was showing "You are eligible for ESU updates". It doesn't anymore, even though slmgr.vbs /dli still shows the ESU licences. Did anyone notice the same?
     
  17. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,610
    100,025
    340
    "You are eligible for ESU updates" = Consumer ESU
    "slmgr.vbs ESU licenses" = Commercial ESU

    they don't coexist

    once ClipESUConsumer.exe is ran (via scheduled task), and it finds active Commercial ESU, it invalidates Consumer ESU (registry values only, it doesn't remove the license)
     
  18. nicolaasjan

    nicolaasjan MDL Junior Member

    Jan 27, 2020
    56
    10
    0
    Windows 10 Pro; activated (can't remember if I did HWID or TSforge...) and TSforge ESU applied.
    Are these registry entries OK?

    Code:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\ESU]
    "win10ConsumerESUStatus"=dword:00000001
    "Win10CommercialAzureESUEligible"=dword:00000000
    "Win10CommercialKeybasedESUEligible"=dword:00000001
    "Win10ConsumerESUAY"=dword:00000009
    Windows Status:

    Code:
    ============================================================
    ===                   Windows Status                     ===
    ============================================================
    
    Name: Windows(R), Client-ESU-Year6 add-on
    Description: Windows(R) Operating System, VOLUME_MAK channel
    Activation ID: 0b533b5e-08b6-44f9-b885-c2de291ba456
    Extended PID: 03612-05188-162-433277-03-1043-19045.0000-3282025
    Product Key Channel: Volume:MAK
    Partial Product Key: PDQ36
    License Status: Licensed
    
        The product is permanently activated.
    ____________________________________________________________
    
    Name: Windows(R), Client-ESU-Year2 add-on
    Description: Windows(R) Operating System, VOLUME_MAK channel
    Activation ID: 1043add5-23b1-4afb-9a0f-64343c8f3f8d
    Extended PID: 03612-05151-024-754071-03-1043-19045.0000-3282025
    Product Key Channel: Volume:MAK
    Partial Product Key: YWWJX
    License Status: Licensed
    
        The product is permanently activated.
    ____________________________________________________________
    
    Name: Windows(R), Client-ESU-Year3 add-on
    Description: Windows(R) Operating System, VOLUME_MAK channel
    Activation ID: 83d49986-add3-41d7-ba33-87c7bfb5c0fb
    Extended PID: 03612-05152-087-780173-03-1043-19045.0000-3282025
    Product Key Channel: Volume:MAK
    Partial Product Key: TMYCM
    License Status: Licensed
    
        The product is permanently activated.
    ____________________________________________________________
    
    Name: Windows(R), Client-ESU-Year1 add-on
    Description: Windows(R) Operating System, VOLUME_MAK channel
    Activation ID: f520e45e-7413-4a34-a497-d2765967d094
    Extended PID: 03612-05150-069-054197-03-1043-19045.0000-3282025
    Product Key Channel: Volume:MAK
    Partial Product Key: BKRWW
    License Status: Licensed
    
        The product is permanently activated.
    ____________________________________________________________
    
    Name: Windows(R), Professional edition
    Description: Windows(R) Operating System, OEM_DM channel
    Activation ID: 040fa323-92b1-4baf-97a2-5b67feaefddb
    Extended PID: 03612-03557-000-759887-02-1043-19045.0000-3282025
    Product Key Channel: OEM:DM
    Partial Product Key: XW3W7
    License Status: Licensed
    
        The machine is permanently activated.
    ____________________________________________________________
    
    Client Licensing Check information:
        AppId=55c92734-d682-4d71-983e-d6ec3f16059f
        LastConsumptionReason=0x00000000
        LastNotificationId=Cleanup
        LicenseState=SL_LICENSING_STATUS_LICENSED
        PartialProductKey=XW3W7
        ProductKeyType=OEM:DM
        SkuId=040fa323-92b1-4baf-97a2-5b67feaefddb
        ruleId=379cccfb-d4e0-48fe-b0f2-0136097be147
        uxDifferentiator=OEM_DM
        LastActivationHResult=0x00000000
        LastActivationTime=2025-11-24:10:43:30
        IsWindowsGenuine=SL_GEN_STATE_IS_GENUINE
        IsDigitalLicense=FALSE
        SubscriptionSupportedEdition=TRUE
        SubscriptionEnabled=FALSE
    ____________________________________________________________
    
    
    Press 0 key to exit.
     
  19. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,610
    100,025
    340
    "IsDigitalLicense=FALSE" means not HWID

    yes