Windows 11 dresses itself in a modern shell — rounded corners, Fluent typography, and Mica blur — but beneath the polish the operating system still carries a pocket of dinosaurs: legacy tools and dialogs that have survived multiple rewrites of Windows and now look, feel, and behave like museum exhibits. What follows is a detailed, evidence-backed look at five pieces of Windows 11 that feel positively prehistoric:
Phone Dialer (dialer.exe),
Winver, the
Run dialog,
Steps Recorder (PSR.exe), and the
Control Panel. I verify history and status against official Microsoft documentation and independent reporting, analyze why these holdouts persist, and explain the practical risks and migration paths for users and IT professionals who want to modernize their workflows without breaking compatibility. rview
Windows’ greatest strength — near-obsessive backward compatibility — is also its slowest-moving liability. Microsoft’s engineering choices have long favored “don’t break customers,” which means code written in the 1990s can still sit, largely unchanged, in a 2026 desktop. That persistence has merit: administrators, OEMs, and enterprise apps rely on stable APIs and trusted utilities. But it also produces a fragmented user experience where pieces of the shell ignore modern theming, accessibility, and interaction models.
This article focuses on five built-in components that are both functionally obsolete for most users and visually jarring next to Windows 11’s modern surfaces. For each item I summarize what it does, trace a short history, verify the current state with multiple sources, assess why Microsoft hasn’t (yet) fully retired or modernized it, and recommend practical next steps. Several claims below are cross-referenced with Microsoft’s own documentation and reporting from independent outlets to ensure accuracy.
Phone Dialer — a literal relic: dialer.exe
What it is and where it came from
The Phone Dialer is a tiny Windows utility implemented as dialer.exe and traditionally used to manage modem-based telephone dialing and analog faxing. It first appeared in early Windows releases and is documented in historical Windows updates and component lists as a classic included tool; multiple community archives trace its origins to the Windows 95 era. Microsoft’s own old Knowledge Base and community archives list a “Phone Dialer applet” in updates for Windows 95, and modern scans of current Windows 10/11 images still show a signed dialer.exe present under System32 on many machines.
Why it’s archaic (and why it still shows up)
Historically, PC users tethered modems to phone lines for dial-up internet, BBS access, and faxing. A GUI dialer made calling numbers and launching modem sessions easy. Today, nearly all consumer networking is IP-based (Ethernet/Wi‑Fi/4G/5G), and modems are rare. That makes the Phone Dialer functionally irrelevant for most users. Yet the executable still exists on many Windows installs: the file is signed by Microsoft and present in System32 on up-to-date builds, which is consistent with Windows’ approach to retaining older, working binaries unless there’s a clear migration path or a strong reason to break compatibility. Practical guides and community write-ups still document how to locate and run dialer.exe on Windows 11.
Strengths, risks, and practical considerations
- Strengths: It’s tiny, self-contained, and harmless when present; it can still handle legacy modem/fax workflows for niche environments (medical, legal, or industrial setups that rely on analog transmission).
- Risks: Most users will never need it; because it’s a superficially outdated binary with a 1990s-style icon and UI, it creates user confusion and undermines the visual consistency of Windows 11. There’s also the usual caution: any rarely-used system binary can be a target for spoofing or misplacement by malware (check signatures and path before trusting).
- Practical guidance: If you need analog fax or modem dialing for business-critical hardware, retain it. For everyone else, treat it as a curiosity — there’s no production-level harm in leaving it installed, but it can safely be removed from locked down corporate images if your organization has no dial-up/fax dependencies. Make sure removal policies are tested on imaging systems and with any legacy vendor software.
Winver — “About Windows” that refuses to modernize
What Winver does
Winver (the winver.exe command) opens Windows’ About box that reports the OS edition and build number. It’s the canonical quick-check tool for diagnosing which Windows build you’re running — the equivalent of “About this Mac” on macOS, though far less feature-rich.
Why the existing Winver feels out of place
Winver remains a Win32 dialog that ignores many Windows 11 design conventions: no Mica or modern blur, no WinUI elements, no dynamic theming or full dark-mode parity in older builds. That contrast is surprisingly prominent on modern displays and with system dark themes enabled. Community projects and hobbyist replacements — including UWP/WinUI wrappers and Winver reimplementations (Modern Winver, WinverUWP, Windhawk mods) — exist precisely because Microsoft hasn’t updated winver to match the rest of the shell. Community repositories and third-party articles document these modernized replacements and show users prefer the cohesive WinUI look.
Verification and independent corroboration
- The persistent existence of legacy Winver and community projects is well-documented in multiple independent threads and GitHub projects that implement WinUI-based Winver replacements. These projects are actively maintained and demonstrate how a modern Winver could look and behave.
- Microsoft has not publicly announced a Winver redesign as of the latest documented releases, and the community work remains the de facto modern alternative for users who want parity with Windows 11 visuals.
Strengths, risks, and recommendations
- Strengths: Winver is minimal and reliable — it does one thing well (reporting build/version).
- Risks: The lack of modern theming and accessibility features is a minor but persistent polish problem; it contributes to the “friction” users feel when switching between modern and legacy dialogs.
- Recommendation: For everyday users and IT pros who want a consistent look, install a vetted Modern Winver utility from a trusted source (prefer projects with signed releases and active issue tracking). For organizations, consider scripting an About/Inventory tool that queries the same OS data (Win32_OperatingSystem class or registry keys) but surfaces it in your management UI.
The Run dialog — ancient UI, modern redesign underway
The classic Run experience
For power users, the Run box (Win+R) is reflex: type a program name or path and hit Enter. Its footprint is tiny, input-focused, and extremely fast. That minimalist design has persisted since the Windows 95 era, and the dialog has remained functionally stable even as Windows’ visual language evolved.
A long-overdue modernization: what’s changing
In preview builds and Insider flights, Microsoft has been testing a refreshed Run overlay built on WinUI/Fluent-style principles — larger, tactile, dark-mode aware, and with inline icons and recently used commands surfaced above the input box. The change was first observed in Insider builds and community screenshots shared by Windows enthusiasts; multiple outlets and preview notes confirm the work-in-progress Modern Run experience. Microsoft appears to be gating the redesign behind an opt-in toggle in Settings so the classic Run remains available while telemetry and feedback are collected.
Evidence and corroboration
- Community and forum reporting captured the modern Run surfaced in preview—screenshots demonstrate Mica blur,MRU entries, and icon feedback as you type.
- Press and community coverage (PC Gamer, BetaNews, Windows forum logs) independently reported the same experimental UI in recent builds, consistent with staged Insider preview rollouts. A Windows Forum thread also cataloged hands‑on observations and noted telemetry gating for staged rollout.
Trade-offs and recommendations
- Strengths: The modern Run helps with accessibility (larger target, dark mode support) and productivity (MRU commands, icon hints). It reduces the visual jolt between classic and modern elements.
- Risks: Power users prize the classic Run’s minimalism and perceived speed. Any added animations or heavier UI could be seen as bloat. Microsoft’s opt-in model mitigates this, but administrators should test the new overlay for keyboard-only workflows and macro/script compatibility.
- Practical steps: If you rely on Run for automation and scripting, test preview builds or wait for official rollout notes. Encourage Microsoft to retain a keyboard-first flow and to document any behavior changes (e.g., removal of the Browse button) that affect scripted workflows.
Steps Recorder (PSR.exe) — deprecated and being retired
What Steps Recorder does
Steps Recorder (PSR.exe, historically “Problem Steps Recorder”) records user interactions as a sequence of screenshots, annotating clicks and keystrokes to produce a step-by-step package useful for troubleshooting. It was introduced as a shipping component in Windows 7 and quickly became a handy low-friction diagnostic aid for helpdesk and support workflows. Microsoft’s developer documentation describes PSR’s purpose and platform support since its introduction.
Microsoft’s decision: deprecation and recommended replacements
Microsoft formally listed Steps Recorder among deprecated Windows features. Official Microsoft documentation notes that
Steps Recorder is no longer being updated and will be removed in a future release of Windows, and specifically recommends other tools for screen capture or recording: the
Snipping Tool,
Xbox Game Bar, or
Microsoft Clipchamp. Numerous news outlets and Windows-focused sites covered Microsoft’s deprecation announcement and the appearance of a “phasing out” banner inside Steps Recorder instructing users about alternatives.
Why Microsoft removed it — and the consequences
- Rationale: Overlap with more powerful inbox tools that provide richer video capture and editing workflows (Snipping Tool now supports recording, Xbox Game Bar targets gameplay with optimized performance, Clipchamp offers editing). Maintaining a specialized, screenshot-based step recorder no longer aligned with Microsoft’s consolidation strategy.
- Consequences: Steps Recorder produced annotated steps in a unique format (MHT inside a zipped archive) that some support teams used as a lightweight repro method. Replacing this with video-based workflows changes the output type and can lose step granularity (unless you annotate manually). Power users who relied on PSR’s compact, annotated output may find the suggested replacements lacking.
- Practical mitigation: If your support workflows depend on PSR’s output format, export existing logs, or rework diagnostics to use Snipping Tool’s capture features together with the clipboard/history and PowerToys (for click highlighting). Organizations should document the new recommended workflows and update internal KB articles; for scripted or automated capture, consider third-party lightweight tools that preserve step-level metadata.
Control Panel — the emaciated settings experience
The slow migration to Settings
The Control Panel is the grandparent of Windows’ configuration surfaces. Microsoft introduced the modern Settings app as a replacement path more than a decade ago, and since Windows 8 the company has been incrementally migrating functionality. In Windows 11, many controls have moved to Settings, but critical applets, diagnostics, and advanced options still live in Control Panel. Microsoft has repeatedly clarified that settings are being “migrated” rather than the Control Panel being immediately removed; the company’s documentation and Q&A responses emphasize a gradual transition with no fixed removal date. Independent reporting corroborates this measured approach.
Why the Control Panel still matters — and why it’s a UX problem
- Why it matters: Some advanced systemnagement consoles, BitLocker options in certain pedigrees, some installers) still route through Control Panel applets. IT administrators and OEMs depend on those stable applets for diagnostics and configuration.
- Why it’s a problem: Control Panel’s UI is inconsistent with Windows 11: mixed iconography, no universal dark-mode coverage, inconsistent redirections (some applets route you to Settings, others do not), and poor touch support on tablets and convertibles. That inconsistency fragments the user experience and raises discoverability problems for less technical users. Recent Windows Insider releases continue to migrate discrete Control Panel pages into Settings, but the overall transition remains a multi-year project.
Risks and recommended actions
- Strengths: Control Panel remains a reliable, familiar surface for advanced configuration, and it’s unlikely to disappear overnight because numerous enterprise scenarios still rely on it.
- Risks: Maintaining two separate settings surfaces increases user confusion and adds technical debt for Microsoft and IT teams. Administrators need to maintain dual knowledge of where settings live and test group policies against both interfaces.
- Recommendations:
- Treat Settings as the canonical UI for user-focused tasks and Control Panel as an advanced compatibility surface.
- Update internal support documentation and training to show both paths to the same setting.
- Use Powershell/Group Policy and modern management tooling (Intune, ConfigMgr) to centralize settings where possible and avoid user-facing drift between Settings and Control Panel.
Practical checklist for admins and power users
If you care about visual consistency, accessibility, or removing legacy baggage from images and builds, here’s a compact action list:
- Inventory: Use scripts to catalog legacy binaries (dialer.exe, psr.exe, winver.exe) across images and endpoints.
- Dependency audit: Confirm no vendor drivers or specialized hardware require the legacy utilities (for example, medical fax modems that use analog lines).
- Migrate or replace:
- Replace PSR-based workflows with Snipping Tool/Xbox Game Bar + documentation templates, or adopt a supported third-party tool that preserves step metadata.
- Use Winver alternatives if visual parity matters; prefer signed releases from reputable maintainers.
- Test staged UI changes (e.g., Modern Run) in a pilot group before broad rollout; watch for keyboard-only regressions.
- Update support documentation to reflect Microsoft’s deprecation timeline and recommended replacements; incorporate screenshots and sample flows for Snipping Tool video capture and Xbox Game Bar.
Conclusion — technical debt, usability debt, and Microsoft’s balancing act
Windows’ backwards compatibility is a virtue that long outlived some of the artifacts it preserves. The five relics examined here illustrate a recurring tension: preserving working behavior for enterprise scenarios versus providing a coherent, modern UX for everyday users. Microsoft’s approach — gradual migration, deprecation notices, and incremental modernizations (like the Run redesign) — reflects an engineering trade-off that prioritizes minimal disruption.
From a user and IT perspective, the pragmatic path is simple: acknowledge which legacy components you genuinely need, migrate workflows where practical, and test the modern alternatives Microsoft recommends for removal scenarios (for example, replacing Steps Recorder workflows with Snipping Tool or Clipchamp pipelines). For the things that remain — dialer.exe’s tiny icon, Winver’s old dialog, Control Panel’s mismatched tiles — treat them as legacy conveniences that will stick around until Microsoft finds safe, compatible replacements. Along the way, expect more small showers of modernization (Run, legacy dialog dark-mode parity) rather than sudden, large removals.
If you want a one-page checklist or a PowerShell template to inventory these legacy components across your estate, I can prepare and vet a script that lists dialer.exe, psr.exe, winver.exe, and key Control Panel applets and outputs a report you can use with your deployment tooling.
Source: Pocket-lint
5 outdated parts of Windows 11 so old they belong in a museum