A collection of activation/evaluation extension methods for Windows Vista through 11.
A collection of activation/evaluation extension methods for Windows Vista through 11.
By WitherOrNot & asdcorp
A collection of activation/evaluation extension methods for Windows Vista through 11.
Note: We provide no support for direct use of this tool. The only supported implementation of the methods presented here is in Microsoft Activation Scripts.
Included methods and tools:
…This tool manipulates data stored in a file known as the "physical store", which is used by Windows to store critical activation data, including expiry timers and the HWIDs bound to each license. Thanks to our reverse-engineering efforts, we are able to insert our own data into the physical store, allowing us to add custom activation data for any product managed by Windows' Software Protection Platform. The data in the physical store is also known as the "trusted store", leading to the name "TSforge".
TSforge offers the most advantages for activating older Windows versions, such as Windows 7 through 8.1, as it can permanently activate any edition of these versions without modifications to the boot process or Windows system executables. TSforge is also the only public activator capable of activating any Windows addon, making it useful for users who wish to activate ESU licenses. Additionally, TSforge is the only public activator to offer hardware-invariant activation without any persistent network connections, added services/tasks, or injected DLLs.
TLDR: You should only use TSforge if you are using an old Windows release or if you want to activate addons such as ESU to extend the support end date.
For Windows 10 and 11, it is recommended to use the HWID method to activate Windows. TSforge is both less reliable and lacks features that HWID offers, such as the ability to survive feature upgrades and complete OS reinstalls. For Windows 7 through 8.1, there are no notable downsides.
No, none of the methods presented here require connecting to the internet in order to function. Everything is done locally.
You can use the /igpk switch in TSforge in order to install licenses by only using an Activation ID. You can get a list of all installable licenses and their Activation ID's by running slmgr /dlv all. You can click into the popup window and press CTRL + C to copy all of the information. Once you have found your desired licenses' Activation ID, run /igpk like so: TSforge.exe /igpk <activation id>.
You can use the /igpk and /zcid options with the activation ID of the KMS Host SKU to be activated. You can then use the /kmsc option with this activation ID to charge the KMS server with 25 clients. Please note that KMS servers will maintain their client counts for a maximum of 30 days.
The following options are implemented:
/dump/load/zcid/kms4k/rtmr/rrmc/kmsc/ctprThe following options are NOT implemented:
/duid - Key Unique ID is not removable from Vista physical store/igpk - Product key data is derived directly from the key string, preventing forgery/siid - IID is also derived directly from the key string/revl - Eval key lock is not present on VistaEffectively, this means that a product key must be provided to activate a given SKU. Additionally, ZeroCID on Vista/Server 2008 lacks protection against deactivation due to the WGA update KB929391, though this update is no longer offered via Windows Update.
If generic keys are installed, you need to run TSforge.exe /duid to remove the product key's unique ID. This will prevent WAT from verifying the key online. Installing a fake product key with TSforge.exe /igpk <activation id> will have an equivalent effect. Alternatively, you can use a non-generic key to bypass this check, though many publicly available keys are blocked by WAT.
Windows doesn't support AVMA activation under VM software that fails to provide Hyper-V Enlightenments. This primarily means that AVMA4k is only supported on VMs running under a correctly configured QEMU instance or Hyper-V. If your VM's activation status is Notification with the status code 0xC004FD01 after using AVMA4k, you will need to use another activation method.
It can, though we do not provide official support for these versions. TSforge works on most insider/beta builds of Windows past Windows 8.1. Beta builds prior to build 9600 are likely to face issues, as the internal data formats used by SPP were constantly changing during this period of development. Builds with similar licensing behavior to retail versions are the most likely to work with the current TSforge codebase. For other builds, you may need to manually edit the source code of LibTSforge to get it to work.
Run Microsoft Activation Scripts, select Troubleshoot > Fix Licensing. This will reset the physical store and revert any changes made by TSforge.
Yes, albeit with some amount of difficulty.
Probably not. If they do, please tell us so we can laugh to ourselves like a bunch of lunatics for the rest of the week.
C:\dotnet-sdk-9.0.200-win-x64TSforge.slnx can be foundC:\dotnet-sdk-9.0.200-win-x64\dotnet build -c ReleaseTSforgeCLI\bin\Release\net35The project is licensed under the terms of the GNU General Public License v3.0.
No open issues yet, or sync has not completed.