Office Tool Plus: one PowerShell line installs a tool that deploys, repacks and activates Office

This repository holds translations, not the program that runs

The repository description is one line long: Office Tool Plus localization projects. That is the whole scope. The root listing is nineteen README files, one per locale, alongside `config/`, `src/`, `CONTRIBUTING.md`, `LICENSE`, `NOTICE.md` and `.github/`. There is no application source here, no installer, and no build for the tool itself, even though the primary language is recorded as PowerShell.

So the open code and the code you execute are two different things. The MIT licence covers the files in this repository. The tool itself is reached through two links that are not the repository: the download page and the documentation, both at otp.landian.vip, with the project site at officetool.plus and the author's blog at blog.yerong.org.

The practical consequence for anyone evaluating this is blunt. You cannot read the code that will install Office, activate it, or remove it, because it is not published here. What you can read is the set of strings a user sees and the contributor instructions for producing more of them. Judge the localisation work on its own terms, and treat the program's behaviour as something you verify on a test machine.

The install line pipes a remote script into iex with no pin and no checksum

There are two documented ways in, and the second one is the whole install procedure:

irm https://officetool.plus | iex

`irm` fetches whatever is at that address and `iex` executes it, in one step, with the privileges of the shell you are standing in. Nothing in that line identifies a version, verifies a signature, or leaves you a copy to inspect. Whatever the server returns at the moment you run it is what runs, which means a compromised host, a hijacked domain or an intercepted request all end in code execution on the workstation rather than in a failed download.

That matters more here than it would for a typical installer, because of what the tool then does. It creates and modifies Office installations, writes ISO images with silent installation configuration, manages KMS and product keys, and force removes Office versions back to 2003 when normal uninstall fails. A reader who pipes a moving remote script into iex is authorising all of that before seeing a line of it.

If your environment forbids that pattern, the alternative is the download page at otp.landian.vip. The repository offers no offline installer, no published hash and no pinned version reference, so the safe route is to download once, read the script, and only then run it.

The translator credits and the file list disagree in both directions

The credits table has twenty locale rows and the repository has eighteen translated READMEs plus the English original, and the two sets are not the same set. Read them against each other and three kinds of mismatch appear.

First, a code disagreement inside Arabic. The credit row is `ar-ly`, Arabic for Libya, credited to Abdul Salam Bin Ali, while the file on disk is `README-ar-sa.md`, the Saudi Arabia code. Any automation that maps a culture to its file will not match that pair.

Second, files with no credit row: `README-es-es.md`, `README-fr-fr.md`, `README-ro-ro.md` and `README-zh-cn.md` exist at the root, but the table has no Spanish, French, Romanian or Simplified Chinese row.

Third, credited locales with no file of their own: `ja-jp`, `pt-br`, `uk-ua`, `vi-vn` and `zho-yue` each have a named translator in the table and no matching README in the root listing.

The consequence is for readers, not just for the project. A translator listed as a contributor may have no delivered file in the tree, and a locale you rely on may be translated without a named owner. For localisation coverage work, diff the files against the table rather than trusting the table.

Document conversion runs through Office COM, so it needs Office sitting there

One feature line states the constraint that governs several others: fast and stable conversion of Office documents, based on Office COM. COM automation is the local Windows interface to an installed copy of Office, which means the conversion feature does not run headless and does not run without Office on the machine.

The same dependency shows up across the repair and removal features. The tool can reset settings, fix Office problems, modify an installation, switch the update channel and upgrade or downgrade without reinstalling, and force remove Office from 2003 through the latest version. Each of those is an operation against a local Office installation, and none is documented as a scripted or unattended operation.

So the consequence for an administrator is that there is no documented server-side or headless use, and the tool's repair features are themselves running inside the environment they are meant to fix. If Office on a machine is broken badly enough to break COM, the tools that rely on it may not run either. Test on the least broken machine you have, and keep a working installation image, because force removal is irreversible in a way that a normal uninstall is not.

Note also that the documented route is PowerShell and the platform behaviour described is Windows only. Nothing here describes macOS or Linux.

Activation covers three routes and documents none of their edge cases

The activation side is the widest part of the feature list, and it is also the part with the least explanation. The tool supports online activation, phone activation and KMS activation, and it supports activation management covering license management, key management and KMS management. It also lists Visio Online Plan 2 and the Project Online Desktop Client alongside the on-premises versions.

