Microsoft is quietly testing a modernized Run dialog for Windows 11 that replaces the decades‑old Win32 pop‑up with a Fluent‑style overlay, and while it isn’t yet enabled for everyone, Insiders can opt in — or force the feature on — in preview builds that include the KB5072043 update.
Background / Overview
The Run dialog (Win+R) is one of Windows’ oldest productivity primitives — a single keystroke that launches apps, shell commands, Control Panel applets and UNC paths. Microsoft has begun migrating this small but widely used surface to match Windows 11’s modern visual language: a larger overlay, rounded corners, tone‑aware backgrounds and a brief Most‑Recently‑Used (MRU) list that surfaces recent commands. Early sightings and hands‑on reports show the UI present in Insider preview artifacts; Microsoft is staging the rollout behind opt‑in controls and server‑side flags so the classic Run experience remains the default for most users. Why this matters: the change is primarily visual and ergonomic, not functional. Power users should still be able to type commands like regedit, calc or \server\share and hit Enter. But the modern Run aims to reduce the jarring Win32 contrast in dark themes, improve discoverability with inline icons for matched apps, and speed repeated tasks with an MRU list. These are modest, high‑frequency wins that reduce friction without reinventing Run’s role.
What’s included in the new Run dialog
- Fluent UI overlay: a larger, centered card instead of the compact Win32 modal, with system‑aware theming and rounded corners.
- Expanded input area: bigger text field and improved spacing for high‑DPI, pen and touch use.
- Most‑Recently‑Used (MRU) list: a short history of previously run commands shown above the input for quick re‑invocation.
- Inline icons and match feedback: when typed text resolves to a known executable or Store app, the item shows an icon and richer affordance.
- Opt‑in control: currently exposed behind Settings → System → Advanced in preview builds; the classic Run remains the default while Microsoft collects feedback.
These changes are intentionally restrained: Microsoft appears to be modernizing presentation and discoverability rather than turning Run into a fully‑fledged extensible launcher like PowerToys Run or Raycast. Expect the built‑in Run to remain a lightweight, keyboard‑first tool while third‑party launchers continue to serve power‑user extensibility.
What you need to try it today
- A PC enrolled in the Windows Insider Program (Dev or Beta channels) that has received the preview build containing the modern Run bits.
- The preview update package identified by Microsoft as KB5072043 — released as Windows 11 Insider Preview Build 26220.7523 — is the confirmed delivery vehicle for these preview bits in recent Insider flights. Being on the build does not guarantee exposure because Microsoft also uses server‑side gating.
- If the Settings toggle isn’t present, many testers use ViVeTool to enable feature flags; the commonly reported feature IDs associated with the modern Run are 57156807, 57259990, 58527096, 58381341 (order generally does not matter). Use ViVeTool only on test or non‑production systems and verify the IDs against the version of ViVeTool and the build you’re running.
How to enable the modern Run dialog (supported path)
- Enroll a test device in the Windows Insider Program (Dev or Beta channel).
- Update via Settings → Windows Update until you reach Preview Build 26220.7523 (KB5072043) or later that contains the modern Run bits.
- Reboot, then open Settings → System → Advanced and look for the toggle labeled Run dialog or Use the modern Run dialog when pressing Win+R. Flip it on.
- Press Win+R to confirm the modern overlay appears. If you do not see the toggle, the feature may still be server‑gated for your machine.
How to force‑enable the modern Run dialog with ViVeTool (unsupported)
For enthusiasts who understand the risks: ViVeTool is a community utility commonly used to flip Windows feature flags that are shipped but not yet exposed. This method is unsupported by Microsoft and can expose unfinished UI, instability, or regressions. Do this only on disposable test machines or virtual machines and keep backups/snapshots.
- Download ViVeTool from its official repository release and extract it to a folder (for example C:\ViVeTool).
- Open an elevated Command Prompt (Run as administrator).
- Change directory to your ViVeTool folder:
cd C:\ViVeTool
- Run the enable command (example set reported by multiple community guides):
vivetool /enable /id:57156807,57259990,58527096,58381341
- Reboot.
- Open Settings → System → Advanced and enable the Run dialog toggle if it appears, then press Win+R to test.
Important safety notes:
- Validate the feature IDs against the ViVeTool release and your build before toggling; if an ID isn’t present on your build ViVeTool will return an error. Use vivetool /query /id:<id> to inspect state first.
- If you need to undo the change, re‑run ViVeTool with /disable for the same IDs and reboot.
Verification and cross‑checks
Multiple independent publications and community artifacts corroborate the modern Run sightings:
- The Windows Insider Blog lists the relevant preview update as Build 26220.7523 (KB5072043), which is the package Insiders should see in December Insider flights.
- Coverage by Windows Central, The Verge and PC Gamer confirms the modern Run UI appears as a preview overlay and is gated behind Advanced Settings.
- Community how‑tos and enthusiasts’ reporting (including Pureinfotech and multiple forum investigation threads) list the ViVeTool feature IDs commonly used to expose the modern Run; these sources align on the same four IDs. Treat those IDs as provisional and verify against your build before use.
What to test after enabling (a checklist for power users and admins)
- Latency and responsiveness: press Win+R repeatedly to confirm the overlay is instant and not slower than the classic box.
- Keyboard focus behavior: ensure Win+R immediately puts input focus into the text field and that Ctrl+Shift+Enter still triggers elevation if required.
- MRU behavior and privacy: check how many recent commands are stored, whether history can be cleared and whether retention is local only.
- Automation compatibility: validate UI Automation, scripts and macros that interact with the Run dialog still work (automation IDs, focusable elements and coordinates can change if the UI framework changes).
- Accessibility: test with screen readers, high‑contrast themes, keyboard navigation and magnifiers to ensure parity with the legacy dialog.
- Enterprise policy: confirm existing Group Policy / MDM controls that hide or disable Run behave as expected when the modern overlay is present.
Critical analysis — strengths and practical benefits
- Visual consistency: the modern Run removes the jarring Win32 flash in dark mode and aligns Run with Windows 11’s Fluent/WinUI surfaces. This is a high‑value cosmetic and usability fix for many users.
- Micro‑productivity: the MRU list and inline icons are practical improvements that reduce typing and reduce the chance of launching the wrong target when similarly named items exist.
- Conservative rollout: Microsoft’s opt‑in model (toggle in Advanced Settings) respects the needs of admins and power users who require predictable behavior, allowing feedback before a broad rollout.
These are concrete, testable gains: improved theming, better discoverability for casual users and small speed wins for specialists who reuse commands frequently.
Risks, unknowns and where to be cautious
- Automation and compatibility fragility: Run is used in scripts, demos and enterprise workflows. A UI rewrite (likely moving from classic Win32 to WinUI/Windows App SDK) can alter automation hooks, control names and behavior. Validate automation paths before deploying.
- Accessibility parity: small UI changes can unintentionally break screen‑reader experiences or keyboard navigation. Early testing shows promise, but full parity should be confirmed in later builds and official engineering notes.
- Privacy concerns with MRU: recent commands could surface sensitive hostnames, file paths or commands on shared devices. Enterprises should demand clear controls for history retention and provide Group Policy to disable or clear MRU if necessary.
- Staged‑rollout fragmentation: server‑side gating can create a mixed fleet experience where identical builds behave differently, complicating documentation and support. Admins must pilot and standardize acceptance criteria before enabling broadly.
- ViVeTool and unsupported toggles: enabling hidden flags with ViVeTool can expose unstable code and is unsupported — do not use on production endpoints. Several community threads and guides consistently warn to use VMs or test hardware.
Where claims are provisional: community‑reported feature IDs and build attributions are reliable indicators but can change as Microsoft iterates; flag lists and build numbers are subject to revision. Treat any third‑party ID list as an
implementation snapshot not an immutable truth.
Enterprise considerations and recommendations
- Pilot the modern Run in a controlled ring that includes helpdesk staff, automation engineers and assistive‑technology users.
- Update support documentation to show both classic and modern screenshots and provide troubleshooting guidance for fallback (turning the toggle off).
- Monitor for Group Policy/ADMX updates from Microsoft that explicitly control the Run dialog exposure or MRU retention.
- If MRU history policy is a compliance issue, request or implement a policy to clear or disable Run history on shared systems before broad enabling.
- Avoid using ViVeTool on managed endpoints; use Microsoft’s Insider program and supported update channels for controlled testing.
Practical troubleshooting & rollback
- If the modern Run causes problems, revert the change using Settings → System → Advanced (toggle off).
- If you used ViVeTool and need to undo the forced flags, run:
- vivetool /disable /id:57156807,57259990,58527096,58381341
- Reboot.
- Keep a system snapshot or image when experimenting with Insider builds or hidden flags so you can restore quickly if anything impacts workflows.
Final assessment
The modern Run dialog is a careful, low‑risk modernization that brings a long‑neglected micro‑surface into visual parity with Windows 11. The changes are deliberate and restrained: polish and small productivity gains without attempting to replace extensible third‑party launchers. Microsoft’s gated, opt‑in rollout is the correct approach for a utility relied on by IT pros and automations; it minimizes disruption while allowing telemetry and accessibility testing to guide final decisions. That said, administrators and power users should validate automation and accessibility before adopting broadly, and avoid unsupported flag toggles on production devices.
For enthusiasts who want to experiment: enroll a
non‑production test machine in the Windows Insider Program, confirm you have Build 26220.7523 (KB5072043) or later, and look in Settings → System → Advanced for the toggle. If you choose the community route with ViVeTool, verify IDs and use VMs or lab hardware only. The Run dialog is small, but it’s invoked many times by skilled users. Modernizing it without taking away the speed and predictability that made it useful is the narrow design goal Microsoft appears to be pursuing — and the current preview approach gives both testers and administrators the control needed to make that outcome likely.
Source: Windows Report
Here's How to Enable Windows 11's New, Modern Run Dialog