Microsoft's slow-motion demolition of the classic Control Panel took another quiet step forward this week. Windows 11 Insider Preview Build 27928, released to the Canary Channel on August 20, 2025, ported several more time and language controls into the modern Settings app—moving additional clocks, NTP server selection, date and time formatting, and regional options out of the legacy panel. The changes are small individually, but they chip away at a fragmentation that has irritated users and IT administrators for over a decade.

The moves are not about new features. Every item being relocated already existed in Control Panel. Instead, they close parity gaps that forced users to flip between two different configuration surfaces for logically related tasks. "Why do I have to go to PC settings to forget a network and Control Panel to change IP settings? Can't this all be done from a single place?" That frustration, voiced in community discussions and echoed in a recent Verge report, captures the real-world friction Microsoft is trying to erase, one applet at a time.

A Migration a Decade in the Making

The Settings app first appeared in Windows 8 as a touch-friendly alternative to Control Panel, but it was largely a skeleton. Over successive Windows 10 and Windows 11 releases, Microsoft has steadily built out its capabilities, often redirecting Control Panel links to equivalent Settings pages. The company has never ripped everything out in one go. Instead, it takes an incremental approach—adding parity, testing telemetry, and only then deprecating the old pathway.

This cautious method has left Windows with a bimodal configuration experience. As recently as 2024, Microsoft's own support documentation still listed dozens of Control Panel applets with no Settings equivalent, and users frequently complained about hunting for options split across two interfaces. Build 27928 is the latest example of that long-running consolidation program, and it focuses squarely on the Time & Language category.

What Changed in Build 27928

According to Microsoft's official release notes, the following controls have been moved from Control Panel to Settings in this Canary build:

  • Additional clocks: Users can now add and manage extra clocks directly from Settings > Time & language > Date & time. These additional clocks appear in the Notification Center and in the taskbar clock tooltip—exactly matching the behavior previously configured in Control Panel.
  • Time server (NTP) selection: The ability to choose which Internet time server to synchronize with is now exposed under Settings > Time & language > Date & time > Additional settings.
  • Date/time formatting: Controls to change the AM/PM symbol, long date, short date, and time formats have been moved to Settings > Time & language > Date & time. Previously these lived under Language & region.
  • Number and currency formats: Regional formatting options for numbers, currency, and measurement systems are now in Settings > Time & language > Language & region > Region.
  • Unicode UTF‑8 toggle: A switch to enable “Unicode UTF‑8 for worldwide language support” (the global UTF‑8 option) appears under Settings > Time & language > Language & region > Language.
  • Copy language and region settings: The ability to copy the current user's language and region settings to the welcome screen, system account, and new user accounts now sits in Settings > Time & language > Language & region > Additional settings.

Independent tech outlets such as Neowin and Pureinfotech quickly confirmed the changelog, noting that these are parity moves, not brand-new capabilities. They also remind readers that the Canary Channel is an early development branch; features may change or ship months before reaching the general public.

Why These Moves Matter

On their own, adding a toggle for UTF‑8 or moving an AM/PM symbol editor into Settings looks trivial. In aggregate, however, these changes deliver three strategic outcomes:

  1. Improved discoverability and consistency – Grouping all time-and-language controls in one place reduces cognitive overhead. A user who wants to adjust the clock, change date formats, and set the region no longer needs to guess which UI hosts each setting.
  2. Modern UI parity and accessibility – The Settings app uses the latest UWP/WinUI accessibility frameworks and input models. Migrating features allows Microsoft to apply consistent accessibility practices and collect telemetry to refine the experience, especially for international users who frequently touch language and formatting.
  3. Simpler lifecycle and maintenance – Maintaining one configuration surface is easier than supporting two parallel systems that must coexist. Over time, this reduces technical debt and improves update velocity.

