Microsoft shipped PowerToys version 0.100.0 on June 10, 2026, releasing a long-awaited feature that turns the Command Palette launcher into a platform. The Extension Gallery, now built into the launcher, lets anyone browse a Microsoft-curated feed of add-ons and install them with a click. It’s a clear win for users who want to extend the tool’s capabilities without hunting down packages manually. For IT administrators, though, the update lands with a thud: there is no built-in way to control which extensions employees can install, and the existing fleet-management policies for PowerToys don’t touch the new gallery.
A Launcher Transformed into an App Platform
The Command Palette in PowerToys started as a keyboard-driven productivity launcher, but version 0.100.0 fundamentally changes its role. The new Extension Gallery, accessible directly from the launcher’s interface, presents a curated list of extensions that can add commands, pages, forms, and even custom workflows. Installation happens through WinGet, Microsoft’s package manager, meaning the process is quick and consistent.
Behind the scenes, each extension is a standalone .NET application that runs in its own process and communicates with Command Palette via a WinRT API, according to Microsoft’s extensibility documentation. They register with Windows through an app manifest declaring a specific extension point (com.microsoft.commandpalette). When you install an extension through the gallery, you are actually adding a Winget package that, upon installation, registers its presence with the operating system. The next time Command Palette launches, it scans the Windows Package Catalog for apps that declare that extension point, loads the extension’s COM server, and connects to it automatically.
This architecture isolates extensions from each other and from the core PowerToys process, which Microsoft argues improves security and stability. It also means each extension is functionally a separate piece of software—with its own update lifecycle, dependencies, and potential access to system resources. Extensions can provide several types of content: top-level commands on the home page, fallback commands that trigger when no other results match a query, context menu items, and dedicated pages. Supported page types include lists, detail views, interactive forms, markdown, and grid galleries, making the launcher capable of hosting fairly complex mini-apps.
In addition to the gallery, the release adds multi-monitor Dock support, letting users pin a quick-launch bar to the edges of any display. But the gallery is the star: it turns Command Palette from a tool you configure into a hub you stock with capabilities chosen from a feed that Microsoft says is reviewed for quality and safety.
For Users: Productivity, but Read the Fine Print
If you’re an everyday Windows user who relies on PowerToys to zip around your workflow, the gallery is a gift. You can now install extensions that add a dictionary lookup, a system-monitoring command, a quick-launcher for internal tools, or a GitHub search—all without leaving the launcher. Microsoft’s curated feed should, in theory, weed out malicious or poorly coded packages, and the separate-process model means an unstable extension is unlikely to crash the whole utility.
But “curated” does not mean “approved for your environment.” The review process ensures a baseline standard, but it doesn’t verify that an extension aligns with your company’s compliance policies or doesn’t introduce a dependency that conflicts with other software. Power users and developers will likely dive in first; they’re also the ones most likely to hit edge cases. If you plan to install an extension, look for signs of active maintenance—check the publisher’s release notes on GitHub, confirm it doesn’t request unreasonable permissions (though the permission model is fairly limited to what Command Palette offers), and understand that you’re adding a piece of software that could be abandoned or altered in future updates.
Because the gallery is fed by the Windows Package Catalog, anyone who can publish a Winget package could, in principle, create an extension. The curation applies to the gallery feed itself, but the underlying platform is open. Early adopters on Reddit are already sharing their favorite extensions, but a personal endorsement is no substitute for a thoughtful review. Treat extensions like any downloaded utility: useful but not entirely risk-free.
For IT: A Governance Challenge Dressed as a Productivity Win
For enterprise administrators, the gallery is a mixed blessing. On one hand, it reduces the number of “shadow IT” scripts and unsanctioned launcher hacks that users cobble together on their own. On the other, it opens a straightforward path for anyone to install arbitrary code—packaged as a .NET app—that integrates deeply with the desktop experience. Every installed extension becomes a new application to track, update, and support.
PowerToys has supported ADMX-backed policy management since version 0.64, which lets administrators control which utilities are enabled and how they behave across the fleet. But the published policy controls do not include any mechanism for managing extensions. There is no allowlist, no blocklist, no way to pre-approve specific extensions, and no centralized configuration for extension settings. In the current release, an employee can open the gallery, pick any extension, and install it—and the IT department won’t necessarily know unless they monitor WinGet events or application inventories closely.
According to WindowsForum’s analysis, the appropriate first step is not a company-wide deployment but a tightly controlled pilot. Treat the gallery as a new application-acquisition path, not a cosmetic update. Even though extensions run in separate processes, they should be reviewed individually because they can access local files, network resources, or sensitive data depending on what they’re built to do. Packaging them as Winget apps doesn’t exempt them from your standard software onboarding checklist: confirm the publisher’s identity, the stated purpose, support responsibility, and data-access implications.
The Road to 0.100.0: Building an Extensible Command Palette
PowerToys underwent a major architectural shift in 2022 when Microsoft split the old Run launcher into a new Command Palette. Early versions (0.90.1, 0.93, 0.97) focused on performance and usability, making the launcher faster and more responsive. WindowsForum’s previous reviews documented incremental improvements that attracted a growing user base. The extension API, introduced publicly in preview form last fall, hinted at the coming gallery. With 0.100.0, that API matures into a fully integrated experience.
The move mirrors broader trends in Windows development: Microsoft has been pushing package-based distribution through WinGet, encouraging developers to modernize their apps with MSIX packaging, and exploring extensibility models that work across the desktop. The Command Palette extension model, built on .NET and COM, is a more enterprise-friendly foundation than the loose scripts sometimes used in other launchers. But that doesn’t automatically solve governance, and Microsoft hasn’t yet shipped the administrative tooling that would make large-scale management practical.
How to Run a Safe Pilot — Starting Now
If your organization wants to explore the productivity gains without accepting uncontrolled risk, start with a hand-picked group of technically competent users whose work involves heavy keyboard navigation, automation, or developer tooling. Here’s a practical framework, adapted from operational guidance collected by WindowsForum:
- Deploy PowerToys 0.100.0 to the pilot group and verify that Command Palette appears and is functional.
- Open the Extension Gallery and have users browse the available feed. Ask them to submit extension requests with a rationale, rather than installing directly.
- Review each requested extension for business need, publisher reputation, data exposure, and support requirements. Record approvals in a register separate from PowerToys configuration.
- Allow installation only of reviewed extensions, and use your existing endpoint management tools to monitor those installations. Since the gallery uses WinGet, you may also need to adjust WinGet access policies on managed devices.
- Document rollback procedures for each approved extension, including how to remove it and what alternative workflows exist.
- Expand the pilot only when you have a repeatable process for approval, update monitoring, and removal. That process is the true governance layer; the gallery merely provides the catalog.
Crucially, this approach avoids the most common trap: assuming that because PowerToys is “Microsoft-curated,” it’s safe to turn everyone loose. The curation helps filter out clearly malicious packages, but it does not account for organizational specifics. A glowing user review in the gallery does not equal a security sign-off.
What to Watch: Will Microsoft Bridge the Governance Gap?
The extension gallery is still young, and Microsoft has a track record of adding enterprise controls to popular tools after initial release. Administrators should watch for upcoming PowerToys updates that might introduce extension allowlisting, deployment profiles, or integration with Microsoft Intune for per-extension configuration. Even a basic policy switch to disable the gallery entirely would give IT teams breathing room.
In the meantime, the gallery is a functional, well-integrated feature that will almost certainly increase PowerToys’ adoption and utility. The coming months will test whether organizations can harness it safely or whether it becomes another unmanaged software channel. For now, the advice stays simple: explore it, pilot it, but don’t let it run without a leash.