KMS server can be set in two ways: Global - Windows and Office both can use that server. Specific - Only the specified products can use the added server. So, if you add a global KMS server to activate Office, it's going to activate Windows as well if the KMS key is installed. KMS server activation is for 180 days, so if Windows is activated with KMS38 (till 2038), the system will replace it with a 180-day KMS activation. To workaround this issue, so that if the user wants 180 days KMS for Office and KMS38 for Windows, we set a specific KMS address to the Windows product only and add a localhost address (not a valid 180 days KMS server), so KMS38 won't be affected by the 180 days global KMS server. Later, to make sure that when the user tries to activate the office using other KMS tools (MAS and KMS_VL_ALL can handle this without breaking KMS38), they won't replace KMS38, we started locking that specific KMS address registry. Now we are just adding a specific KMS server registry for Windows in KMS38, but not locking the registry anymore because that's kind of not a very good thing to do to touch the system in that way. Users now have better options to activate Office (Ohook, TSforge), and even if they want to use KMS, it's fine with KMS_VL_ALL and online KMS options in MAS. And even if they want to apply KMS commands manually for the office, it's fine because those normal commands don't touch the specific KMS server for Windows. Considering pros and cons, we have decided not to lock the registry anymore and keep it clean and nice.
4-6 Years ESU is not officially supported, but you can manually install Server 2008 R2 x64 updates until Jan 2026
One question, please: :: Can Windows Server also be activated with KMS4k+? Are there multiple activation options besides Online KMS and Host KMS, KMS4k+? Does Tsforge work with Windows Server 2025?
Morning everyone. I've used TSforge (ESU activation) on a couple of older Windows 10 computers. Both of them were originally setup with Local accounts. Will I need to login to a Microsoft account at least once to get the 3 years of updates or will it work just fine with Local Accounts? Regards, Paul
The commercial ESU (3 years) does not need anything except activating the license(s) with TSForge. @abbodi1406 has also made a script for Consumer ESU (1 year) that works without MS Account.
Thank you. It is good to know we can get the 3 extra years without having to create / login to a Microsoft account.
I understand that TSforge_Activation.cmd is sufficient for this purpose? What will happen to the current Windows activation? It's activated with a valid key. Should I use some TSforge command-line switch? It's not a major issue for me, but I'd like to provide extended support to a few friends, but with their systems retaining the same activation keys. Is this possible with TSforge?
The ESU licenses are additional licenses, the main activation remains untouched. TSForge is part of MAS, where ESU is a dedicated menu option.
Thank you, @Carlos Detweiller this is crucial information. I can't afford to experiment too much on my work computer. So the script I should run is MAS_AIO.cmd, correct? And after running it, I'll find the option to activate ESU. One thing I'm curious about is whether ESU activation needs to be repeated after reinstalling the system, or will it be assigned to the machine, just like system activation?
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.