What is not written is what an administrator would need. There is no guidance on which route suits which kind of licence, nothing on what happens to an existing installation when the activation method changes, no rollback path, and no note on what state the tool leaves behind if activation fails halfway. The feature is described as existing, not as being supported.

Channel switching sits in the same category. Changing the update channel and upgrading or downgrading without reinstalling is a state-changing operation on a live installation, and the description gives no prerequisites, no schedule to do it in, and no statement about what it does to settings that are not part of Office itself. The honest reading is that these are capabilities the author uses and has documented as capabilities. If activation or channel changes are part of your rollout, validate them on a single machine first and record what you observe, because the documentation will not tell you.

Version tags name the application build, not the translation set

The recent releases are named after the application rather than after the content of this repository: v11.8.50.0 titled Office Tool Plus v11.8.50.0, released 2026-10-18, then v11.7.9.0 on 2026-09-09 and v11.6.6.0 on 2026-08-12. The version scheme is four-part, which reads like a build number rather than a semantic release.

Because the tags track the app and not the strings, a tag tells you nothing about which locales were present in it. There is no per-language release, so the only way to find out what changed in a translation is to read the diff between tags, and the only way to know a locale is current is to compare the file against the English original yourself. The last push to this repository was on 2026-10-19, which is after the v11.8.50.0 tag, so the tip and the newest release are not the same point in time.

One more asymmetry to keep straight. The MIT licence and the LICENSE and NOTICE.md files apply to what is in this repository. The README footer carries a separate copyright line for the author across 2016 to 2026, and the program you install is fetched from a different site. Do not read the repository's licence as covering the application binary.

Install coverage stops at Office 2024 while removal reaches back to 2003

The supported product list is short and specific. It covers Microsoft 365, Office 2016, 2019, 2021 and 2024, Visio 2016 through 2024 plus Visio Online Plan 2, and Project 2016 through 2024 plus the Project Online Desktop Client. Configuration can be created, imported or exported, Office can be downloaded in any language from any update channel, an installation can be modified by adding or removing components, and an ISO can be produced with both a default installation configuration and a silent installation configuration.

Two asymmetries in that list are worth noticing. Removal reaches much further back than installation: force removal is offered from Office 2003 to the latest version. And the subscription products are named unevenly, with Visio and Project given an Online variant while Microsoft 365 is listed without one, so a reader looking for a specific perpetual Office SKU or a separate OneDrive or Teams deployment has to work out from the release notes whether it is covered.

For deployment specifically, the documented syntax stops at the PowerShell line that installs the tool. The README does not give the tool's own command line for unattended or silent use, no switches for generating an ISO, and no example of feeding it a configuration file in a script. If you are automating a rollout, that gap is the work, and the documentation page at otp.landian.vip/help/ is where you would have to find it.

Community channels are broad while the documentation is one site deep

The project runs several public channels at once: a Telegram channel, a Discord community reached through a redirect on the download domain, GitHub, and a blog at blog.yerong.org. Downloads and help both point at otp.landian.vip, and the site is officetool.plus.

That surface area is useful and it is also where the limits of the published information show. The help documentation is one site, and the details that matter most for an enterprise rollout, the silent install invocation, the configuration file format, the supported switches, the activation edge cases, are not in the repository and not in the feature list. The community channels are the realistic place to get them, which means support knowledge lives in chat history rather than in a versioned document you can pin.

The documented route is a PowerShell command, and nothing in the README describes macOS. If you are evaluating for a non-Windows estate, treat that as a no rather than an open question, and if you are evaluating for Windows, budget time for the fact that the authoritative details are not versioned with the release.

Editorial conclusion

Use Office Tool Plus if you are administering Office on Windows and want one place for ISO creation, silent install configuration, channel switching and activation routing. Do not expect an audit trail from this repository: it holds translations, config and src, while the program itself is fetched from otp.landian.vip, so you are running code you have not read. Before deploying it across a fleet, read the install script rather than piping it to iex, confirm which locales you need actually have files, and test channel switching and activation changes on one machine before touching a rollout.

Frequently asked questions

Official sources

1. License: MIT
2. Project website
3. README
4. Releases
5. YerongAI/Office-Tool on GitHub