It seems to work. As I understand it, this is the output of the slmgr /dlv command? For me, this window doesn't fit on the screen, and I only see Client-ESU-Year6 and Year2, but I think everything is fine. Is there any way to make the output window of this command smaller or to save the output to a txt file? Either way, the method is incredibly simple and safe – I'll be able to help a few layman friends even remotely, and they should be able to handle it. Thank you for your help, best regards.
Nope, slmgr.vbs /dli /dlv is way too verbose for our purposes here. %windir%\system32\cscript.exe /NoLogo %windir%\system32\slmgr.vbs /dlv
thanks, I was installing Office 2024 on Windows 11 LTSC and keeping this error, I thought that MS patched the activation method, or that was an error of ARM64 architecture (this was on my Snapdragon laptop)
I read that Microsoft now intends to scan your PC periodically to check if you sign in to your Microsoft account at least once every 60 days. If not, they will expire ESU. If you only ever use a local account and have used TSforge to activate ESU, will ESU on your PC still be activated after this 60 day period is up?
Reddit posts always like FUD https://forums.mydigitallife.net/threads/discussion-windows-10-esu-license.89665/page-3#post-1891880
A short question to the activation process in TSforge with ZeroCID vs. StaticCID: While reading this thread, i understood the reason, why StaticCID was needed, and also why it was the default method beginning from Windows 10 (19041). In earlier post the question was asked, what will happen to PCs, which was activated with ZeroCID, when Microsofts publishes the same update to Windows 10, and the answer was, that all these ZeroCID activations will be invalidated. So my question is: beginning from MAS v3.7, the default method is again ZeroCID, and StaticCID is used only beginning from Windows 11 (Build 26100). So does the risk of backporting the dangerous update to Windows 10 no longer exist, which will invalidate the activations, which were done with ZeroCID?
We figured that the risk of them backporting the Windows 11 sppobjs is quite low at this point, and the benefits of ZeroCID over StaticCID outweigh it.
Windows Update on Windows 10 Home after using abbodi1406's ConsumerESU script shows that I am enrolled in ESU. TSForge's activation status shows no information on each year's addon. After removing the enrollment using the ConsumerESU script, Windows Update shows that I am eligible for enrollment. Running TSForge to activate the ESU shows Years 1-3 and Year 6 addons permanently activated. But Windows Update still shows that I am eligible for enrollment, not enrolled. After running TSForge, registry key HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\ConsumerESU\ESUEligibility has a value of decimal 2 meaning eligible for enrollment. It should be 3 for enrolled. Registry key HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\ConsumerESU\ESUEligibilityResult has a value of decimal 1 meaning success. Why does TSForge not update Windows Update to show that the ESU is activated?
Because the keys are set and needed only by Consumer ESU (the one year one) where end users need something to check as they usually don't know how to check licenses. The Business ESU (three years) deployed by TSForge has no need to brag with enrollment text are it is supposed to be deployed by corporate administrators using tools. In short: Business/Commercial ESU does not set up any text as the end users do not need to know, and the admins already know.
Code: cmd /c ClipESUConsumer.exe -evaluateEligibility and it will become 1 Ineligible + Result 12 + then check registry path: Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\ESU] values listed here is what WU will use to detect and offer ESU updates (not installing them)
I just ran TSforge from Powershell. It completed and said the first 3 years of ESU updates are activated. In Windows Update, the system is up to date but it still says "Windows 10 support ends in October 2025" and it has the option to enroll. Should that notice still be present? I ran slmgr.vbs /dli from cmd.exe but the popup didn't have any info about ESU status. Are there any good ways to check if the activation was successful?