Windows 11’s new Run dialog is here: modern design, faster launch, and PowerToys DNA

Microsoft has quietly rebuilt one of Windows’ oldest power‑user tools, and it’s finally starting to show up in Windows 11 Insider builds. The classic Win+R Run dialog has been re‑engineered with a modern Fluent Design look, dark mode support, faster startup, and some clever new tricks that will feel instantly familiar to PowerToys fans.

In a new post on the Windows Command Line blog titled “The new Run dialog: faster, cleaner, and more capable,” Windows Terminal and PowerToys lead Clint Rutkas walks through how the team took a 30‑year‑old utility and rebuilt it from the ground up without breaking decades of muscle memory. The new experience is currently rolling out as an opt‑in feature for Windows Insiders in the Experimental channel, and Microsoft is explicitly asking power users to turn it on, hammer on it, and share feedback via Feedback Hub.

How to try the new Run dialog in Windows 11

For now, the redesigned Run dialog is hidden behind a feature toggle, which means only Windows Insiders can enable it. You’ll need to be on the Windows Insider Experimental Channel, then head to Settings > System > Advanced and flip on the “Run Dialog” option at the top of the screen to switch from the classic UI to the modern version. Once enabled, you still invoke it the same way you always have: press Win+R and the new dialog appears in place of the legacy one.

Microsoft is deliberately rolling this out slowly to give the team time to monitor performance, gather telemetry, and react to real‑world feedback before it ever reaches the wider Windows 11 audience. If you prefer the old experience, this approach also means you’re not being forced into the change—at least not yet—since the toggle keeps the new Run dialog fully optional while it’s being tested.

Data‑driven redesign without breaking 30 years of habits

Run has been part of Windows for over 30 years, and for many developers and IT pros it’s still a daily‑driver tool for launching apps, jumping to paths, and connecting to network resources. Rutkas notes that the team treated that history with a lot of respect: they knew people slam Win+R and expect it to appear “seemingly instantly,” remember and reuse their command history, and handle everything from wt and mstsc to long UNC paths without blinking.

Before touching the design, Microsoft added instrumentation to the old dialog to understand how people actually use it and how fast it really was. The data showed a median time‑to‑show of 103 ms, confirming the existing dialog was already very quick. It also revealed that the Browse button was essentially dead weight—only 0.0038 percent of users clicked it across a 35‑million‑user sample—and that some people rely on Run specifically as a quick way to paste text from the clipboard, scrub formatting, and copy it back out without running anything. Those insights created a hard baseline: any new Run dialog had to be at least as fast, keep the minimal UI, and preserve those “weird but important” workflows.

Built on PowerToys Command Palette and C#/WinUI 3

The new Run dialog has deep roots in PowerToys. Many of the early mockups were heavily inspired by PowerToys Run and the push to make keyboard‑first workflows faster. That exploration ultimately led to the creation of Command Palette (CmdPal) in PowerToys, a more ambitious launcher that Microsoft always intended could eventually graduate into the OS itself.

According to Rutkas, the same run command provider that powers CmdPal is now powering the new Run dialog in Windows 11. Under the hood, the modern Run is a C#/WinUI 3 application compiled with .NET Native AOT, giving it the speed and lean footprint of native code while still using modern C# language features and tooling. Microsoft says this architecture work is not just about Run: platform‑level optimizations made to get this dialog to load quickly also help other UI surfaces across Windows feel snappier and more efficient.

Faster than legacy Run: 94 ms median time‑to‑show

Performance was a non‑negotiable for this project, and the team is already beating the original target. With the rewrite in place, Microsoft is reporting a 94 ms median time‑to‑show for the new Run dialog—faster than the 103 ms baseline from the legacy version. That might sound like a small difference on paper, but for something that users open dozens of times a day, shaving off a few milliseconds adds up and is immediately noticeable to keyboard‑first users.

Rutkas calls out that this was a “huge team effort,” involving close collaboration with partners across the Windows platform to tighten up load paths and reduce overhead. The team still sees room to improve these numbers further as they continue to tune the experience in Insider builds, but hitting a faster median time at this stage is a strong signal that the new architecture is on the right track.

New tricks: quick ~\ home access and richer list icons

While the primary goal was to modernize Run without breaking workflows, Microsoft did sneak in at least one new capability that command‑line fans will appreciate. You can now type ~\ in the Run dialog to instantly jump to your user directory and then keep navigating just as you would from a shell, making it much quicker to launch tools or open folders relative to your home path.

The updated Run experience also supports richer icons in the results list, giving you clearer visual cues about what you’re about to launch. These refinements line up with the broader Fluent Design direction of Windows 11, which aims to modernize visuals without sacrificing clarity or speed. Combined with dark mode support and the C#/WinUI 3 foundation, the new Run feels less like a Windows 95 relic and more like a first‑class citizen in the current OS.

Community‑driven, and Microsoft wants more feedback

One of the most interesting parts of this story is how much of it happened in the open. Because CmdPal and PowerToys are open source, anyone who has contributed to Command Palette over the last few years has indirectly helped build part of Windows itself. Rutkas explicitly thanks the community for their role in shaping the new Run dialog, and the team reiterates its belief in open source as a way to test ideas quickly and polish them before they ship in the OS.

Now that the new Run is in Insider hands, the team is asking for even more feedback. If Run is a mission‑critical part of your workflow, Microsoft wants you to enable the new experience in the Experimental channel and file feedback through the Feedback Hub—or just hit Win+F, since, as Rutkas jokes, “we are all keyboard‑first users here.” The goal is to make sure this small but important piece of Windows works for everyone before it moves beyond Insiders.