Microsoft has rolled out PowerToys version 0.93, a significant update that overhauls the Settings dashboard with a Windows 11-style card layout and supercharges the Command Palette with ahead-of-time compilation to slash startup times and memory usage. Yet the release also sharpens a long-standing pain point: there is still no built-in search box to quickly locate any of the dozens of module toggles and nested options scattered across the PowerToys interface. The community has been vocal about this missing feature, and Microsoft’s roadmap now explicitly targets settings search improvements for the next milestone, v0.94, promising to transform how power users configure their toolkit.

What’s new in PowerToys v0.93

The v0.93 update zeroes in on two pillars: a friendlier onboarding experience and raw performance engineering. The old, plain-text module list has been replaced by a card-based dashboard that mimics the look and feel of Windows 11’s Settings app. Each utility—from FancyZones to Color Picker—now appears as a tile, complete with toggle switches, shortcut summaries, and quick-action buttons. This change directly addresses the frequent complaint that the previous UI was hard to scan and slow to navigate.

Under the hood, the Command Palette (the successor to PowerToys Run) received aggressive optimizations. By adopting ahead-of-time (AOT) compilation and other runtime streamlining, the team reports a roughly 55% reduction in the extension’s install size, an approximate 15% drop in startup memory consumption, and load-time improvements of around 40% in their internal benchmarks. Users on a variety of hardware should feel the snappier response immediately. The update also bundles dozens of smaller fixes: improved accessibility labeling, better high-contrast support, and an expanded suite of automated UI tests that signal a maturing commitment to stability over rapid prototyping.

These gains are real and welcome, but the redesign inadvertently highlights a usability gap. The more modular PowerToys becomes, the more you need to hunt for specific settings. Turning on a particular FancyZones tweak, finding a Keyboard Manager shortcut, or locating a Command Palette extension option often means scrolling through a long tree of nested pages. That hunt costs time and adds friction, especially for administrators and power users who manage configurations across many machines.

The search box that isn’t there—yet

The absence of a settings search has been a recurring topic on GitHub and in community forums. Issue threads and feature requests repeatedly ask why PowerToys, with its expanding catalog of utilities, doesn’t offer a simple, omnipresent text field where you can type “color picker hotkey” and jump straight to the relevant page. Windows 11’s own Settings app demonstrates the power of a unified search that understands natural phrasing and deep-links to the exact toggle; PowerToys users have wanted that same convenience for years.

Microsoft’s PowerToys engineering team has been listening. In the official blog post announcing v0.93, they explicitly mention that “improvements for searching your Settings” are on the roadmap for the v0.94 milestone. Multiple GitHub issues, including one with the community label “In for 0.94”, track the design and implementation of a search bar. While no single, merged pull request has been conclusively tied to a production-ready feature as of this writing, the combination of the roadmap note and active development threads makes it clear this is not wishful thinking—it’s a planned, high-priority item.

What a PowerToys Settings search could look like

Based on GitHub discussions and community proposals, the likely implementation will blend several practical elements:

  • A persistent search box on the Settings dashboard that filters modules, pages, and brief descriptions as you type.
  • Results that include module cards, specific setting controls, and quick actions (e.g., “Open FancyZones editor”). Deep links would take you directly to the exact sub-page, possibly even highlighting the target toggle.
  • Optional inline toggles for simple boolean settings, letting you enable or disable a feature right from the search results without leaving the list.
  • Full keyboard navigation and compatibility with screen readers and high-contrast modes, building on the accessibility fixes already applied to the Command Palette.
  • Possible ties to the Command Palette itself, enabling you to search and control PowerToys settings from the launcher. Community members have already proposed indexing PowerToys module pages as part of Command Palette extensions.

The goal is straightforward: minimize the steps between “I want to change a setting” and actually changing it. If done well, this will feel like a natural extension of the Windows 11 design language, rather than a bolted-on afterthought.

Why a searchable Settings is a big deal

The productivity impact goes beyond mere convenience. For IT professionals and power users who rely on PowerToys daily, a search bar can shave minutes off routine configuration tasks. When you manage a fleet of machines or replicate the same layout across multiple workstations, quickly finding the right toggle saves cumulative hours. New users, too, benefit from lower onboarding friction—they’re more likely to discover and enable utilities like Text Extractor or Peek when they can surface them with a single query.

