mrkeyoor.com_
Mon 07 Sept 07:10 UTC
Dev Toolsevaluationupdated 07 Sept 2026

PowerToys review

PowerToys is a Windows 10 and 11 utility suite from Microsoft that puts more than 30 small desktop tools under one settings app. It handles jobs such as arranging windows, remapping keys, launching apps, bulk-renaming files, extracting screen text, and keeping a PC awake without making users assemble a folder of separate utilities.

Verdict

Our PowerToys checkout installed its Node-based GitHub artifacts helper in 13 seconds and passed that helper's tests in 127 seconds, but we did not build the Windows suite. Windows 10 and 11 users should try the signed installer if several of its 30-plus utilities solve recurring annoyances; the app earns its place when FancyZones, Keyboard Manager, Text Extractor, and the launch tools all get used. Choose a focused alternative if one feature is the whole requirement, and expect a full Microsoft Windows toolchain before contributing to the main codebase.

We ran it

Lab card: what happened when we ran PowerToysScreenshot of PowerToys (github.com/microsoft/PowerToys)
Install✓ · 13s110 packages · 28 MB
Buildn/ano build script
Tests✓ · 127sran, no count parsed
Known vulns00 critical · 0 high · 0 moderate · 0 low (npm audit)
Repo8842 files~811,483 lines of source · 202.9 MB · 10 CI workflows

Answers from our run

Does PowerToys build from source?

Dependencies installed in 13 seconds (110 packages), and the project has no separate build step. We cloned commit 6703073 into a clean Debian container with 3 CPUs and no project-specific setup.

Do PowerToys's tests pass?

The test command failed in our container, and its output did not report a pass or fail count.

Does PowerToys have known vulnerabilities in its dependencies?

npm audit found none in the dependency tree at the time of our run.

Who should not use PowerToys?

macOS, Linux, and 32-bit Windows users: the installation guide requires Windows 10 version 2004 or newer, or Windows 11, on x64 or ARM64.

What are the alternatives to PowerToys?

AutoHotkey, Flow Launcher, GlazeWM. Our PowerToys checkout installed its Node-based GitHub artifacts helper in 13 seconds and passed that helper's tests in 127 seconds, but we did not build the Windows suite.

Setup4/5End-user installers are simple; source work needs a Windows toolchain
Docs5/5Each utility plus installation and development has detailed guidance
Community5/5138,458 stars with issue and pull request activity on September 7
Maturity5/5Thirty-plus utilities ship through signed x64 and ARM64 installers

Who it’s for

Windows power users who regularly rearrange windows, rename files, remap keys, or search for apps.
Developers and support staff who want tools such as Color Picker, File Locksmith, Hosts File Editor, and Text Extractor close at hand.
Multi-monitor users who can use FancyZones, Mouse Jump, PowerDisplay, and Window Hopper.
IT teams that want per-user or machine-wide installation plus policy control over preview updates.

Who it’s NOT for

macOS, Linux, and 32-bit Windows users: the installation guide requires Windows 10 version 2004 or newer, or Windows 11, on x64 or ARM64.
People who need only a launcher or only tiling: PowerToys carries more than 30 utilities, while Flow Launcher or GlazeWM gives that single job a smaller surface.
Contributors seeking a portable build on Debian or macOS: the developer guide requires Windows, Visual Studio 2022 or 2026, several desktop workloads, two Windows 11 SDKs, .NET 8, long-path support, and submodules.
Organizations that cannot allow diagnostic collection before a policy review: the README says PowerToys logs basic diagnostic data and points to a separate privacy document.

Setup reality

Our sandbox run at commit 6703073 installed the Node helper in tools/mcp/github-artifacts/ in 13 seconds: 110 packages occupied 28 MB. It had no build script, so build was skipped. Its tests passed in 127 seconds, and npm audit found 0 known vulnerabilities.

Those results do not prove that the Windows desktop suite runs in Debian. End users install an x64 or ARM64 package through GitHub, Microsoft Store, or WinGet. Ordinary utilities need no account. Cloud actions in Advanced Paste need provider configuration; version 0.101 also offers Phi Silica processing on supported Windows devices.

Source work is considerably heavier. The developer guide calls for Windows, Visual Studio 2026 or Visual Studio 2022 17.4 or newer, C++, WinUI and .NET desktop workloads, two Windows 11 SDKs, .NET 8, long paths, and initialized submodules. Some Explorer modules work only after building and installing the full installer.

More than 30 utilities replace a folder of one-off Windows tools

PowerToys bundles over 30 utilities behind one settings app, and the range is the point. FancyZones creates repeatable window layouts, Keyboard Manager remaps keys, PowerRename handles batch renaming, Text Extractor copies words from the screen, and File Locksmith identifies processes holding a file open. Color Picker, Image Resizer, Awake, Mouse utilities, and the Hosts File Editor cover smaller jobs that otherwise send a Windows user hunting for separate downloads.

The bundle works best when several modules earn a hotkey or context-menu slot. A developer might use PowerToys Run or Command Palette every hour, grab colors during UI work, preview unfamiliar files, and pin a reference window above an editor. Each utility can be enabled according to need, so the 30-plus list does not have to become 30 resident habits. If only one function matters, a focused project is easier to understand and replace.

