The redesign also comes with an unusually revealing statistic. Microsoft says just 0.0038% of users in a 35-million-user sample clicked Browse in the classic dialog. That is compelling evidence of low observed usage—not proof that nobody needs the button, and certainly not a census of every Run user since Windows 95.
The useful story is therefore bigger than a new coat of paint: what is actually shipping, what Microsoft measured, and how to try the replacement without surrendering the classic experience.
What has arrived—and what December still means
Microsoft identifies the Release Preview update as KB5132057, covering all editions of the two listed Windows 11 versions:
| Windows 11 version | Release Preview build |
|---|---|
| 25H2 | 26200.10066 |
| 26H2 | 26300.10066 |
The Run entry appears under Gradual rollout. Microsoft explains that features in this category reach devices in phases, so installing the update does not necessarily make every listed feature immediately available.
Windows Latest expects an optional public update later in November, followed by the December 8, 2026 Patch Tuesday update. That is the publication’s rollout expectation. The Microsoft release notes establish the preview release and staged availability, but they do not promise those public-release dates or universal activation by December 8.
This distinction matters when troubleshooting. “The update is installed” and “the feature is enabled on this device” are different checkpoints under the rollout model Microsoft describes. A missing switch should not automatically send you hunting for a broken installation.
There is also a scope boundary: the confirmed November announcement concerns 25H2 and 26H2 Release Preview. It should not be stretched into a claim about every Windows 11 version. Microsoft’s announcement separately lists a 26H1 preview build; that does not establish that it receives this same Run change.
Bottom line: the redesign has advanced to another distribution stage. December remains an expectation, not an evidence-backed deadline for every PC.
Browse was rarely used, but the denominator matters
In his May 1 announcement on the Windows Command Line blog, Microsoft Principal Product Manager Clint Rutkas explained that the team briefly instrumented the existing dialog to understand its performance and usage. The Browse measurement was one result of that exercise.
Taking the published figures literally, 0.0038% of 35 million works out to approximately 1,330 users. That calculation helps make a very small percentage understandable. It should not become “only 1,330 people ever used Browse.”
Why the caution? Microsoft’s account does not specify the observation window, provide a detailed explanation of the counting methodology, or establish lifetime usage. The defensible conclusion is narrower: Browse attracted very little use during the measurement Microsoft describes.
Windows Latest reports that the modern design omits the button. Its practical purpose in the classic dialog is to let users locate a file or application rather than type the complete path. Removing that affordance may be inconsequential to someone who already knows the command, but less welcome to someone who occasionally needs help finding the target.
Our assessment is that low usage can justify reconsidering a control without proving the underlying workflow is worthless. A rarely used feature can still be important to the people who use it. The appropriate test is whether the replacement leaves those users a reasonable way to complete their task—not whether a percentage looks sufficiently microscopic.
For this transition, the ability to switch back is an important safeguard. Microsoft documents that the classic dialog remains accessible by turning the modern experience off.
Faster to appear does not mean faster to execute
Microsoft reports these median time-to-show results:
- Classic Run: 103 milliseconds.
- Modern Run: 94 milliseconds.
That is a reduction of 9 milliseconds, or approximately 8.7% relative to the older measurement. These are Microsoft’s reported results, not an independently reproduced WindowsForum benchmark.
The metric concerns showing the dialog. It does not measure how quickly an application finishes launching after you submit a command, or how quickly a network location responds. Microsoft’s documentation labels it a launch-time comparison for Run itself.
Nine milliseconds is not a reason to reorganize your working day. The more meaningful engineering claim is that the refreshed interface did not require accepting a slower reported median.
There are limits to what the figures establish. Microsoft’s announcement does not publish a hardware breakdown, confidence intervals, or enough measurement detail to reproduce the comparison. A median also cannot describe every slow launch or every device. Accordingly, the numbers support a modest performance claim, not a promise that every PC will improve by exactly nine milliseconds.
Nor should a gaming monitor’s frame interval be treated as an equivalent benchmark. The comparison would only become useful with clearly defined measurement boundaries. For readers evaluating this update, the sensible questions are more practical: does Run appear promptly, accept input reliably, and preserve the commands they depend on?
Why C#, WinUI 3 and AOT matter
Microsoft says the replacement is written in C# with WinUI 3, compiled using .NET ahead-of-time compilation, and shares its Run-command implementation with PowerToys Command Palette. That is a substantive implementation change, rather than merely a restyled classic window.
Microsoft’s.NET documentation supplies useful context: Native AOT compiles intermediate code into native code when the application is published. It does not use a just-in-time compiler when the application runs. Microsoft identifies faster startup and smaller memory footprints as benefits of this deployment model.
That helps explain why “written in C#” does not, by itself, tell you how much compilation work must happen when a user opens an application. The deployment model matters alongside the language and interface framework.
However, AOT is not a complete explanation of the 94-millisecond result. Microsoft does not publish an experiment isolating how much of Run’s improvement comes from compilation, interface work, or other platform changes. Treating the entire reduction as an AOT dividend would go beyond the evidence.
The developer takeaway is encouraging but bounded: this is an example of Microsoft using a modern application stack for a latency-sensitive Windows interface. It is not proof that every WinUI application automatically outperforms a Win32 equivalent.
What changes in everyday use
Microsoft’s documentation describes a Fluent-style interface that follows the system theme, including dark mode. The familiar jobs remain: executing commands, opening local and network paths, and recalling previous commands. Up and Down cycle through command history.
The new navigation shortcut is:
~\
Typing it takes you to your user directory, with the ability to continue navigating into subdirectories. This is a convenience inside Run—not evidence that the dialog has become a full command shell.
The PowerToys connection should be understood with similar restraint. Sharing the Run-command provider does not mean Windows has absorbed every Command Palette capability. Microsoft explicitly describes Command Palette as doing more than the Run dialog.
There is also a wonderfully mundane discovery in Microsoft’s usage research: some people paste formatted text into Run, copy it back out, and never execute anything. They are using the field to strip formatting.
That is a useful reminder for interface designers. The official purpose of a control does not necessarily capture every reason people keep returning to it. Even a small utility can accumulate workflows its creators did not originally anticipate.
How to enable the modern Run dialog
First, your device needs a Windows build that has received the feature. Microsoft’s general documentation also specifies the Advanced settings system component as a requirement. Having a relevant update installed is not sufficient if the staged rollout has not reached your PC.
Once the option is available:
- Open Settings.
- Go to System > Advanced.
- Enable the Run setting. The November release notes call it New Run dialog; Microsoft’s dedicated guide calls it Run Dialog.
- Press Win+R to open the redesigned experience.
- To restore classic Run, return to the same page and turn the setting off.
Success means the shortcut opens the redesigned interface. You do not need to judge the result with a stopwatch.
For a useful first check, we suggest trying a familiar command, a known local path, and—if relevant to your work—a network path you normally use. Then test history navigation and the home-directory shortcut. These checks focus on the capabilities Microsoft documents rather than assuming that a visual refresh proves every individual workflow works correctly.
For support teams, record which experience is enabled when investigating a complaint. Asking a user to compare the same task in classic and modern Run is more informative than asking whether the new one “feels different.”
If the switch is missing
Start with availability rather than repair.
Check the release scope. The November preview announcement is specific to the listed 25H2 and 26H2 builds. Do not assume instructions for that release apply unchanged to another Windows version or servicing channel.
Allow for staged delivery. Microsoft places Run in the gradual-rollout group. A missing control therefore does not, on its own, demonstrate a failed update. Reinstalling Windows would be a remarkably large hammer for evidence this small.
Consider organizational policy. Microsoft warns that policies can hide or disable Advanced settings controls and advises affected users to contact their administrator. On a managed PC, the absence of a switch may reflect configuration rather than a malfunction.
There is one documentation wrinkle worth knowing. The dedicated Run guide still describes Experimental-channel availability, while the newer November 13 announcement confirms Release Preview distribution. For present build availability, the newer, version-specific announcement is the more relevant evidence; the older guide remains useful for operation and requirements.
We would not recommend treating a hidden-feature workaround as the normal installation procedure. The documented settings switch gives users a clearer, reversible path.
A small redesign deserves a precise verdict
The most useful way to evaluate this change is not as a contest between nostalgia and modernity. Ask whether it improves consistency without disrupting work.
Microsoft’s evidence supports a refreshed, optional Run experience with a lower reported median time-to-show, theme support and a convenient user-directory shortcut. It also supports an unusually low Browse usage figure—but not the conclusion that every Browse-dependent workflow is disposable.
Our verdict is cautiously positive: keeping an easy rollback is the right approach for a tool built around habit. Try the redesign when it becomes available, check the tasks you actually perform, and retain the classic option if it serves you better.
Above all, distinguish the confirmed release from the projected schedule. Release Preview availability is established; “everyone in December” is not. Windows users deserve that distinction just as much as they deserve a Run box that gets out of their way.