A searchable interface also reduces the volume of “where is this setting?” questions on community forums and enterprise help desks. And if Microsoft exposes robust deep-linking capabilities, organizations could script configuration workflows more reliably, making PowerToys a more enterprise-friendly tool.

The risks and trade-offs

Adding a centralized search is not without complications. Several potential pitfalls deserve attention:

Accidental misconfiguration: If search results include one-click toggles, it becomes trivially fast to modify system behavior. In managed environments where IT policies lock down certain modules via Group Policy, the search UI must respect those controls—otherwise it could become a backdoor to configuration drift. PowerToys already ships Group Policy templates; any search feature must integrate cleanly with them.

UX ambiguity: Inline toggles in search results could confuse users about whether they are acting on the actual setting or a shortcut. The design should clearly indicate that the result is a live control and offer a way to jump to the full settings page for more context.

Performance overhead: The v0.93 release focused heavily on shrinking installation size and improving startup times. A naive search implementation that eagerly indexes every module and loads all localized strings at launch could undo some of that work. Discussion on GitHub suggests contributors are mindful of lazy-loading and incremental indexing to keep the impact minimal.

Accessibility and localization: Search must work for everyone. The team has already invested in accessibility fixes for the Command Palette; those same standards must carry over to the Settings search. Screen-reader announcements, keyboard focus management, and localized auto-suggestions need thorough testing.

Security for AI-adjacent modules: PowerToys now includes features like Advanced Paste that can integrate with external AI services. Any search indexing or deep-linking mechanism must avoid exposing sensitive data (such as API keys or user tokens) in results or logs. The project’s PR review process already shows caution around such risks.

The open-source advantage—and the paperwork

Because PowerToys is an open-source project, community contributors can accelerate development—but that also adds procedural steps. Anyone can propose a design or even submit a pull request for a search bar, but maintainers must review it for code quality, security, accessibility, and localization. The team uses GitHub milestones and labels (“In for 0.94”) to coordinate, but labels are plans, not guarantees. Features can be split across multiple releases or iterated upon after merging.

In the meantime, the Command Palette itself serves as a useful stopgap. You can already launch it, start typing, and activate many Windows settings or plugin-powered actions. Community extensions have been proposed to include PowerToys module settings as searchable items, which could provide some of the desired discoverability even before a dedicated settings search arrives.

What should you do now?

If you haven’t already, update to PowerToys v0.93 from the GitHub releases page or via the built-in updater. The new dashboard and Command Palette speed alone are worth the upgrade. For settings discovery today, lean on the Command Palette (try the keyboard shortcut or launch it from the system tray) to quickly find what you need; it’s not a perfect substitute, but it’s faster than clicking through menus.

System administrators managing PowerToys across multiple devices should continue to use Group Policy templates to control which modules are available. Once a search feature lands, test it in a small pilot before broad deployment to ensure it doesn’t conflict with existing policies or introduce unwanted behavior.

To follow the development of the settings search, watch the PowerToys GitHub repository—specifically issues tagged for the v0.94 milestone. The public discussion threads offer a transparent view of the design choices, technical constraints, and timeline discussions as they evolve.

The bottom line

PowerToys v0.93 is a solid maturity step: the dashboard finally feels native to Windows 11, and the Command Palette is leaner and faster. But for a toolkit that has grown to encompass dozens of utilities, the lack of a settings search has become the most noticeable omission. Microsoft appears to agree, and the explicit roadmap entry for v0.94 suggests that a search bar is imminent. When it arrives, it will change the daily rhythm for power users—turning a slow, manual hunt into an instant, keyboard-driven action.

The challenge will be to ship something that is fast, accessible, secure, and manageable in enterprise settings—all without sacrificing the speed gains that v0.93 worked so hard to achieve. Given the project’s recent focus on polish and testing, that seems entirely within reach. Until the v0.94 release notes drop, however, treat the search feature as a highly probable but provisional improvement. In the meantime, enjoy the speed boost, explore the new dashboard, and keep an eye on the GitHub repo. The best is yet to come.