Overview
KMSOffline exists for the case where the machine has no network connection at all, or where a resident component is out of the question. It runs from a single executable, applies the licensing state locally in one action, and closes. There is no service, no scheduled task, no folder installed somewhere and nothing to remove afterwards. Delete the file and the machine is exactly as it was.
It covers the volume channel Windows editions and the volume channel Office suites, which is the same ground the other tools on this site address, but with the simplest possible mechanism. For a machine being prepared offline, for a virtual machine that never touches a network, or for anybody who would rather not leave anything behind, this is the direct answer.
How it works and what it touches
The interface is one window. It detects the installed products, lists them with their current state, and offers a single action to apply the licensing. The result is reported per product in a log pane, with the failure reason printed when something does not take, rather than a single unhelpful message.
Everything happens locally against the installed products. No connection is opened, no external address is contacted, and nothing is downloaded during the operation. That is the entire design goal and it is what makes the tool suitable for an air gapped machine or a network where outbound traffic is watched.
The changes it makes are to the licensing state of the products themselves. Nothing is written into the startup sequence, no driver is loaded, and no component is registered. When the window closes, the tool is not running.
What it covers
On the Windows side, the volume channel client editions from 7 forward and the corresponding server editions are supported. A retail channel installation is converted to the volume channel first where the edition allows it, which the tool handles as part of the same operation.
On the Office side, the volume channel suites are covered, which is the variant of the 2010 through 2024 lines posted on this site. Subscription channel installations are a different mechanism entirely and are not addressed here. If a subscription channel suite is what is installed, replace it with a volume channel one first.
A state check runs automatically when the window opens, so you can see what is installed and what condition it is in before doing anything. On a machine somebody else set up, that first screen is often the most useful part.
Running it
Run it as administrator, since the licensing state cannot be changed from a standard user context and the tool will report a failure rather than a permission error if you forget. Suspend real time protection first, or the executable will be quarantined before it opens, which every scanner will do because manipulating licensing state is precisely the behaviour their definitions describe.
One run is enough. There is nothing to schedule and nothing to maintain. If the state ever lapses, run the file again. Keeping the executable on a stick alongside the other tools is the usual arrangement, since it needs no installation to be ready.
What you get
- Single executable with no installation and nothing left resident
- Works entirely offline with no outbound connection at any point
- Automatic state check on open showing every installed product
- One action applies the licensing state across detected products
- Per product result logging with failure reasons printed
- Volume channel Windows client and server editions from 7 forward
- Volume channel Office suites across the supported lines
- Retail to volume channel conversion where the edition allows it
- Runs on both 32-bit and 64-bit systems
- Portable, runs from a stick without touching the system
Inside the archive
- KMSOffline executable, single file
- Readme covering supported products and channels
- Notes on running as administrator and scanner exclusions
- Change history for the recent versions
- Interface language files for the options listed above
System requirements
| Operating system | Windows 7 or later, or Windows Server 2008 R2 or later |
|---|---|
| Privileges | Administrator, the tool cannot work otherwise |
| Products | Volume channel Windows or Office installations |
| Storage | 20 MB free |
| Antivirus | Real time protection suspended during the run |
| Network | Not used at any point |
Installing it
- Unpack the archive to any folder, including one on a removable stick.
- Suspend real time protection, or the executable will be quarantined before it opens.
- Right click the executable and run it as administrator.
- Read the state check that appears when the window opens.
- Apply the licensing and read the per product results in the log pane.
- Close the window and delete the file. Nothing remains on the machine.
Mirrors
| Route | Region | Note | State |
|---|---|---|---|
| Direct, primary | Europe | No wait, resumable | Online |
| Direct, secondary | North America | No wait, resumable | Online |
| Torrent magnet | Global | Direct is faster, the file is tiny | Online |
Release history
- Product detection updated for the current Office volume build numbers
- Fixed a failure on server editions with a specific installed role set
- Log pane output reworked to be readable at a glance
- Retail to volume conversion extended to another client edition
- Reduced the executable size by removing obsolete product tables
- State check now runs automatically when the window opens
- Failure reasons printed rather than reported generically
Questions about this release
Does it need an internet connection?
No, at no point. Everything happens locally, which is the reason this tool exists.
Does anything stay on my machine?
No. There is no service, no scheduled task and no installed folder. Delete the executable when you are done.
Will it work on a subscription channel Office?
No. Replace it with a volume channel installation first, then run this.
Why does my scanner delete the file on sight?
Because manipulating licensing state matches its definitions exactly. Suspend protection for the run and it will open normally.
Do I need to run it again later?
Only if the state lapses. There is nothing to schedule, so keep the file somewhere and run it again if needed.
Comments
Keep it on the same stick as my rescue tools. No install, no traces, runs anywhere.
Server role failure is fixed here. Previous version would just stop with nothing useful printed.
Comments are read before they appear. If a build stops working, say so here and it gets rebuilt rather than quietly left up.
Machine has never been on a network and this still did the job in one click. That is exactly what I needed.