Yet these benefits come with trade-offs. Settings is not yet a perfect one‑for‑one replacement for every Control Panel function. Some advanced options that required deep system hooks or legacy COM‑based dialogs are slow or difficult to port. Microsoft's method—small, verifiable parity moves—minimizes regression risk but extends the timeline before Control Panel can be fully deprecated.

The Technical Reality: Redirects, Parity Gaps, and Persistent Legacy Applets

History shows Microsoft will often redirect Control Panel applets to Settings equivalents rather than keep both accessible. For example, in previous Windows 10 releases, the System Control Panel applet began redirecting to Settings > System > About. Over time, the company has blocked or redirected other applets, sometimes breaking scripts that relied on the old control.exe launch paths.

This piecemeal redirection matters for administrators and power users who depend on Control Panel GUIDs, .cpl files, or automation scripts. When an applet is redirected, some workflows break. Tools that call control timedate.cpl or a specific GUID may suddenly land in a Settings page that doesn't accept the same command-line arguments. Sysadmin forums are full of threads documenting these transition pains, urging Microsoft to either keep dual access or provide documented APIs for automation parity.

Even when a Control Panel page appears to vanish, an equivalent setting is usually somewhere in Settings—but not always in the same format or with identical advanced options. For instance, the old Date and Time dialog offered a handy “Internet Time” tab for NTP configuration; that functionality now exists in Settings, but the UI is different, and the path to reach it is not obvious to someone accustomed to the classic panel.

Usability and Stability: Settings Improves, but Friction Remains

Build 27928 also includes a fix for a Settings crash when adding a security key under Settings > Accounts > Sign‑in options. That fix reflects the ongoing reality: as more functionality migrates to Settings, stability and UX polish are essential. Microsoft's release notes list numerous other fixes and known issues for this Canary flight, including potential DWM crashes and problems with Storage > Temporary files scanning. These known issues underscore the Canary Channel's role as a testing ground—useful signals for IT pros but not always safe for production deployment.

Independent reporters and forum users have repeatedly noted that the Settings app still has edge cases where functionality is incomplete, elevation prompts misbehave, or advanced controls are missing compared with Control Panel. For example, some network settings still require a detour into the old Network and Sharing Center, and power users often rely on Control Panel for device manager tasks that lack a modern equivalent.

What This Means for Administrators, Enterprises, and Power Users

Organizations that manage Windows fleets must treat the Settings‑Control Panel migration as operational risk to manage, not a cosmetic change. Practical consequences and recommended steps include:

  • Inventory Control Panel dependencies – Audit scripts, Group Policy templates, and helpdesk runbooks for explicit calls to Control Panel applets (control.exe, shell:::{GUID}, or .cpl files). Note which applets have Settings equivalents and where they are located. Some applets now redirect; others still require legacy access.
  • Test automation and elevation flows – Validate PowerShell, management tools, and scheduled tasks that interact with system settings. Settings pages use different elevation models than some Control Panel dialogs; non‑admin prompts may behave differently.
  • Update internal documentation and user guidance – Helpdesk knowledge bases should map old Control Panel locations to new Settings pages. Include screenshots and exact navigation paths (for example: Settings > Time & language > Date & time > Additional settings).
  • Use Insider builds for early detection – Run Canary/Beta Insider builds in a staged test pool to spot breaking changes before they reach broad deployment. Insider release notes provide advance warning of parity moves and known issues.
  • Plan for long‑term transition – Avoid building permanent operational dependencies on Control Panel applets. Where possible, adopt supported APIs, Group Policy, and MDM configuration profiles that are version‑resilient.

Strengths of Microsoft's Approach

  • Cautious, incremental migration reduces large‑scale regressions. Moving small feature sets lets Microsoft validate UX and telemetry before wider rollouts. This lowers the likelihood of a catastrophic one‑time removal that breaks admin tooling at scale.
  • Consolidating discoverability helps everyday users. For non‑technical users, a single, logically organized Settings app is easier to navigate than hunting through a Control Panel that still retains legacy groupings and less intuitive labels.
  • Opportunity to modernize accessibility and telemetry. Porting to the Settings app allows Microsoft to apply modern accessibility practices and gather better usage telemetry to prioritize further improvements.

