Microsoft is quietly testing a redesigned Run dialog for Windows 11 that replaces the 30‑year‑old, Windows‑95 era quick launcher with a modern, Fluent‑style overlay — and it’s
optional by design: the new Run appears in preview builds and can be switched on from Settings → System → Advanced when the code is present on your device.
Background
The Run dialog (Win+R) has been a staple of Windows since the 1990s, prized by power users for its raw speed and simplicity. Over decades its functionality remained essentially unchanged while the rest of the OS migrated to Fluent Design and WinUI. That long‑standing visual gap has driven periodic community requests for a refresh and, as of recent preview builds, Microsoft has begun testing a modern replacement that keeps Run’s core behavior while updating the experience for Windows 11. This change is part of a broader push to modernize legacy UI surfaces — adding dark mode to historical dialogs, polishing File Explorer prompts, and exposing a new “Advanced Settings” surface for power users and developers. Microsoft is rolling these updates gradually to Insiders before any general release.
What’s actually new in the redesigned Run dialog
The modern Run preview is a visual and interaction update rather than a reinvention. Key user-facing differences reported in preview screenshots and notes include:
- Larger input area with more generous spacing and rounded corners consistent with Windows 11 Fluent design.
- Recent commands / history list shown above the text box so previously used entries are one click away.
- Inline app icons and richer match feedback when typed entries resolve to installed apps or Store packages, improving visual clarity.
- Dark mode support and tone-aware backgrounds so Run no longer looks out of place when system dark theme is active. Microsoft has explicitly noted Run dark mode is rolling out in preview channels.
- Optional and gated: by default the classic Run remains active; the modern Run is presented behind an opt‑in toggle in the Settings app.
A few small but notable omissions have been observed in initial screenshots: the traditional
Browse button (previously used to pick an executable or file via Explorer) is reportedly not present in the modern UI, which may impact certain workflows. Early reports also indicate the previewed UI may still be partially inactive in some builds — Microsoft is testing code paths across channels and devices.
Why Microsoft made Run optional and gated
Microsoft is being conservative for good reasons. Run is small but relied on by IT pros, support staff, and power users; any functional regression could break automation or habit‑driven tasks. Making the modern Run an opt‑in control in a central “Advanced Settings” surface lets testers try the new UI without forcing it on every user or device. The Advanced Settings approach also creates a place to expose developer and experimental features in a discoverable, controlled way. This approach also reduces enterprise risk: admins can continue to keep legacy UI active while evaluating the modern overlay before approving a broader roll‑out.
How to enable the redesigned Run dialog (insider / preview method)
If the modern Run has been delivered to your PC via Microsoft’s controlled rollout, the toggle to opt in lives in the new Advanced Settings page. The standard path reported across preview coverage is:
- Open Settings.
- Go to System → Advanced.
- Locate the Run dialog (or similar) toggle and set it to On.
- Press Win+R to open the modern Run UI.
Multiple outlets and community screenshots show the control under Settings → System → Advanced once the Advanced Settings page is available in your build. If the toggle is present the new UI becomes active immediately when you press Win+R.
If you don’t see the Advanced Settings page
The Advanced Settings surface is itself a preview component and may not be visible on stable builds. There are two supported ways to get the toggle:
- Join the Windows Insider Program and pick the Dev or Beta channel, then update Windows so that preview packages land on your device. Many of the Run UI changes are being staged to Insider channels first.
- Advanced users who understand the risks can unlock the feature surface using community tools. ViVeTool, a common utility used to toggle hidden Windows feature flags, has been used to enable the Advanced Settings page in supported preview builds with the command:
vivetool /enable /id:56005157
After rebooting, Advanced Settings appears under Settings → System → Advanced and the Run toggle (if present) becomes visible. This method is third‑party and unsupported by Microsoft; it should be used only on test machines or non‑production devices. Back up the system before attempting.
Step‑by‑step: enabling modern Run using ViVeTool (technical steps)
- Download ViVeTool from the project repository and extract it to a folder (e.g., C:\ViVe).
- Open an elevated Command Prompt (Run as administrator).
- Change directory to the ViVeTool folder, e.g.:
- cd C:\ViVe
- Run:
- vivetool /enable /id:56005157
- Reboot the PC.
- Open Settings → System → Advanced. If the Advanced Settings UI is active and the Run flag is present, toggle it on.
- Press Win+R to invoke the modern Run overlay.
This sequence has been circulated in community how‑tos and tested by Insiders, but it uses an unofficial tool. ViVeTool modifies feature enablement flags that Microsoft may change without notice. The best practice is to use this only for testing and to avoid applying it to critical systems.
If you’re on Stable builds — what to expect and alternatives
For non‑Insider users the modern Run UI will arrive only when Microsoft includes it in a public release. Microsoft’s update notes and staged KB packages have previously carried related changes (for example, Run dark mode and File Explorer dialog polish), and the company is using staggered rollouts and enablement packages to gate features. Expect a phased delivery rather than a single big‑bang release. If the modern Run is not available or if the new UI removes a feature you rely on (like Browse), there are robust third‑party launchers and tools that can fill the gap while giving modern design and extra features:
- PowerToys Run — the lightweight launcher included in Microsoft PowerToys provides fuzzy search, plugin support and keyboard‑centric command launching.
- Raycast (and similar launcher apps) — a modern launcher with extensibility, clipboard history, and command actions. These tools often offer more power and customization than legacy Run.
Deployment, enterprise considerations, and configuration management
The modern Run being opt‑in helps IT administrators minimize disruption, but a few practical considerations remain:
- Group Policy / MDM controls: At the time of preview reporting there’s no published Group Policy specifically targeting the modern Run UI. Existing Group Policy controls to remove Run from Start or disable the Run dialog continue to work, and traditional registry locks (e.g., NoRun) remain effective to restrain or remove access. Enterprises should test the new UI in controlled rings before broad deployment.
- Scripted enablement: If Microsoft exposes an official feature flag or MDM policy, that will be the recommended enterprise method. Avoid deploying third‑party feature‑toggling tools in production images unless Microsoft documents support.
- Accessibility & automation: Test scripts, screen readers, and automation that rely on Run’s old window geometry or behavior should be validated. Although the core capabilities (typing a command and pressing Enter) appear unchanged in preview, the new visual layer could change window focus sequences or UI element coordinates used by automation tools.
Potential benefits
- Visual consistency: Run will no longer feel visually jarring in dark theme or on systems that use Mica and rounded Fluent surfaces. This reduces cognitive friction for users switching between modern apps and legacy dialogs.
- Usability improvements: The recent commands list and inline icons shorten interaction time for repeated tasks and reduce ambiguity when multiple similarly named executables exist.
- Opportunity for future features: Rebuilding Run on WinUI 3/WinRT surface allows Microsoft to add context, richer app matching, or integration with other launchers or Copilot features later without reworking the legacy dialog. Early reports suggest Microsoft is building the modern Run with modern UI tech, which can unlock enhancements.
Risks and potential downsides
- Feature parity concerns: The missing Browse button in preview screenshots is a concrete change that could impede workflows where users rely on Explorer selection rather than typing paths. That omission has been noted by early testers and should be considered a real impact for some users.
- Performance and reliability: Any new UI element adds code paths and potential regressions. Insiders have reported the modern Run is sometimes nonfunctional or gated, and Microsoft is actively testing it. Early adopters who enable experimental flags should expect occasional instability.
- Enterprise policy ambiguity: Organizations that centrally manage UI experience may face a lag between Microsoft’s preview work and published policy templates or MDM options. In the short term administrators must rely on existing controls or block third‑party toggles.
- Accessibility implications: New UI surfaces must be validated for screen reader, keyboard navigation, contrast, and high‑DPI support. The modern Run may address some visual accessibility issues (dark mode), but changes to focus, element ordering, or touch targets should be verified across assistive technologies.
Verification and caveats about build numbers and timing
Multiple community posts and coverage have linked the modern Run appearance to specific preview builds (for example, Build 26534 in a handful of reports), but those build‑level attributions are inconsistent and not always confirmed by Microsoft. Microsoft’s official release notes have referenced Run dark mode and Advanced Settings rollouts in certain Insider flights (for example, build 26220.6780 notes and KB release entries), but the exact build that first surfaces the modern Run may vary by channel and region due to controlled rollouts. Treat specific build numbers mentioned on social posts and early blogs as provisional until Microsoft publishes formal Flight Hub or Knowledge Base documentation.
Practical recommendations (short checklist)
- If you want to test the modern Run UI:
- Use an Insider Beta or Dev VM, or a non‑critical test PC.
- Prefer official Microsoft updates over third‑party tools; if using ViVeTool, be aware of the risk and back up the device.
- If you rely on the Browse button or automation:
- Delay enabling the modern Run until Microsoft confirms feature parity or supplies an alternate mechanism. Test automation and assistive tech thoroughly.
- For organizations:
- Pilot the change in a controlled ring and evaluate Group Policy/MDM blocking options before wide deployment. Monitor Microsoft’s release notes and policy ADMX updates.
Conclusion
The redesigned Run dialog for Windows 11 is a welcome and overdue polish that brings a tiny but frequently used tool into the modern visual language of the OS. Microsoft’s cautious, opt‑in approach via Advanced Settings respects legacy usage while letting Insiders validate the experience. Early previews show useful usability additions — history, icons, and dark mode — but also raise practical questions (Browse removal, build variability, enterprise controls) that demand careful testing before broad adoption.
For power users who prefer an immediately modern launcher, Microsoft’s built‑in path will arrive in time; meanwhile, proven third‑party launchers and PowerToys Run remain reliable alternatives. Test the new Run on non‑production devices, validate automation and accessibility scenarios, and watch for Microsoft’s official rollout and policy documentation before making sweeping changes across managed fleets.
Source: Neowin
https://www.neowin.net/guides/how-to-enable-redesigned-run-dialog-in-windows-11/