Windows Search turns into a command bar in Microsoft's WinUI 3 rebuild

Search for something like an actor's height in Windows 11 today and, by The Verge's account, you wait a few seconds for what is essentially a miniature Bing result ^[11]. Microsoft is pitching the rebuild against that wait. "This new Windows Search experience is built for speed," Anshul Rawat, corporate vice president of the Windows product team, said, according to The Verge. "It's built on WinUI 3 and is part of our broader investment in modernizing our core Windows experiences." ^[8]

Part of the work is plumbing. Rawat said Microsoft is improving how search understands queries, "including better matching for typos and synonyms" ^[10]. The rest adds surface. The rebuilt box works as a launcher that can switch Bluetooth or dark mode, minimize windows and open apps side by side ^[2]. Engadget reported that from this fall it will carry out thousands of different actions typed as short commands ^[5].

So Microsoft is treating the shell as a product again, and in this release that means building on top as well as underneath. In Rawat's words, the product team wants "more natural ways to express what you need" and "more ways to get things done directly from search" ^[4]. The complaint on record is narrower, seconds of waiting for a simple answer ^[11], and only the speed work addresses it.

The Copilot piece has history. Engadget noted that the redesign comes less than a year after Microsoft promised to remove unnecessary Copilot integration from Windows 11 ^[15].

Microsoft has not said how large the speed and memory gains are, or which of the new actions administrators can turn off ^[9]. The Verge expects the new search in Windows 11 within months ^[7]. That leaves whoever rolls it out a short window to sort it on two axes. One is measured speed: whether the rebuilt box opens the app or file a user wanted faster than today, timed on the organisation's own hardware. The other is reach: whether an action stays on the PC, like dark mode, or leaves it, like a text sent through Phone Link ^[13] or a conversation with Copilot ^[14].

Faster with local actions only is an easy yes. Faster with actions that leave the PC is a yes for a pilot group, once you know which of those actions can be switched off. No measurable gain with local actions is a reason to wait for a later Insider build ^[1]. No measurable gain plus actions that reach a phone or Copilot is a hold. I'd start the pilot as soon as the box leaves Insider testing. The tradeoff is that, until Microsoft documents its controls, the pilot group gets the phone and Copilot actions along with the speed.