KMSpico
11.2.0
KMSpico is a KMS host emulator and activation client for Windows and Office, packaged as a single self-contained executable. v11.2.0 is the first release of the full rewrite of KMS ELDI from VB.NET to C# / .NET 9 — one executable for x64 and x86, with the Office hook DLLs embedded as resources and extracted at runtime, so there is nothing to install alongside it.
Version
11.2.0
11.2.0
Report this app
Description
KMSpico Overview
KMSpico is a KMS host emulator and activation client for Windows and Office, packaged as a single self-contained executable. v11.2.0 is the first release of the full rewrite of KMS ELDI from VB.NET to C# / .NET 9 — one executable for x64 and x86, with the Office hook DLLs embedded as resources and extracted at runtime, so there is nothing to install alongside it.
Features of KMSpico
- Emulates an MS-KMS host (protocol versions 4, 5 and 6) for other machines on the network, and activates this machine as a KMS client.
- Detects and uses a genuine digital/OEM licence when the machine already has one, instead of emulating anything.
- Installs and manages product keys and GVLKs.
- Activates Office — 2010 (MSI) and 2013/2016/2019/2021 (Click-to-Run) — through KMS or through the Office hook.
- The protocol core is verified byte for byte against an independent reference implementation (py-kms), using captured reference vectors that live in the test suite.
- The activation planner is a real decision engine, in the spirit of MAS / TSforge: it picks the method that fits the situation and explains why it picked it.
- The whole program, diagnostic log included, in 18 languages.
What it activates
- Windows — the method is picked automatically, in this order
- Digital licence — a genuine OEM/retail ticket is honoured and turned into a permanent digital licence.
- KMS client — volume licence, 180 days, renewed automatically by the scheduled task.
- OEM/SLP — machines with a SLIC table in the firmware get a local OEM licence, no host needed.
- TSforge — direct write to the licensing store when none of the above applies.
- Office — one method per product, not one for the whole machine
- Office 2019 / 2021 / 2024 / Microsoft 365 (Click-to-Run) — activated through the Ohook hook. Verified: Microsoft Word reports “Product Activated”.
- Office 2010 (MSI) — activated as a KMS client. Verified: Word 2010 reports the product as activated, full 180-day KMS interval. This is the method we recommend for Office 2010.
- Office 2013 / 2016 (MSI) — KMS client or hook, whichever fits.
- Any already-activated MAK / Retail / OEM licence — not touched. A real licence is never overwritten.
Not activated — please read
- Windows 7, Windows 8, Windows 8.1 — the program does not run at all. It is built on .NET 9, and Microsoft’s last runtime to support Windows 7 / 8.1 was .NET 6 (support ended 12 November 2024). There is no .NET 9 for those systems. Windows 10 or newer is required.
- Office preview / evaluation editions — no public volume key exists for them.
- A retail Office with no product key installed — the hook does not invent licences. If Word says “This product is unlicensed”, install a key first.
- Office 2010 through the Ohook hook — it works, but it does not hold on Windows 11: Office’s own repair (“Configuration Progress”) keeps restoring the original licensing client. Use the KMS method for Office 2010 instead — that one is verified end to end and does not modify the Office installation.
System Requirements for KMSpico
RAM: 2 GB
Operating System: Windows 10 and 11
Space Required: 400 MB
What's new
- Every message now comes from one catalog in your Windows display language — all 130 diagnostic messages and all 36 activation-planning explanations. In v11.1.0 the GUI was translated but the log was Spanish and English mixed, and the console output was always Spanish even on an English Windows.
- Fixed: the Office hook went to the wrong target when Office 2010 and a Click-to-Run Office were installed on the same machine. The target was decided from a machine-wide flag, so both products received the Click-to-Run hook; Office 2010 never loads that hook and stayed unactivated while the program reported "Ohook deployed". The target is now decided per product.
- Fixed: the program could report the Office hook as deployed when it was not. The check looked only for the backup file, so once Office repaired its licensing client the program believed the hook was in place. It now checks that the licensing client really is the hook, and puts it back if it is not.
- Fixed: a real race in OEM/SLP activation. The SLIC key catalog published its "loaded" flag before filling the list, so a second thread could read an empty catalog and activate with no key at all.
- Fixed: the retail to volume conversion looked for a package that does not exist, so it silently did nothing. A retail Click-to-Run Office can now be converted and activated as a KMS client without depending on the hook.
- Fixed: the window title could show the wrong version. It is now read from the binary itself.
