Microsoft Activation Scripts
Version 3.12 · Open source project · Windows 8 / 8.1 / 10 / 11 · ranked #63 in the library
An open collection of activation scripts distributed as readable text rather than a compiled binary, run from a simple menu, aimed at people who want to see exactly what a tool does before it touches the licensing store.
Read the installation section below before you start. The order of the steps matters on this release.
About this release
Overview
This is a set of scripts rather than an application. It runs from a menu, offers a small number of activation methods for the system and the office suite, and does its work through the licensing services that are already present rather than by installing anything of its own. The whole point of the project is transparency: the scripts are plain text, they are published openly, and anyone who wants to read exactly what each method does before running it can open the file and check.
The menu keeps it approachable. Launch it, read the short description of each method, and pick the one that matches your situation. There is a status readout that reports the current licensing state before you change anything, which is usually enough to tell you which method is appropriate. Nothing installs, nothing registers a permanent service unless the method you choose requires one, and the folder can be deleted afterwards with nothing left behind.
Because it works through the standard licensing plumbing rather than patching binaries, it tends to survive updates better than tools that modify system files. The trade is that it is command driven and text based rather than a polished window, which suits the audience it is aimed at. This package is the current release with all methods present and the help text intact.
What it does
Feature breakdown
Distributed as readable scripts
Plain text you can open and inspect before running, which is the reason the project exists rather than shipping a compiled tool.
Menu driven
A short list of methods with a description of each, so you choose the one that fits rather than running everything in turn.
Status readout
Reports the current licensing state before you make any change, which usually makes the right method obvious.
Works through standard services
Uses the licensing plumbing already present rather than patching binaries, so it tends to survive updates.
System and office coverage
Methods for both the desktop system and the office suite across recent generations.
Portable and self cleaning
Nothing installs unless a chosen method needs it, and the folder can be removed afterwards.
Changed in this build
Version 3.12
- Menu text clarified with a plain description of what each method changes.
- Status readout expanded to report the channel a product was installed from.
- Improved detection of a state left behind by an interrupted previous run.
- Compatibility refreshed for the current system build.
- Several help entries rewritten for clarity.
Installation
Follow these in order
- Disable real time protection. Activation scripts are flagged on sight and quarantine will break the menu.
- Extract the archive to a folder you control.
- Run the launcher as administrator.
- Read the status readout to see the current licensing state.
- Pick the single method that matches your situation and let it complete.
- Reboot, verify the state, then re-enable protection and add an exclusion only if you keep the folder.
Release notes
From whoever packed it
- Detections are expected because of what the scripts do, not because of this specific build.
- Do not run more than one method against the same product. Overlapping changes are the usual cause of a broken licensing store.
- Because the scripts are plain text, read the one you intend to run first if you want to know exactly what it does.
System requirements
Minimum and recommended
| Operating system | Windows 8 through Windows 11 |
|---|---|
| Processor | Any x86 or x64 processor |
| Memory | 1 GB |
| Privileges | Administrator rights are required to run the scripts |
| Storage | 20 MB of free space |
Questions about this release
Answered before you ask
- Why does antivirus flag it?
- Any tool that changes licensing state is classified as a risk tool by every engine. That is about behaviour, not about this build.
- Do I have to install anything?
- No. It runs portable from the folder and most methods leave nothing permanent behind.
- Which method should I pick?
- Read the status readout first. It reports the product and channel, which determines the appropriate method.
Download
Pick a mirror