# Lenovo Legion Toolkit: the Vantage replacement that outlived its upstream > A Windows-only hardware control suite carried forward by a volunteer team after the original repository was archived, shipping three update channels and talking straight to laptop firmware. **LenovoLegionToolkit-Team/LenovoLegionToolkit** — Lenovo Legion Toolkit (LLT) is a Windows desktop utility created for Lenovo gaming laptops that replaces Lenovo Vantage, Legion Zone, and Legion Space. - Repository: https://github.com/LenovoLegionToolkit-Team/LenovoLegionToolkit - Website: https://discord.gg/TB3ER8ZVdt - Stars: 2,395 · Forks: 91 - Language: C# - License: GPL-3.0 - Published: 2026-10-07 · Updated: 2026-10-07 · Language: en - Canonical page: https://hysenlabs.com/projects/lenovolegiontoolkit-team-lenovolegiontoolkit ## Where this repository came from The first thing in the README is a status notice, placed above even the logo, and it carries the three facts that matter most about this project. It is actively developed by the LenovoLegionToolkit-Team. The original source repository, BartoszCichecki/LenovoLegionToolkit, is archived. And the project is not officially affiliated with Lenovo. That last line is the one people skim past. Lenovo ships Vantage and Legion Zone themselves, and this tool replaces all three of Lenovo's own utilities, which puts it squarely in territory where trademark language matters. The team states the separation plainly rather than leaving you to infer it. The lineage explains more than the branding does. An archived original usually means the maintainer stopped, the hardware moved on, and the accumulated reverse engineering work sits rotting in a read-only tab. A fork that keeps going is the outcome you want precisely because the work is hard to recreate. Anyone who remembers the original repository as the place to look will land on a frozen copy, and anyone who searches now finds the team that inherited it. The rest of the metadata is unremarkable in the good way. C# and WPF on the front end, GPL-3.0, Windows 10 and Windows 11, x64, targeting .NET 9.0. At 2,179 stars and 82 forks with 22 issues open, it is a project with steady interest and a small enough surface that issues get looked at. The last push to the default branch, master, was on 2026-09-28, which is recent enough that the project is plainly in motion. There is no corporate team behind this. It is volunteers, and the repository says so. ## The pitch is fewer resident pieces on a hot laptop The whole argument for the tool fits in one paragraph. It is a Windows desktop utility created for Lenovo gaming laptops that replaces Lenovo Vantage, Legion Zone and Legion Space. It runs no background services, uses less memory, uses virtually no CPU, and contains no telemetry. Just like Lenovo Vantage, this application is Windows only. Four claims, each specific enough to be falsifiable, which is more than most utility README files offer. The no-telemetry line matters more than it looks. Vantage is the kind of program that reports usage back to its vendor, and some users object to that on principle rather than on principle about resource use. The absence of a resident service is the load-bearing claim, because a service is what actually keeps a vendor utility's background work alive after you close its window. There is a small tension inside the README that is worth naming. It advertises no background services, then tells you that the toolkit works best when it is running in the background. Go to Settings and enable Autorun and Minimize on close. The next thing is to either disable Vantage and Hotkeys or just uninstall them. So the intended steady state is a tray-resident WPF application, not a service. That is a materially different architecture from what it replaces, and it explains why the resource comparison is plausible rather than marketing. It also means the tool has to be allowed to run at login to do its job, which is the part some people object to. The README is upfront about it rather than burying it. ## Three update channels and a self-verifying installer The updating story is unusually well specified for a community Windows utility. The application can update itself automatically or be updated by hand. In the app, under Settings then Updates, you pick a channel of Stable, Beta or Dev releases and a check frequency, with Daily, Weekly and Hourly offered as intervals. Automatic updates are cryptographically verified with Authenticode signatures before installation, which is the detail that decides whether you let a background process fetch and run binaries. That claim is not just prose here, because the repository tree contains the machinery to make it true: `LenovoLegionToolkit.cer` sits at the root next to the solution file, and there are three PowerShell scripts whose names describe the signing chain exactly, `generate_certificate.ps1`, `sign_installer.ps1` and `build_identity_package.ps1`. Two Inno Setup scripts, `make_installer.iss` and `make_installer_action.iss`, plus an `InnoDependencies` directory, cover packaging. The Dev channel is not a stale label. The newest tagged build, v2.36.2.12 from 2026-09-28, is described as an automated development build compiled from the `dev` branch, and its contents are pure bugfix work. The stable line sits at v2.36.0.0 from 2026-09-08, and the README badges track a separate workflow for each branch, `build.yml` on master and `dev-release.yml` on dev. Two branches, two pipelines, two channels is a release process with real machinery behind it. The upgrade story is also explicit about what survives. Installing over an existing version preserves all settings, custom modes, actions and macros, so you never need to uninstall a previous version first. That claim has one important exception, and it is the subject of the next section. ## The one upgrade the maintainers asked you to handle yourself Every release page here opens with a request for donations, which is normal. The v2.34.0.0 release from 2026-06-02 opens with something else: a block headed Critical Upgrade Instructions, read before installing. The reason is architectural. Due to the extensive architectural overhauls in how power modes, plan overrides and plugin caches are handled, the note says legacy configuration files are highly likely to conflict with the new system. To avoid erratic behavior, power state desyncs, or the side effects of unbalanced configurations, you are told to follow one of two paths when upgrading. The published note lays out both options with their consequences rather than leaving the choice to guesswork. Read that against the in-place upgrade feature and you get the clearest picture of how this project is run. The updater promises to carry your settings across an upgrade, and generally it does. But when the meaning of a stored setting changes underneath it, carrying the file forward is exactly the wrong thing, so the maintainers say so and ask for a manual decision instead. Power state desyncs are the scary phrase in that note, and it is the kind of failure a laptop user notices immediately: fans at the wrong curve, a performance mode that reports one thing and does another. The practical consequence is small but real. If the updater is going to fetch a version that crosses this kind of boundary, read the release page first rather than accepting the prompt. The habit worth forming here is that this repository's release notes are unusually worth reading, because they name specific failure modes rather than listing features. ## Nine projects in one solution The tree tells you more about the scope than any feature list would. The solution file `LenovoLegionToolkit.sln` holds nine projects, and their names describe a real separation of concerns rather than a single growing application. `LenovoLegionToolkit.WPF` is the desktop application, matching the Windows-only, WPF, .NET 9.0 badges. `LenovoLegionToolkit.CLI` and `LenovoLegionToolkit.CLI.Lib` are a command line front end with its own library, which means the hardware calls are reachable without launching a window. `LenovoLegionToolkit.Lib` is the shared core. Three sibling projects take single features seriously: `LenovoLegionToolkit.Lib.Automation`, `LenovoLegionToolkit.Lib.Macro`, and `LenovoLegionToolkit.LampArray`, the last of which corresponds to the per-key lighting controls that show up in the README's keyboard screenshots. The remaining two are the interesting ones. `LenovoLegionToolkit.Probe` and `LenovoLegionToolkit.SpectrumTester` are not application features. They are instruments, which is what you build when the underlying problem is reading hardware state that no vendor documented. The v2.36.0.0 stable notes describe the effort behind recent work as hundreds of hours of reverse engineering, kernel and hardware investigation, refactoring and community-driven polishing, and a separate project for spectrum testing is consistent with that description. Build plumbing is centralized rather than scattered. `Directory.Build.props` and `Directory.Build.targets` handle shared configuration across all nine projects, which is the convention you want in a solution this size. Batch files named `clean.bat`, `make.bat` and `make_action.bat` cover the local loop. One thing this tree does not give you is a build recipe. The README carries no command examples to copy, no code fence, no dotnet invocation. For a project aimed at end users rather than developers that is defensible, and the Windows binary is the intended artifact. If you want to build from source, the solution file and the directory-level props files are where you start, and the README's own table of contents points to an Arguments section for the command line surface. ## What the dev channel's fix list exposes The v2.36.2.12 development build is worth reading in full, because a bugfix list is an honest map of where a hardware utility is fragile. Five entries, and every one of them sits in the layer between the hardware and the interface rather than in the hardware writes themselves. A sensor toggle was clearing dashboard and OSD settings and leaving a stale on-screen display or tray tooltip behind when re-enabled. A dGPU awake device was being created on the wrong adapter and not recovering after a GPU power cycle. Minimize to tray was not working when combined with Minimize on Close, the maximized state was lost on restore, process priority got stuck at idle, and AMD title bar buttons rendered incorrectly. A single service-disabled exception could crash the whole execution flow. And fan speed did not display until the OSD had started at least once. Two things follow. First, the ordering dependencies between subsystems are the hard part. Fan speed not appearing until something else starts is a state-machine bug, not a sensor bug. Second, the GPU power-cycle case shows the tool is dealing with hardware that changes state underneath it, which is precisely why the project needs a probe tool and why per-model behavior is never fully settled. The stable release that preceded it shows the other direction of travel. v2.36.0.0 added native support for Windows 11 Dynamic Refresh Rate directly in the refresh rate selector, along with Auto Color Management toggling and modernized Win32 HDR state handling. That is an application tracking operating system display features, and it means which features you get depends partly on your Windows build, not just on your Legion model. Worth checking the release page for your Windows version before assuming a display control is missing because the laptop cannot do it. ## Localization, the disclaimer, and where support actually happens Localization is organized rather than incidental. The fork has linked to the Crowdin project LenovoLegionToolkit, and the root holds a `crowdin.yml` configuration file. Translated READMEs ship in the repository for Japanese, Russian and Simplified Chinese, alongside a Russian README and a Chinese one, and the contributing guides are translated too, with Japanese, Korean and Chinese variants of `CONTRIBUTING.md`. The word unofficial in the Crowdin project slug is a leftover of the fork's history and does not describe the current maintenance situation. The disclaimer is short and unforgiving: the tool comes with no warranty, use at your own risk. It is followed by a request to be patient and read the README carefully because it contains important information. For software that sends firmware commands to a laptop you may depend on for work, that is the correct posture and it also tells you something about the project's maturity that the release cadence alone would not. Support does not run through the issue tracker. Three Discord servers are listed, one official for releases, support and discussions, and two community servers for Legion Series and LOQ Series. The repository metadata reflects that: the project's homepage field is a Discord invite rather than a website. There is no documentation site, which means search results for this tool tend to surface Discord and forum threads rather than a maintained manual. The README's own table of contents points to a FAQ, an Arguments section, and instructions for collecting logs, and a `docs` directory sits at the root. Those are the places to look first when something misbehaves. What none of it settles is the per-model hardware matrix, which is why the community servers carry so much of the practical weight. The README also routes Linux users elsewhere, pointing at LenovoLegionLinux as the project to look at if what you want is a Vantage alternative that is not Windows-only. ## Conclusion What makes this repository interesting is not that it can set a fan curve or a power limit, since other tools can do that too. It is that a small team picked up an archived codebase, kept shipping stable builds roughly every few months, kept a dev channel for people who want the newest bug fixes, and signed its own installers. The claims in its README are specific and checkable: no background services, no telemetry, Windows only, replaces Vantage, Legion Zone and Legion Space. The unresolved parts are equally specific. Hardware behavior still varies across Legion generations, the README promises no warranty at all, and support happens on Discord rather than on an issue tracker that a search engine can index. If you install it, take the stable channel, read the release page for the version you are crossing rather than letting the updater do it for you, keep Autorun and Minimize on close enabled, and remove Vantage rather than running both. Everything else the tool does, it does because somebody spent time reading firmware responses that nobody documented for them. ## FAQ ### What is Legion Toolkit? Lenovo Legion Toolkit is a free Windows-only desktop utility for Lenovo Legion gaming laptops that replaces Lenovo Vantage, Legion Zone and Legion Space. It is written in C# with a WPF interface, licensed GPL-3.0, and is maintained by the LenovoLegionToolkit-Team after the original repository was archived. ### Is Legion Toolkit safe? It is an unsigned-by-Lenovo community tool, and the project states plainly that it comes with no warranty and is used at your own risk. It does verify its own automatic updates with Authenticode signatures before installing, ships open source under GPL-3.0, and is not officially affiliated with Lenovo. ### Does Lenovo Legion Toolkit run in the background? It runs no background services, but the app itself is meant to stay resident. The README recommends enabling Autorun and Minimize on close under Settings, then disabling or uninstalling Vantage and Hotkeys so only one utility is controlling the hardware. ### How do I update Lenovo Legion Toolkit? Under Settings then Updates you can pick the Stable, Beta or Dev channel and how often it checks. Upgrades install in place and preserve settings, custom modes, actions and macros, and downloaded updates are checked against Authenticode signatures before they run. ### Which version of Lenovo Legion Toolkit should I install? Take the latest Stable build unless you specifically want unreleased fixes. The current line is v2.36.0.0 from 2026-09-08, with v2.36.2.12 as the Dev build from 2026-09-28, and releases are published on the repository's releases page. ### What do I do before upgrading from an older Lenovo Legion Toolkit? Read the release page for the version you are crossing. The v2.34.0.0 notes flag that legacy config files are highly likely to conflict after power modes, plan overrides and plugin caches were reworked, and offer two paths to avoid power state desyncs. ## Sources - [LenovoLegionToolkit-Team/LenovoLegionToolkit on GitHub](https://github.com/LenovoLegionToolkit-Team/LenovoLegionToolkit) - [License: GPL-3.0](https://github.com/LenovoLegionToolkit-Team/LenovoLegionToolkit/blob/master/LICENSE) - [Project website](https://discord.gg/TB3ER8ZVdt) - [README](https://github.com/LenovoLegionToolkit-Team/LenovoLegionToolkit/blob/master/README.md) - [Releases](https://github.com/LenovoLegionToolkit-Team/LenovoLegionToolkit/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/lenovolegiontoolkit-team-lenovolegiontoolkit