About this project

What this site publishes

• Explanations of the activation mechanisms: KMS leases, HWID digital licences, Ohook Office licensing and TSforge.
• Version and compatibility information for the KMSAuto family of builds.
• Verification data — file name, size and SHA-256 — for the archive offered here, published on the security page.
• Troubleshooting references for Windows and Office licensing errors, based on Microsoft's own slmgr and ospp.vbs tooling.

What this site does not claim

• It is not affiliated with, endorsed by or connected to Microsoft.
• It does not claim that any build is malware-free, audited, code-signed or certified by a security vendor.
• It does not publish checksums, scan results or release dates that have not been verified — missing values are marked as such instead.
• It does not grant any licence. KMS is a Microsoft volume-activation protocol; licence compliance stays with the user.

How release information is maintained

When the archive served here changes, the version, publication date, file size and SHA-256 are recorded and published on the security page. Any field that has not been verified against the actual file stays visibly empty rather than being estimated.

Reporting an issue

Report a checksum mismatch, a broken page or an inaccurate technical statement through the contact page. Reports that include reproducible detail — file name, hash, engine and date, or the exact error code and Windows build — are the ones that can be acted on and published.