Yeah, i already had the ESU stuff running on Oct. 14 2025 so i never got it offered on WU on my 19045 Pro x86 T100TA laptablet, all my other hardware is running IoT Enterprise 2021 LTSC, that also never got it offered.
That surprised me too. For me, it currently stands at 0:1. Mainsys Win10 Pro: OEM Key, 19045.6456, MAS TSforge ESU (yesterday): For reasons (I want to see if it gets installed automatically), I haven’t manually check for updates yet. Despite two reboots (I have to for other reasons), nothing has been installed so far. VM Win10 Pro: Generic key, MAS HWID months ago, 19045.6456: MAS TSforge ESU, 1. Check for updates: got KB5071959 (OOB), EOS message still there. 2. Check for updates: got KB5068781 (LCU), EOS message is gone. Greetings to everyone! Martin
I've already got the MAS/TSforge ESU tool deployed and licensed in Windows 10 Pro Version 22H2 Build 19045.6456 64-bit in 2 of my Dell Precision 3620 towers. I'll be checking them out tomorrow to see how Windows Update responds to a scan for November 2025 updates.
Updated the OP with the latest info: https://forums.mydigitallife.net/th...options-activation-and-troubleshooting.89665/
Exactly that happened to me on another VM... After MAS TSforge ESU: Win10CommercialAzureESUEligible = 0 Win10CommercialKeybasedESUEligible = 0 win10ConsumerESUStatus = 2 = no ESU Update. Running ClipESU.exe changed "Win10CommercialKeybasedESUEligible" to 1 and ta-da the ESU LCU was detected. Does ClipESU do anything other than setting the corresponding registry value? It would be nice if that were triggered by MAS - right? Is this actually documented anywhere by Microsoft? I couldn’t find anything quickly at least. My main system is still at 0/0/2 as well, but at least I should automatically receive the OOB – I’ll wait a little longer.
With most of the disclosed pre-requisites details applied for Windows 10 ESU enabling: Under Windows 10 Pro 22H2 x64 "reg.exe add "HKLM\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides" /v 4011992206 /t REG_DWORD /d 2 /f" , + running ConsumerESU Features Management, then ConsumerESU Enrollment scripts , + "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\ConsumerESU" Set Manually using Registry Editor ESUEligibility = 0x00000002 (2), ESUEligibilityResult = 0x00000003 (3) , + "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\ESU" Setting checked as: win10ConsumerESUStatus = 0x00000002 (2) 1 attempt was made for KB5068781 with its original .MSU file from MUC, and it was unsuccessful at 94% after restart. Downloading the latest version of W10UI_10.57, unpacking the .MSU files inside the W10UI directory and running the .cmd file with Administrator privileges, everything detected automatically and it was a simple "Press 0 to begin". The packages installed okay, the restart configurations passed and it worked all the way to 100%. I checked afterwards in "Programs and Features" - "View installed updates" and voila! -- Security Update for Microsoft Windows (KB5068781) was present, as well as "Servicing Stack 10.0.19041.6575". Even going to Settings - System - About , and scrolling down to Windows Specifications, the OS Build was 19041.6575 . This is an old Windows 8.1 Embedded Updates method I became familiar with, where utilizing W81UI worked out better than the BypassESU Blue for x86 versions. Here with Windows 10 ESU this is the current alternative success route where the TSForge method works only for those possessing the correct files. I also tried TSForge ESU activation online without success due to a missing ActivationWs.ActivationHelper file not present in the latest TSforge-1.1.1 folder. KMS4k and StaticCID online were the only 2 basic options for novice users with TSforge 1.1.1 without the fuss of zcid and igpk options. I'm content that W10UI v10.57 works for Windows 10 ESU. Windows 10 22H2 Enterprise is not ConsumerESU, but with W10UI v10.57 it took the November 2025 Cumulative Update also.
The installation requires activated ESU license to proceed, unless you mess with extendedsecurityupdatesai.dll. You don't need ActivationWs either, that's for StaticCID. Just use TSforge /igpk and /zcid options with the ESU activation IDs, or use MAS script.
It's mainly to enable Windows 365 ESU subscription, but it also check and set Azure / Keybased eligibility MAS 3.8 now trigger it no it's not documented
It worked for mee too. 1) Post1 TSForge option 3 then 2. 2) registry adjust from page 9 3) Clipesu under admin prompt. I had to reboot 2 times, perhaps because i had first get the no ESU update. W10 Familly.
Just wondered if anyone has noticed fresh install W10 home latest 22H2 ran all available updates available receiving the EOS message as expected. However run MAS 3.8 TS forge ESU applied ok Have just left computer for several hours after rebooting several times to see if the November update etc. will come through without manually pushing for them in updates. But as yet nothing has come through automatically as it use to ? Are we saying to receive future monthly updates using TS Forge ESU we have to push these ourselves manually each month ? as no automatic update so far seems to be running ? Thanks Guys !!
I hardly ever see WU triggered by itself to update, maybe because i am always pressing "search for updates" but also on client's pc's i don't see WU running by itself very often.
well here I am using version 1809 for testing and I was surprised when opening settings to check for updates; and to my amazement there were updates which I executed immediately; MSFT surprised me once again...
Thanks for that! I previously ran TSForge and ClipESU.exe but one of the values was 0 instead of 1. Checked WU again and bam, November update is downloading now!
Well surely if this was the case about 99% of people would never ever get any Windows updates installed ? Most people havent got a clue how to manually search & push for updates ? Pretty sure they trickle away in the background ( using the windows updates service ) and once ready you get the icon on the taskbar telling you updates are ready and please reboot your computer to complete updates
Yes, the majority of the global windows users are not tech people but simple users who just use windows.
With the MAS/TSforge tool deployed and ESU licensing confirmed, this is what Windows Update looked like before doing a check for updates: This is what Windows Update now looks like after detecting and installing KB5068781(19045.6575) and rebooting:
I guess you manually had to ask windows updates to check for KB5068781(19045.6575) ? So far its looking like you have to force the update ? Annoyingly its not finding this update without manual help ? Are we going to have to check ourselves each month from now on ? I am sure it never use to be like this prior to W10 EOS ?
I purposely have my Windows 10 PCs set that way to deal with Windows updates. I don't like having Windows updates automatically appear and install on their own without any intervention from me.