Risks and Downsides

  • Automation and legacy tooling breakage. Administrators who depend on .cpl GUIDs or Control Panel automation must update scripts and workflows. The pace of change—slow from a headline perspective but relentless in practice—raises the maintenance burden for enterprise IT teams.
  • Feature and parity gaps remain. Some advanced settings and diagnostic links historically present in Control Panel are either absent in Settings or reachable only through complex redirect sequences, impacting troubleshooting workflows.
  • Potential for inconsistent UX and regressions. The Settings app and Control Panel have different models for elevation, modal dialogs, and layout. Incomplete ports can introduce confusing user flows and unexpected behavior in privileged operations. Microsoft's own release notes for Canary builds list stability issues—a reminder that this is active development.
  • Change management fatigue. Long, incremental migrations can be more disruptive than a single planned cutover: users and admins must adapt repeatedly to small differences rather than a single coordinated migration plan.

Practical Workarounds and Short‑Term Tactics

  • Create a mapping document that lists Control Panel applets and the corresponding Settings paths. Start with high‑value items like Date & time, Region, Network, and Programs & Features.
  • Use direct shell URIs for Settings pages in scripts and shortcuts (for example, ms-settings:time-date). These are more future‑resilient than control.exe calls. Verify ms‑settings URIs in your environment as their parameters can vary by build.
  • For tasks that currently lack Settings parity, maintain small helper scripts that use legacy GUIDs but include detection logic to switch to Settings URIs when available.
  • Train helpdesk staff to search Settings and use the Feedback Hub when Settings functionality is missing or regressions are discovered; Microsoft monitors Insider feedback and sometimes responds to volume.

Timeline and Prognosis: Control Panel's Near‑Term Future

Control Panel will not disappear overnight. Microsoft's Canary Channel release notes explicitly describe these moves as part of an ongoing effort and warn that Canary builds represent early platform changes that may not map to any specific Windows release. Past behavior indicates Microsoft will continue to migrate items piecemeal until Settings achieves functional parity for the majority of common tasks.

This migration has been underway since Windows 8 and accelerated under Windows 10 and 11, yet legacy pieces linger. The result: Control Panel is likely to persist—in some form—across several future OS releases even as its role steadily shrinks. Where Microsoft will draw the final line, and on what schedule, remains unclear. The company historically avoids sudden removals and tends to prefer a long transition with fallback compatibility. That means enterprise planners should assume Control Panel will still exist for the next major Windows releases, but with an increasing number of redirects and missing applets over time.

Final Analysis: Measured Progress, Persistent Friction

Build 27928 demonstrates Microsoft's pragmatic, risk‑averse approach to migrating legacy settings into the modern Settings app. The moves in this flight are small, user‑facing parity adjustments that reduce context switching for time, language, and region settings—and they do offer tangible usability improvements.

At the same time, the pace and piecemeal nature of the migration create cumulative operational friction. Automation breakage, UX inconsistencies, and the need for repeated documentation updates fall disproportionally on IT and power‑user communities. Microsoft's cautious method reduces single‑release risk, but it increases the total number of change events administrators must track.

For most individual users, the changes will be an invisible improvement: a single place to manage clocks, formats, and language settings. For enterprises and power users, these releases are signals to audit dependencies, update automation, and increase testing cadence on Insider previews. The practical advice is to treat the Settings‑Control Panel migration as an ongoing project: inventory reliance on legacy applets, establish mapping to new Settings targets, and embrace ms‑settings URIs and supported management APIs where possible.

Microsoft is not rushing the Control Panel out the door; it's methodically shrinking its role. That strategy may be frustrating for some, reassuring for others, and ultimately sensible for a platform that must balance backward compatibility with modernization. The Control Panel is not dead yet—but every Insider flight like Build 27928 narrows the range of reasons to keep using it.