Overview
This package is a set of scripts rather than a compiled tool, which is exactly why it has the reputation it does. Every method it uses is plain text that can be opened in a text editor and read line by line before anything runs, and nothing is packed, obfuscated or hidden behind an installer. For anyone who is nervous about running a binary from a download site, that transparency is the whole selling point.
The console menu offers the common activation routes and explains what each one does before it starts. It covers the current desktop Windows editions, the server editions, and the Office family from the older perpetual releases through the current ones. Each route reports what it changed and can be reversed from the same menu, so a machine can be put back the way it was found.
Because it is script based there is nothing to install and nothing left running afterwards. The package runs from a folder, does its work, and can be deleted. There is no tray icon, no background service and no scheduled task unless one of the renewal options is explicitly chosen from the menu, in which case the task it creates is listed by name so it can be removed later.
What it does well
Readable source
Everything is plain script text. No packing, no compiled payload, and every command is visible before the menu runs it.
Console menu
A numbered menu with a short description of each route, current status readout, and a confirmation step before anything is changed.
Wide coverage
Handles the current and previous Windows desktop editions, server editions, and the Office perpetual and subscription application sets.
Reversible
A removal option undoes what was applied and clears anything the tool registered, including the optional renewal task.
Nothing left behind
No install, no service, no tray process. The folder can be deleted once the menu is closed.
Changes in this build
- Menu reorganised so the status readout appears before the route list.
- Support added for the current Windows feature branch and the newest Office application set.
- Removal routine extended to clear entries left by other tools.
- Logging improved with a per-run text log written next to the script.
- Fixed a failure on systems where the script host was restricted by policy.
What is in the package
- Activation script package, unpacked
- Console launcher with the numbered menu
- Removal and status check routines
- Optional renewal task installer
- Readme covering each route in detail
System requirements
| Processor | Any x86 or x64 processor |
| Memory | 512 MB |
| Graphics | Not applicable |
| Storage | 10 MB free |
| Display | Console, any resolution |
| System | Windows 8.1 through Windows 11, and the current server editions |
Installation
- Extract the folder to a local drive, not a network share.
- Add an exclusion for the folder in the security software before extracting.
- Open the readme and skim the route you intend to use.
- Run the launcher and pick the numbered option from the menu.
- Read the confirmation line, then let the routine finish without closing the window.
Before you start
Security software flags activation tooling by category, which is expected. Set the exclusion before extraction or the files are removed mid-copy.
Run the status check first, some systems are already in the state the user was trying to reach.
Do not run two different activation tools against the same machine, clean up the first before trying another.
Questions about this title
Is there a compiled binary?
No, the package is script text. That is the reason people pick it over packed tools.
Does it install anything?
No. Optionally it can register a renewal task, and that task is named so it can be removed later.
Which Office releases are covered?
The perpetual releases from the older cycles through the current ones, plus the subscription application set.
Can the changes be undone?
Yes, the removal option in the same menu reverses what was applied.
About this listing
This entry was checked on a clean install of Windows 8.1 / 10 / 11 and Server before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.