Overview
KMSAuto++ is the small tool that sits at the end of a lot of install guides. It does one job, which is to put a Windows or Office installation into a licensed state and keep it there, and it does that job without an installer, without a service left running in the background and without any of the configuration a manual approach would need. You unpack it, run it, press the button for the product you want handled, and it reports back what it did.
This is the current build of the utility, portable, with no setup routine at all. The interface is deliberately plain: a product selector, an information panel that reads the current licensing state off the machine, and a small set of manual tools behind a second tab for the cases where the automatic path does not apply. Everything it changes is visible in the log pane while it works, which is the reason this particular utility has outlasted most of the alternatives.
What the tool actually does
The utility installs the appropriate product key for the edition it finds, points the machine at a local service that answers the activation request, completes the handshake, and then removes the temporary pieces it created. The whole sequence takes a few seconds on a normal machine. If the edition on the machine is one that cannot be handled that way, the tool says so plainly rather than reporting a false success, which is more than can be said for a lot of similar utilities.
A renewal task can be added to the task scheduler so the licensed state refreshes itself on a schedule rather than lapsing after the usual interval. The task is a single entry with a visible name, it runs silently, and it can be removed from the same tab that created it. If you would rather not have a scheduled task at all, skip that step and re-run the tool manually when the state lapses.
The manual tab
Behind the main screen there is a set of individual operations for people who want to see each step separately. You can install or remove a product key, set or clear the service address, inspect the full licensing information dump for both Windows and Office, and force a state refresh without touching anything else. This is where you end up when a machine has been through several previous attempts by other tools and the state is confused.
There is also a cleanup routine that removes leftover keys and stale service entries from earlier attempts. Running that first on a machine with a messy history solves most of the cases where the automatic path reports a failure for no obvious reason.
Notes on the build
The archive contains a single executable and a readme. Nothing else is written to disk except the log file the tool creates next to itself, and the scheduled task if you choose to create one. There is no bundled extra, no toolbar, no optional offer during a setup step, because there is no setup step.
Every scanner on the market flags this category of utility on sight. That is expected and it is not a comment on this particular file. The tool writes to licensing state, which is exactly the behaviour heuristic detection is built to notice. Suspend protection while it runs, or add the folder as an exclusion if you intend to keep it around for the scheduled renewal.
What you get
- Single portable executable with no installation step
- Handles Windows and Office in the same interface
- Reads and displays the current licensing state before changing anything
- Optional scheduled renewal task that can be removed from the same screen
- Manual tab with individual key, service and state operations
- Cleanup routine for machines left messy by previous attempts
- Full visible log of every step while it runs
- English and Russian interface, selectable from the menu
- Works on both 32-bit and 64-bit installations
Inside the archive
- KMSAuto++ portable executable
- Readme covering the manual tab operations
- Exclusion note listing the folder paths to whitelist
System requirements
| Operating system | Windows 7 or newer, 32-bit or 64-bit |
|---|---|
| Framework | .NET Framework 4.6 or newer, present on Windows 10 and 11 by default |
| Privileges | Administrator rights required |
| Memory | 512 MB free |
| Storage | 40 MB free for the tool and its log |
| Other | Real time protection suspended for the duration |
Installing it
- Unpack the archive to a folder you will keep, not to a temporary location, if you plan to use the scheduled renewal.
- Suspend real time protection or add the folder as a permanent exclusion.
- Right click the executable and run it as administrator.
- Pick the product you want handled and let the sequence finish. Do not close the window while the log is still writing.
- Check the information panel afterwards to confirm the reported state, and add the renewal task from the second tab if you want it.
Mirrors
| Route | Region | Note | State |
|---|---|---|---|
| Direct, primary | Europe | No wait, resumable | Online |
| Direct, secondary | North America | No wait, resumable | Online |
| Torrent magnet | Global | Rarely needed at this size | Online |
Release history
- Updated edition detection for the current Windows 11 servicing branch
- Fixed the scheduled task failing to register on systems with a renamed administrators group
- Log pane now scrolls with the output instead of jumping to the top
- Cleanup routine now clears stale service entries left by other tools
- Reduced false failure reports on machines with several Office builds installed
- Office detection reworked for click to run installations
- Interface translations refreshed
Questions about this release
Does it need to stay on the machine afterwards?
Only if you created the scheduled renewal task. Without that task the tool has done its work and the folder can be deleted.
Will an update undo what it did?
A normal quality update will not. A feature upgrade that replaces the installation can, in which case run the tool again afterwards.
Why does my scanner delete it immediately?
It writes to licensing state, which is the exact behaviour detection heuristics look for. Add an exclusion before unpacking, not after.
Does it work on Home editions?
Some editions are handled and some are not. The information panel tells you which case you are in before you run anything.
Comments
Cleanup tab fixed a machine that three other tools had left in a mess. Should be the first thing anyone tries.
Had to whitelist the folder before unpacking or Defender ate it mid extract. After that, no trouble at all.
Comments are read before they appear. If a build stops working, say so here and it gets rebuilt rather than quietly left up.
Ran it on a fresh 11 install, took about six seconds and the state panel showed exactly what I expected. No leftovers.