A rebuilt Run dialog has landed in Windows 11 preview builds, and it’s not just a cosmetic touch-up. Microsoft recast the decades-old prompt in WinUI 3, and the company claims the modern version is measurably faster than the legacy box, while staying entirely optional. The median time-to-show clocked in at 94 milliseconds, shaving about 10 milliseconds off the old dialog, based on internal telemetry. For power users who summon Run hundreds of times a day, that’s less about a stopwatch victory and more about preserving muscle memory without compromise.
The change may seem tiny, but it arrives as part of a broader Windows K2 effort that aims to win back enthusiasts by prioritizing performance and reliability. And it arrives with a philosophy that the Windows shell has sorely needed: modernize a component fully, prove it’s faster, and let users decide when to switch.
Inside the WinUI 3 rebuild: What’s new and what’s gone
The most visible difference is the new look. Gone is the flat, Win32-era gray box that traces its lineage to Windows 95. In its place is a Fluent Design surface with rounded corners, support for light and dark modes, and the Mica backdrop material that blends the dialog into the desktop environment. The new Run box also shows the icon of any program you launch, a subtle touch that makes it feel like a native part of Windows 11 rather than a fossil.
Under the hood, the dialog is written in C# and WinUI 3, the same modern framework that powers parts of File Explorer and other shell components. That matters because WinUI applications have a reputation for launching slower than their Win32 counterparts—a perception born from early Windows 11 experiments. Here, Microsoft claims to have bucked that trend: the 94-millisecond median launch time beats the legacy box’s 104 milliseconds, according to telemetry collected from Insiders.
That 10-millisecond gap is statistically small and unlikely to be consciously perceived, but it carries symbolic weight. Microsoft set out to prove that a modern UI framework could match or exceed the responsiveness of a decades-old Win32 dialog, and it did. The company was careful to measure time-to-show and usage patterns before making changes, a discipline that has been missing from several Windows 11 updates.
One feature that didn’t survive the transition is the Browse button. Microsoft’s data revealed that only 0.0038 percent of users clicked it in a sample of 35 million. The old button let you hunt for executables through a file picker, but the Run box is overwhelmingly a keyboard-first tool. Removing it simplifies the interface, and the legacy dialog remains available for those who still want it.
A new addition is support for ~\ as a shortcut to the user’s home directory—a nicety familiar to command-line users and developers. This small tweak shows that Microsoft is considering power users who navigate paths from muscle memory, not just casual launchers.
What the new Run dialog means for different audiences
For everyday users: If you rarely open Run, you may not notice the change at all. The dialog looks cleaner and blends better with Windows 11’s design, but the core function—typing a command and hitting Enter—remains identical. You won’t lose any functionality unless you relied on the Browse button, which was seldom used anyway.
For power users and enthusiasts: This is where the rubber meets the road. You invoke Run dozens or even hundreds of times daily to launch cmd, regedit, services.msc, appwiz.cpl, UNC paths, or shell folders. The biggest concern is whether the new dialog feels as instant as the old one—and whether it drops the first keystroke while the UI draws. Microsoft claims it’s faster, and early Insider reports suggest it doesn’t miss inputs. The addition of the ~\ shortcut and program icons is a welcome upgrade, and the optional nature means you can revert with a toggle if anything breaks your workflow.
For IT administrators and enterprise: The opt-in rollout is critical. You can test the new Run dialog in controlled environments, checking for compatibility with your scripts, remote sessions, and lockdown policies. Since the legacy box remains the default, you won’t have to scramble to accommodate a forced change. When the modern version eventually becomes the default (assuming it passes muster), you’ll have had ample time to validate it. The telemetry-backed removal of the Browse button also demonstrates a data-driven approach that admins often ask for: measure before cutting.
How we got to an optional, faster Run dialog
Windows’ Run dialog has been largely untouched since the Windows 95 days precisely because it was simple, reliable, and fast enough to disappear from consciousness. For years, Microsoft’s attempts to modernize the shell—from the Windows 8 Start screen to the Windows 11 taskbar and File Explorer—often felt like trade-offs: you got a fresher look but slower performance and lost features.
File Explorer became the poster child for this problem. Tabs, a modern command bar, cloud integration, and partial WinUI rewrites brought visual cohesion but also introduced latency and inconsistency. Users learned to distrust UI makeovers, assuming “modern” meant “bloated.”
The Run dialog represented an acid test. It’s a single-purpose tool with almost no dependencies, so there was no excuse for making it slower. Microsoft’s Windows K2 initiative, recently reported as an internal push to refocus the OS on performance, gamers, and power users, created the mandate to modernize without regressing. The Run box is one of the first visible fruits of that shift.
Crucially, the team didn’t just guess. They instrumented the old dialog, measured real usage, and set a performance budget before writing code. That’s a departure from the “ship now, fix later” approach that plagued earlier Windows 11 releases.
What to do now: How to try the new Run box
The modern Run dialog is currently available in Windows 11 Insider Preview builds—specifically in the Dev and Beta channels. If you’re already enrolled, you can enable it with these steps:
- Open Settings (Win+I).
- Navigate to System > Advanced (or search “Run dialog” in Settings).
- Toggle “New Run dialog” to On.
The change takes effect immediately. Test the dialog by pressing Win+R and launching a few commands. Pay attention to whether the first keystroke registers, how quickly the box appears, and whether any of your edge-case commands still work.
If you run into trouble, you can flip the toggle back off. The legacy dialog remains untouched and is the default, so you’re not forced into the new experience.
For feedback, use the Feedback Hub (Win+F) under the Desktop Environment > Shell category. Microsoft has explicitly asked for feedback, indicating the team plans to iterate based on user reports.
Outlook: A small victory that could reshape Windows modernization
The new Run dialog, by itself, won’t transform Windows 11. But it sets a pattern that Microsoft would do well to replicate: identify a well-understood legacy component, rebuild it entirely in a modern framework while exceeding the original’s performance, remove non-essential features based on hard data, and ship it as an opt-in until trust is earned.
If this discipline extends to other shell surfaces—Context Menus, Task Manager, Control Panel applets—Windows 11 could shed the reputation that modernization must come at the expense of speed. The K2 effort suggests Microsoft is aware that power users have been drifting toward skepticism, and that winning them back requires more than marketing. It requires quiet, measurable improvements in the places they touch every day.
For now, the Run dialog is one data point. But it’s a promising one: a reminder that the fastest Windows component can still be made faster, and that the best way to modernize is to replace the old only when the new is undeniably better.