Microsoft has officially disabled the KMS38 offline activation method for Windows 10 and Windows 11, a technique widely used by hackers and enthusiasts for years. While the change was implemented recently, official release notes do not mention this update, leaving users surprised.
What Was KMS38?
KMS38 originated from the Massgrave project (MAS – Microsoft Activation Scripts), known for its repository of unofficial tools for activating Windows and Office.
The method worked by:
- Exploiting the GatherOSstate.exe utility, which checks system eligibility for upgrades.
- Extending the Key Management Service (KMS) activation period from 180 days to January 19, 2038.
This date was chosen due to the Y2K38 problem, which prevents setting a later date.
Timeline of Microsoft’s Crackdown
The fight against KMS38 began nearly two years ago:
- January 2024:
gatherosstate.exedisappeared from Windows build 26040, resetting activation grace periods during major upgrades. - October 2025: Optional update KB5067036 removed GatherOSstate completely.
- November 2025 Patch Tuesday: Updates KB5068861 and KB5067112 delivered the final blow, making KMS38 non-functional.
Massgrave developers confirmed the change, removing KMS38 support in MAS version 3.8.
Why Did Microsoft Remove KMS38?
KMS38 allowed offline activation without contacting Microsoft servers, making it a favorite among hackers. By eliminating GatherOSstate and related mechanisms, Microsoft aims to:
- Prevent unauthorized activations
- Strengthen licensing compliance
- Reduce piracy risks
Alternatives Recommended by Massgrave
Massgrave suggests switching to:
- HWID (Hardware ID activation)
- TSforge method
Both remain functional and are included in the latest MAS release.
Interestingly, reports from 2023 revealed that Microsoft support engineers themselves occasionally used Massgrave tools, highlighting their popularity.
Open Source and Microsoft’s Stance
Massgrave’s tools have long been open source, with project files available on Microsoft’s own GitHub. Despite this, Microsoft has historically taken no direct action against the project, focusing instead on patching loopholes like KMS38.
Impact on Users
For those relying on KMS38:
- Future upgrades and reinstalls will require new activation methods
- Offline activation via KMS38 is no longer possible
- Organizations using unofficial scripts must transition to legitimate licensing or alternative methods
