Choosing an activation method without guesswork
Most Microsoft Activation Scripts (MAS) questions come down to one thing: which method fits the product in front of you. The MAS menu lists several options, but they are not interchangeable — each one targets a different licensing mechanism. This page turns that choice into a short decision tree you can follow in under a minute.
Step 1 — Identify the product
Start with what you are activating, not with the method name.
- Windows 10 or Windows 11 client edition → continue to step 2.
- Windows Server → HWID does not apply; look at KMS-based options.
- Microsoft Office (2016 through the current perpetual releases, including LTSC) → Ohook is the method designed for Office.
- Older or unusual builds (Vista, 7, 8.1, Server 2008/2012 era, some IoT SKUs) → TSforge is the option upstream documents for those cases.
Step 2 — Does the edition support a digital licence?
HWID produces a hardware-bound digital licence stored on Microsoft's activation servers. It only covers the client editions Microsoft issues digital licences for. If your edition is on that list, HWID is normally the cleanest result: it survives a clean reinstall of the same edition on the same board, and it needs no scheduled task.
If the edition is not covered — Enterprise G, some education and regional SKUs, Server — HWID will simply fail. That is expected behaviour, not a broken script.
Step 3 — Will the machine be online?
- Permanently offline, supported edition → KMS38 sets the activation expiry far into the future without needing a renewal task or a reachable KMS host.
- Occasionally online → Online KMS works, but relies on a renewal task that must be allowed to run.
- Normally online, supported edition → HWID first, KMS38 as a fallback.
Step 4 — Confirm the result, do not assume it
After any method, verify instead of trusting the on-screen message:
slmgr /xpr
slmgr /dlv
For Office, the equivalent check is ospp.vbs /dstatus from the Office installation folder. A method that "ran successfully" but left the licence unchanged is one of the most common sources of confusion in support threads.
Quick reference table
| Situation | Method that normally applies | Persistence |
|---|---|---|
| Supported Windows 10/11 client edition, online | HWID | Tied to hardware, survives reinstall |
| Supported client edition, offline | KMS38 | Long-dated expiry, no renewal task |
| Windows Server, volume editions | Online KMS | Renewal-based |
| Microsoft Office / LTSC Office | Ohook | Persistent while the hook file remains |
| Legacy Windows and Server builds | TSforge | Depends on product |
When the tree does not resolve
If none of the branches fit, the safest next step is reading the upstream documentation rather than trying methods at random. Running one method after another can leave mixed licence state that is harder to diagnose than the original problem. The upstream project publishes per-method notes at massgrave.dev and the scripts themselves are readable in the repository.
Common mistakes this tree prevents
- Trying HWID on Office. HWID has no Office path at all.
- Using Online KMS on a machine that will be permanently offline and then wondering why activation lapses.
- Deleting the scripts after a renewal-based activation.
- Treating an antivirus detection as proof that a method failed — the detection happens before the method even runs.
Related reading
- MAS activation methods compared
- MAS version history (upstream releases)
- Activation troubleshooting
- Security and source verification
massgrave.download is an independent documentation and troubleshooting resource. It is not the official Massgrave project. The official project lives at massgrave.dev and github.com/massgravel.