Microsoft has released PowerToys 0.100, a milestone update that introduces an entirely new Shortcut Guide utility, a significantly enhanced Command Palette with an Extension Gallery and multi-monitor Dock support, and a raft of under-the-hood improvements including a migration to .NET 10. Yet for all the new firepower, the release sidelines two UX refinements the community has been clamoring for: a search box inside PowerToys Settings and a quit confirmation flyout to stop accidental shutdowns.

What’s new in PowerToys 0.100

The latest version, available now on GitHub and via the Microsoft Store, packs several headline features that push the suite closer to a polished productivity platform.

New Shortcut Guide: contextual help that reads your current app

The brand-new Shortcut Guide appears as a side pane when you press the activation hotkey and automatically detects the active application, displaying only the keyboard shortcuts relevant to what you’re doing. Unlike the legacy guide that simply overlaid a static Windows key shortcuts diagram, this one is context-aware. It detects the foreground app—Word, Excel, Visual Studio Code, or any of the supported applications—and surfaces app-specific shortcuts alongside Windows system shortcuts and shortcuts from enabled PowerToys utilities.

Community contributor @noraa-junker drove the implementation (tracked in issue #40834), and the feature’s documentation already lists a growing array of supported apps. If your favorite app isn’t on the list, the team welcomes pull requests or issues with a link to the app’s shortcut documentation. The underlying design uses Fluent styling and feels native to Windows 11.

Command Palette, the spiritual successor to PowerToys Run, was rebuilt with extensibility at its core. Now it gains an Extension Gallery accessible directly from the Palette’s Settings screen. Users can browse, install, update, and remove extensions without leaving the interface—no more hunting GitHub repositories or WinGet commands. The gallery lists extensions that are curated or verified, though developers can also submit third-party extensions to the Microsoft Store or WinGet for discovery.

Complementing the gallery, the Dock feature now supports multi-monitor setups. Each monitor can host its own independent Dock, configurable with different sets of pinned commands. Improved pinning logic lets you choose exactly where a command lands. Meanwhile, the built-in Performance Monitor extension gains a Battery widget showing charge level, charging status, and estimated time remaining; individual metrics (CPU, Memory, GPU, Network, Battery) can now be pinned directly to the Dock.

Dozens of smaller fixes accompany these headliners: better search result ranking, accessibility polish, asynchronous loading to keep the UI responsive, and a mountain of extension platform updates. Much of the credit goes to @jiripolasek, who has become the project’s Command Palette lead.

PowerDisplay gets a stability injection

The PowerDisplay module, which lets you adjust monitor brightness, contrast, and color profiles via DDC/CI, receives a major reliability upgrade. Startup times on many systems are now noticeably faster; monitor identification across reboots is more consistent; and settings are preserved more reliably when hardware configurations change. A new Max Compatibility Mode opens the door for displays that don’t properly advertise DDC capabilities. Usability tweaks include dismissing the flyout with Escape, adjusting sliders with the mouse wheel, and an automatic rescan when the PC wakes from sleep.

ZoomIt gains webcam recording; under-the-hood revamp

ZoomIt, the screen zoom and annotation tool, now supports a webcam overlay while recording, making it a more capable demo and tutorial companion. You can also append multiple clips with transitions, stitching together recordings without leaving the tool.

PowerToys itself has undergone a foundation upgrade. The entire codebase has migrated to .NET 10, bringing performance and tooling improvements while shrinking the installer size by 15%. Auto-update reliability has been bolstered: the app now relaunches properly after an update, shows clearer success notifications, and automatically backs up configuration files beforehand so settings can be restored if corruption is detected.

Other UI components continue their modernization. Quick Accent and Workspaces have shed custom WPF theming libraries in favor of native Fluent-inspired WPF styling. Workspaces, in particular, got a visual refresh with updated typography, spacing, and layout.

The long wait for two sorely needed UX fixes

While version 0.100 delivers feature richness, it conspicuously omits two enhancements that PowerToys power users have been requesting—and in some cases actively developing—for months.

Settings search remains absent

PowerToys’ Settings app has ballooned as new modules joined the suite. Toggling an option often requires scrolling through sidebar entries and nested groups. A search box was a perennial community ask, tracked across multiple GitHub issues that were triaged, closed, or consolidated as duplicates. The idea was straightforward: type a keyword and jump directly to the relevant toggle. Some contributors even pushed for inline toggle controls inside search results, letting you enable or disable a setting without leaving the search pane—a convenience even Windows Settings itself doesn’t offer.

That work was initially targeted for v0.94, the release that community discussions referenced before the jump to 0.100. The official 0.100 release notes, however, make no mention of a Settings search bar, and the installation experience remains unchanged. While the feature is still visible in GitHub milestones and active discussions, its public debut has slipped past the latest milestone.

No confirmation flyout for the Quit button

Equally persistent is the problem of accidental exits. The Shutdown/Quit button sits in the Settings title bar, perilously close to minimize. A stray click can terminate the entire suite, killing background utilities like FancyZones, Keyboard Manager remaps, or Clipboard History. Users have complained about lost hotkeys and disrupted workflows, particularly those who rely on PowerToys to just work in the background.

The planned fix—a confirmation flyout with distinct “Quit (exit completely)” and “Hide (minimize to system tray)” options—was fleshed out in design threads, complete with tooltip text discussions and careful consideration of the “Quit” label versus “Close.” But the 0.100 release doesn’t include it. The quit control still offers no guardrails, and the only mitigation remains the system tray “Exit” menu item or the “Run at startup” toggle.

Why these omissions matter

PowerToys’ success depends on being unintrusive yet immediately available. A settings search isn’t just a nice-to-have; it reduces cognitive load as the utility count grows, and it lowers the bar for new users who might otherwise abandon the suite after failing to find a toggle. Inline toggles in search results would set a new standard for Windows utility configuration.

Accidental quits, meanwhile, are a paper cut that bleeds productivity. When a user’s carefully configured keyboard remaps or always-on clipboard history vanishes because of a misplaced click, frustration follows. A confirmation dialog is a trivial engineering task that would eliminate an entire class of support complaints.

The fact that both fixes have lingered through multiple release cycles suggests a prioritization challenge. The team has chosen to invest in marquee features like the Shortcut Guide and Command Palette extensibility before addressing these housekeeping items. That’s a defensible trade-off—new, attention-grabbing features can attract more users and contributors—but it leaves the core daily experience less polished than it could be.

Practical advice for users and admins

Until a Settings search and quit flyout materialize, several workarounds can smooth the rough edges.

  • Avoid the title-bar quit button: Always use the system tray icon’s “Exit” menu if you intentionally need to close PowerToys. This reduces the risk of accidental clicks.
  • Enable “Run at startup”: If you rely on background tools, turn this on in Settings. Should PowerToys exit unexpectedly, it will restart automatically on the next logon.
  • Back up your settings: The suite already backs up configurations before updates, but you can manually export your settings via the UI. Keep a copy safe, especially before upgrading to a new major version.
  • Test updates first: Administrators should validate 0.100 in a non-production environment. Pay particular attention to modules that hook into input (Keyboard Manager), shell extensions (File Explorer add-ons), and overlay UI (Text Extractor). Use Group Policy or deployment tools to control which modules are enabled.
  • Monitor GitHub for progress: Both the settings search and quit flyout remain in open issues and pull requests. Watching the repository will give you the earliest signal when they land.

The bigger picture: a suite on a dual track

PowerToys development operates on two parallel tracks. One track delivers flashy, public-facing utilities that generate buzz and draw new users—the Shortcut Guide and Command Palette extensions are perfect examples. The other track consists of deep infra work, accessibility fixes, and performance optimizations. The 0.100 release excels on both: .NET 10 migration, reduced installer size, and auto-update reliability are infra wins; the new utilities are the buzz.

But the third track—continuous UX refinement of existing modules—sometimes falls behind. Settings search and quit confirmation are not complex features. Their absence after a round-number release like 0.100 highlights a tension between building new things and perfecting old ones. Microsoft’s open approach allows anyone to see the plans, but it also means users can grow impatient when commits don’t translate into releases.

The good news is that the project maintains a healthy contribution pipeline. The settings search issue has gone through triage, consolidation, and design; the quit flyout has been discussed at length with maintainer involvement. These aren’t abandoned ideas. They’re likely to surface in a subsequent 0.101 or 0.102 release, perhaps as a highlight of the next minor version.

Final thoughts

PowerToys 0.100 is a substantial update that reinforces the suite’s role as a must-have for Windows enthusiasts. The new Shortcut Guide alone justifies the download, and the Command Palette’s extension gallery will spawn a new ecosystem of plugins. Yet the release also serves as a reminder that even the most beloved open-source projects must juggle priorities. The UX fixes users have been craving—the ones that make daily interaction frictionless—are still in the pipeline. They’re the kind of polish that separates a useful toolkit from an indispensable productivity partner. When they finally arrive, PowerToys will feel complete in a way it hasn’t yet. For now, update to 0.100 for the new features, keep an eye on the GitHub releases, and maybe contribute a comment or a thumbs-up to the UX issues that matter most to you.