If you’re the kind of person who reaches for Win + R the moment you need to get something done on Windows, you already know what the Run dialog means to you. It’s fast, it’s no-nonsense, and it has been there since Windows 95 – more than 30 years ago. For decades, it sat untouched in the operating system, a tiny text box that somehow became one of the most powerful tools for developers, IT admins, and power users everywhere. And now, for the first time in a very long time, Microsoft has completely rebuilt it from the ground up.

The announcement came quietly on May 1, 2026, from the team behind Windows Terminal and PowerToys – Microsoft’s own developer productivity group. In a blog post written by Principal Product Manager Clint Rutkas, the team revealed that the new Run dialog is not just a cosmetic refresh. It’s a full architectural rebuild, powered by a modern technology stack, built with community feedback at its core, and designed to be faster than what it replaces.

The story of why this needed to happen is actually more interesting than you might expect. Before writing a single line of new code, the team did something smart – they measured how people actually used the old Run dialog. They added telemetry briefly to understand usage patterns before making design decisions. What they found was pretty fascinating.

First, the original Run dialog had a median time-to-show of 103 milliseconds – already blazing fast, which is exactly why touching it felt risky in the first place. Second, the “Browse” button that has sat in the dialog for years? It turns out almost nobody uses it. Out of a sample of 35 million users, only 0.0038% had ever clicked it. Third – and this one is kind of hilarious when you think about it – a meaningful number of users were using the Run dialog as a clipboard formatting scrubber. They’d paste text in there, select all, copy it back, and walk away without running anything at all, just to strip rich formatting.

These three data points shaped almost every decision in the redesign. The Browse button is gone. The performance target became “at least as fast, if not faster.” And support for clipboard use cases was kept intact.

The new dialog runs at a median time-to-show of 94 milliseconds – nine milliseconds faster than before, which sounds tiny but represents a genuine engineering achievement when you consider what changed under the hood. The old Run dialog was a legacy Win32 component, built on technology from the early 1990s. The new one is a C#/WinUI 3 application, compiled with .NET AOT (Ahead of Time compilation) so that it delivers native-code performance without the JIT startup delay you normally associate with managed code. This means it loads with the kind of snappiness you’d expect from a native application, while the team gets to work in a modern, safe language with modern tooling.

The visual update is real too. The redesigned dialog finally matches the Fluent Design language that Windows 11 introduced, with proper dark mode support and a clean, minimal look that feels like it belongs in 2026 rather than Windows 98. But Microsoft was careful not to bloat it up – the Windows 95-era philosophy of “minimal and fast” was explicitly cited as a design constraint they wanted to honor. The team didn’t add a search bar, a widget panel, or a Copilot button. They kept it focused.

One genuinely useful new feature is ~\ navigation. Type ~\ in the new Run dialog and it instantly drops you into your user home directory, from where you can keep typing a file path to navigate further, just like you would from a terminal prompt. For developers who are used to the ~ shorthand in Linux or macOS, this is a small quality-of-life addition that will save a lot of typing. Previously, navigating to your user folder meant remembering and typing out C:\Users\YourName\ every single time.

The backstory of how this dialog came to be is genuinely one of the more interesting pieces of Windows engineering history from recent years. It all ties back to PowerToys, Microsoft’s open-source power-user toolkit. The team had been experimenting for years with ideas for a smarter Run dialog through PowerToys Run, a launcher that many Windows users have come to love as a productivity tool. Those experiments eventually turned into a hackathon project called Command Palette – or “CmdPal” internally. The goal was to build something that could ultimately become part of the OS itself.

CmdPal gave the team a real-world testing ground. They could iterate fast, collect community feedback directly through GitHub and the PowerToys release cycle, and polish ideas before committing them to Windows itself. The Command Palette in PowerToys is often compared to macOS’s Spotlight launcher – a keyboard-first interface that lets you find and launch anything with just a few keystrokes, faster and more reliably than Windows Search. Now, the same underlying code that powers CmdPal in PowerToys has been brought directly into the new Run dialog. According to the team, the run command provider in CmdPal is literally the same code as the new Run dialog.

That means every open-source contributor who ever submitted a pull request or a bug fix to PowerToys’ Command Palette has, in a very real sense, contributed to a core part of Windows 11. That’s a meaningful shift in how Microsoft builds operating system features, and it signals a broader cultural change in how the company engages with its developer community.

For now, the new Run dialog is rolling out slowly through the Windows Insider Experimental Channel as an opt-in experience. To try it, you need to be on that channel, then head to Settings > System > Advanced and toggle on the “Run Dialog” option at the top. Microsoft is deliberately going slow here because for many users – particularly developers, sysadmins, and IT professionals – this dialog is mission-critical. A broken Run dialog is not a minor inconvenience. It can disrupt deeply ingrained workflows built on decades of muscle memory.

The community response has been what you’d expect from a feature with this kind of passionate user base. Some are thrilled, praising the speed improvement and the cleaner look. Others are pushing back, arguing that the more meaningful usability gaps – like being able to set a working directory for command-line launches, or a larger history list – still haven’t been addressed. One commenter on the official blog post pointed out that launching anything from Run opens it in System32 by default, which is largely useless as a starting point for most terminal commands. These are fair criticisms, and Microsoft has actively encouraged feedback through the Windows Feedback Hub (Win + F) so the team can keep iterating.

What’s clear is that this is not a finished product. It’s the beginning of a new chapter for one of Windows’ oldest and most beloved tools. Microsoft has done the hard foundational work – the modern tech stack, the performance baseline, the design alignment – and now the question is how far they’ll take it. Given that CmdPal is already significantly more powerful than a plain run box, and given that the same code underpins both, there’s plenty of room for the two to grow closer together over time. The line between a simple run command dialog and a full-blown system launcher is thinner than it’s ever been, and Microsoft is walking it carefully.