TSforge Activation (Windows/ESU/Office) (MAS)

Cmd and write cscript slmgr.vbs -dlv

 

You need to login to view this posts content.

 

Hello,

Please consider displaying the installation key on the event screen.

Regards,

 

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)

 

How can I check to see if the ESU workaround works?

 

What workaround?

slmgr.vbs /dli will show activation status for ESU addons

 

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?

 

ESU from MAS is business version, i doubt they require to use an online msft account.

 

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?

 

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?

 

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?

 

Use massgrave license check section

 

You need to login to view this posts content.

 

Is it known yet if there will be years 3 - 6 of 10 ESUs ? Was there ever a Software Assurance program of some sort for 10 ?

 

Wasn't 6 just a placeholder?