Windows 10 build 19041 is the minimum, and 32-bit PCs are excluded

Microsoft's installation guide requires Windows 11 or Windows 10 version 2004, build 19041, on an x64 or ARM64 processor. Setup installs the current stable Edge WebView2 Runtime when needed. GitHub offers per-user and machine-wide executables, while Microsoft Store and WinGet cover managed or repeatable installation. That is a friendly path for users; there is no supported macOS or Linux edition in the project documentation.

Most tools work without credentials or a server. Advanced Paste is the exception worth checking before adoption because its AI actions can involve OpenAI or Azure OpenAI configuration. Release 0.101 added on-device Phi Silica transformations for supported Windows hardware, with a model download initiated from settings. Teams can hide the AI paste area when unused. The README also says the application records basic diagnostic data, so privacy-sensitive organizations should review Microsoft's linked collection policy before rollout.

What happened when we ran it

Our sandbox cloned commit 6703073 and found the runnable Node project under tools/mcp/github-artifacts/. Its npm install completed in 13 seconds, adding 110 packages and 28 MB on disk. There was no build script or target, so we skipped that step rather than treating it as a failure. The available tests passed in 127 seconds, and npm audit reported 0 known vulnerabilities across critical, high, moderate, and low severities.

The result covers a repository helper, not the PowerToys desktop binaries. Our fresh unprivileged container had 3 CPUs, 8 GB of RAM, no secrets, and the lab-node:22 image. The checkout itself contained 8,842 files, about 811,483 source lines, and 202.9 MB. We counted 10 CI workflow files, no Dockerfile, and no tests directory. A successful helper test cannot substitute for compiling or exercising the Windows UI, Explorer hooks, installer, or elevated behavior.

A 202.9 MB checkout requires a full Windows development machine

The developer path is much more demanding than installing the app. Microsoft's guide recommends Visual Studio 2026, or Visual Studio 2022 version 17.4 or newer, with Desktop Development with C++, WinUI application development, and .NET desktop development. It also names two Windows 11 SDK versions, .NET 8, long-path support, Developer Mode, and Git submodules. The setup PowerShell script can prepare much of that environment, and some steps require administrator rights.

Building PowerToys.slnx produces binaries that can run from the output folder, but several Explorer-integrated modules remain unavailable until the installer is built and installed. The installer itself spans an EXE bootstrapper and MSI, and its documented build is Release-only. For a first contribution, the issue-first workflow and module-specific developer pages are useful. For a quick Linux patch, this 811,483-line Windows codebase is a poor candidate.

Version 0.101 adds Window Hopper, compact search, and local AI paste

Release v0.101.2362.0 was published on August 25, 2026. Window Hopper cycles among windows belonging to the current application. Command Palette gained a compact mode, PowerDisplay added linked monitor controls and a command-line interface, and Shortcut Guide added Windows-key activation plus search. ZoomIt gained DemoMirror and more recording controls. These are practical additions, though the release note also warned that an update-rollout issue could delay delivery to some users.

The same release shows the maintenance cost of a broad desktop suite. Quick Accent and Mouse Jump continued their WinUI 3 moves, while fixes touched FancyZones, Keyboard Manager, Peek, PowerToys Run, File Explorer add-ons, Image Resizer, and Mouse Without Borders. A user can leave unwanted modules disabled. An IT owner still needs to test the enabled set, global shortcuts, shell integration, updates, and policy behavior against the organization's Windows image.

September 7 activity outweighs the queue of 7,667 issues and PRs

GitHub reported 138,458 stars and 7,667 open issues and pull requests when fetched. That combined queue is huge and should never be presented as 7,667 bugs. Activity is equally plain: the repository was pushed on September 7, 2026, and new issue 50430 plus pull request 50433 arrived that day. The latest stable release had landed 13 days earlier. This is an actively maintained project with a large support surface, not a quiet utility with a tidy backlog.

PowerToys is easiest to recommend as a signed Windows download, then judged module by module. Start with two or three recurring problems, disable the rest, and check for shortcut conflicts during a normal workday. AutoHotkey is better for scripted automation, Flow Launcher for a dedicated launcher, and GlazeWM for automatic tiling. Compiling the suite is a separate commitment that needs the Windows toolchain described above, regardless of how cleanly its small Node helper ran in our container.

Alternatives

ProjectWhat it isPick it when
AutoHotkeyA Windows scripting language for custom hotkeys, macros, and desktop automation.pick this instead when you want to script a precise workflow rather than enable a fixed catalog of utilities.
Flow LauncherA focused Windows launcher with file search and community plugins.pick this instead when launching, searching, and plugins are the main job and the rest of PowerToys would sit disabled.
GlazeWMA configurable tiling window manager for Windows and macOS inspired by i3.pick this instead when automatic tiling and a text configuration matter more than PowerToys' broader desktop toolbox.

What people are saying

  1. [velocity-scout] microsoft/PowerToys

Sources

  1. PowerToys README
  2. PowerToys installation requirements
  3. PowerToys developer documentation
  4. PowerToys v0.101.2362.0 release notes
  5. PowerToys issues and pull requests

More dev tools reviews

tldraw · spacemacs · tabler-icons · darwin-vm · Seelen-UI · sofka · the whole board →