MAS activation methods compared
MAS bundles several unrelated activation techniques behind one menu, and picking the wrong one is the most common reason an activation attempt fails. This page compares what each method supports and what its trade-offs are. Method behaviour is documented by the project itself — see the official documentation for the authoritative description.
| Method | Windows | Office | Type | Internet | Persistence | Typical use | Limitations | |
|---|---|---|---|---|---|---|---|---|
| HWID | Windows 10, 11 | No | Digital license tied to hardware | Required | Permanent for that hardware | A normal desktop or laptop you keep | Re-runs needed after major hardware changes; not for Server or Office | Official docs |
| Ohook | No | Office 2013–2024, Microsoft 365 apps | License-check hook | Not required | Permanent while the hook stays in place | Activating Office, including offline machines | Office only; can be undone by some repair/reinstall operations | Official docs |
| TSforge | Windows, Windows Server, ESU | Yes | Licensing store entry | Required on newer builds (26100+) | Permanent | Editions and products the other methods do not cover, including ESU | Newest and most build-sensitive method; behaviour varies by build | Official docs |
| KMS38 | Windows 10, 11, Server | No | Extended KMS expiry | Not required after setup | Until 2038 | Editions with no HWID path, e.g. Server and some LTSC scenarios | Windows only; a dated expiry rather than a true digital license | Official docs |
| Online KMS | Windows, Windows Server | Yes | External KMS host | Required for every renewal | 180 days, renewed by a scheduled task | A fallback when a permanent method is unavailable | Depends on a reachable external host; stops if renewals fail | Official docs |
Every row links to the upstream documentation for that method. Where this page and the official documentation disagree, the official documentation is correct — tell us and we will fix the row.
Notes that are easy to miss
- "Supports Office" is not the same as "activates Office the same way". Ohook intercepts the licence check locally; TSforge writes into the licensing store. A repair or major update affects those two very differently.
- Internet requirement is about the moment of activation, not afterwards. HWID needs a connection once to obtain the digital licence; Online KMS needs one on every renewal, forever.
- Build sensitivity matters more than age. TSforge behaviour differs across Windows builds, which is why a method that worked on one machine can fail on another running a newer build.
- Nothing here changes licence entitlement. These methods change activation state; they do not grant you a licence from Microsoft.
How to choose
- Windows 10 or 11 on your own machine — HWID first; it survives reinstalls of the same edition on the same hardware.
- Office of any recent version — Ohook; it is the only method here designed for Office and works without a connection.
- Windows Server, ESU, or an edition HWID refuses — TSforge, then KMS38 as a fallback.
- Nothing permanent applies — Online KMS, accepting the 180-day renewal cycle.
Reading the "permanent" column honestly
Permanent here means "no expiry date is set", not "cannot ever be undone". Hardware changes, edition changes, Office repairs and future licensing changes on Microsoft's side can all invalidate a state that was permanent when it was applied. KMS38's 2038 date and Online KMS's 180 days are, by contrast, explicit expiries.