Has MS even released any ESU updates yet? I tried the MAS tool and "successfully" activated ESU on plain consumer W10 Home, the Enroll Now dialog is gone but the End of Support message is still visible. Ran ardap86's little script and all 6 steps checks out. It seems those updates is already installed.
I just realized Win 10 LTSC is still in the mainstream support phase till Jan 2027. I wonder if that means LTSC will receive a different KB than 22H2 and if the LTSC KB will have additional non-security updates not included in the 22H2 ESU. Guess we'll find out next Tuesday.
IoT enterorise 2021 LTSC is officially supported till 2032, and no they should still get the same 19041 based updates.
From my personal view, since as a matter of principle, I don't want to send any diagnostic data from my machine to M$, it was important for me to realize the fact that the "fix" suggested by M$ actually enables the sending of diagnostic data to the manufacturer. Since I don't think it's worth for me doing that just to eliminate an erroneous message that doesn't affect the regular receipt of updates, I wonder if everyone who performed that "fix" then reverted the setting after having the satisfaction of seeing the EOS message disappear. I've already said elsewhere that the EOS message issue on IoT LSTC 2021 x64 can be solved without changing any settings at all, but simply by adding the two attached files to the "%ProgramData%\Microsoft\Windows\OneSettings" folder assuming it is empty just as it was here. Please note that I reduced the content of both "config.json" and "UsoSettings.json" files in order to keep themselves to a minimum working content and do not contain any sensitive information. At the end of the day, those two small files solve the EOS fake message issue under IoT LTSC 2021 x64 without changing any settings on your machine and therefore not affecting your privacy. config.json {"queryUrl":"/settings/v3.0/OneSettings/Client","settings":{"ENDPOINT.MUSE":{"Partner":"WSD","Feature":"Muse","CtacAppId":"Muse","StrictRefreshInterval":true,"OnDemandOnly":false,"Payload":{"PayloadHandler":"FILE","Metadata":{"Dir":"%ProgramData%\\Microsoft\\Windows\\OneSettings","Name":"UsoSettings.json"}}}}} UsoSettings.json {"queryUrl":"/settings/v3.0/WSD/Muse","settings":{"ESODATESTRING":"2055-10-15T00:00:00"}}
Yeah simply no update. it works on the Enterprise and Workstation Editions. I will now try it without the "ei.cfg" file "[Edition] [Channel] _Default [VL] 0". I use that to force the Edition Selection menu when a BIOS has an embedded Windows Key.
It will not be detected without one of these registry values: Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\ESU] "Win10ConsumerESUAY"=dword:00000009 "Win10ConsumerESUStatus"=dword:00000003 "Win10CommercialKeybasedESUEligible"=dword:00000001 "Win10CommercialW365ESUEligible"=dword:00000001 "Win10CommercialAzureESUEligible"=dword:00000001 you should run ClipESU.exe (in admin cmd) once to populate KeybasedESU value after activating TSforge ESU
Ahh with those Reg Keys it now works on Home/Pro/Education too after the TSforge ESU. Damn MickySoft.
I decided to do a test today with Windows 10 Pro Version 22H2 Build 19045.6456 64-bit. After doing a clean install, I purposely did not deploy the MAS/TSforge ESU tool. When I did a scan with Windows Update, it detected and installed the KB5071959 OOB fix and showed the build to be 19045.6466. I then went to the Microsoft Update Catalog site and downloaded the KB5068781 update. It appeared to install okay, but when it went through the configuration and reboot progress, it failed at 94% and reverted back to the previous condition. I then deployed the MAS/TSforge ESU tool, then selected option #3, then option #2. When I did a scan with Windows update, it detected and successfully installed the KB5068781 update which previously failed to install, and it showed the build to be 19045.6575. And the message about Windows 10 22H2 no longer being supported is no longer displayed in Windows Update.