Microsoft has packed six long-standing Control Panel features into the Settings app with the release of Windows 11 Insider Preview Build 27928 to the Canary channel. The August 20 flight relocates additional clocks, time server selection, date and time formatting controls, number and currency formats, a Unicode UTF-8 toggle, and the ability to copy language and region settings — all now accessible under the Time & Language and Language & Region sections of Settings. The move marks another deliberate step in the decade-plus effort to retire the legacy Control Panel and establish Settings as the single, discoverable configuration surface for Windows users.

Build 27928 is the latest in a series of incremental migrations that have accelerated in recent Insider flights. For users who have grown tired of bouncing between two separate UIs to adjust locale- or time-related preferences, the consolidation offers immediate relief. For IT departments and power users, it signals the need to review automation scripts and internal documentation that rely on Control Panel GUIDs. The Canary release also temporarily disabled a battery iconography experiment, underscoring the testbed nature of the channel.

The Six Moves at a Glance

The official release notes for Build 27928 confirm the following settings have been ported into the modern Settings app:

  • Additional clocks: Users can now add and manage up to two extra clocks from Settings > Time & language > Date & time. These appear in Notification Center and the taskbar clock tooltip, just as they did in Control Panel.
  • Time server (NTP) selection: The option to change which Internet time server Windows uses is now exposed under Additional settings on the Date & time page.
  • Date/time formatting: Controls to customize calendar formats, including the ability to alter AM/PM symbols, have migrated from Language & region to Date & time.
  • Number and currency formats: Locale-specific numeric and monetary formatting now lives at Settings > Time & language > Language & region > Region.
  • Unicode UTF-8 toggle: A switch to enable worldwide language support can be found under Settings > Time & language > Language & region > Language.
  • Copy language and region settings: The option to propagate current language and region configuration to the welcome screen, system account, and new user accounts is now located in Additional settings under Language & region.

These moves are practical, user-facing items that close small but meaningful gaps. They represent the type of functionality that general users need on occasion — setting a second clock for a remote team, adjusting the system’s NTP source, or tweaking how numbers appear — and previously required a detour into the dated Control Panel interface.

Why the Migration Matters

On the surface, these are housekeeping changes. Beneath the hood, they serve three strategic goals that Microsoft has been pursuing since Windows 8’s “PC Settings” app.

Discoverability is the most immediate benefit. The Settings app is built around a search-centric design that helps non-technical users locate options without memorizing legacy applet names. Consolidating clock, locale, and formatting options into a single searchable surface reduces the cognitive load of hunting through two separate environments. A user who types “AM/PM” into Settings search will now land directly on the relevant page, whereas before they would have been stuck.

Consistency follows naturally. Grouping logically related controls under Time & language and Language & region creates a single mental model for configuration. Help desk documentation can reference one UI path instead of directing users to different tools depending on how old the setting is. That uniformity simplifies training and support across organizations, especially as enterprises prepare for Windows 10’s end of mainstream support on October 14, 2025.

Product hygiene is the less visible but equally important driver. Maintaining two overlapping control surfaces increases engineering cost and presents UI debt. Each incremental parity move lets Microsoft eventually retire redundant Control Panel applets while testing the new UX in Insider channels. In Build 27928, the same flight temporarily rolled back a revised battery icon design, a reminder that Canary builds are a live laboratory where features can be tuned or pulled back quickly based on feedback and telemetry.

A Win for Everyday Users

For the majority of Windows users, the relocation is a quality-of-life improvement. Instead of opening Control Panel to add a clock for a colleague in another time zone, they can stay inside Settings. The behavior of extra clocks in Notification Center and the taskbar tooltip remains unchanged, so the transition is seamless.

Non-technical users gain a cleaner flow: open Settings, type “time,” and see date/time options alongside formatting controls. The previously fragmented experience of adjusting AM/PM symbols or switching to a 24-hour format required a separate trip to Language & region; now it all lives together. Similarly, enabling UTF-8 support for worldwide compatibility no longer demands a hunt through administrative tools.

Power Users and Admins Face Transitional Friction

The consolidation is not without pain. Power users and IT administrators who have relied on Control Panel GUIDs, direct applet shortcuts, or command-line invocations like control.exe timedate.cpl will need to adapt their workflows. Scripts that automate system provisioning or image deployment may break silently if they hardcode Control Panel paths that no longer open the same dialog.

Certain legacy management tools, Group Policy paths, and enterprise deployment scripts still reference Control Panel GUIDs. While Microsoft has not removed the underlying applets, the steady migration signals that such dependencies should be treated as deprecated. Organizations must audit their automation decks and, where possible, pivot to supported PowerShell cmdlets, WMI or CIM interfaces, or documented registry keys.

Community reporting has flagged that other settings — notably keyboard and accessibility options — have begun appearing as hidden features in Dev and Beta builds. That pattern suggests Microsoft may ship some Settings integrations behind feature flags before a public rollout, adding another layer of complexity for IT teams that need to stay ahead of changes.

Enterprise Planning: What to Do Now

Build 27928 does not represent an immediate break, but it does deliver a clear signal: the Settings app is the future canonical location for system configuration. Enterprises should begin a structured review by taking four steps.

  • Audit automation: Search PowerShell scripts, imaging tasks, and deployment playbooks for references to Control Panel GUIDs or control.exe calls. Replace them with Settings-equivalent modules or supported APIs. Where parity is incomplete, legacy interfaces may persist but should be flagged for future updates.
  • Update documentation: Replace Control Panel path references in internal knowledge bases with Settings equivalents and tag documents with the Windows build versions where they apply. This prevents confusion for help desk staff and end users.
  • Leverage policy equivalents: Many enterprise controls are now available through MDM/Intune policies or Group Policy Administrative Templates that target Settings-based endpoints. Verify whether policy equivalents exist for the moved time and language settings and update ADMX templates or CSPs as needed.
  • Train support staff: Equip service desk teams with a quick-reference sheet linking common configuration tasks to their new Settings locations. This reduces ticket escalations and ensures consistent guidance.

Because the Canary channel is a testbed, organizations should not deploy it broadly. Staged testing rings allow validation that third-party tools and management scripts behave after migration. Microsoft’s temporary rollback of the battery icon experiment in 27928 illustrates that Canary changes can be reverted, but relying on that is risky for production environments.

Risks and Unknowns

Microsoft’s micro-migration strategy is conservative, but several uncertainties warrant attention.

  • Partial parity: Not every feature will ported at once. Some advanced or deeply technical settings may remain in Control Panel indefinitely because they depend on legacy APIs. This creates a long tail of fragmented configuration surfaces.
  • Documentation drift: If official guidance lags behind the actual UI changes, users and help desks will struggle to locate specific options. Third-party support articles may become outdated, compounding confusion.
  • Silent automation breakage: Scripts that rely on Control Panel paths may fail without obvious errors until a critical workflow is impacted. Proactive inventory and testing are essential.
  • Accessibility tradeoffs: Power users often prefer Control Panel’s direct icon lists over Settings’ search-driven layout. Microsoft must ensure that depth isn’t sacrificed for discoverability, or risk alienating administrative users who need instant access to complex configurations.
  • Unclear deprecation timeline: Microsoft has publicly stated that Control Panel isn’t being removed imminently. However, the steady migration increases pressure to finalize a longer-term plan. Assuming immediate removal would be a mistake, but treating Control Panel as legacy and planning for eventual retirement of overlapping features is prudent.

Users and administrators can find the relocated items in Build 27928 and later under these paths:

  • Additional clocks, NTP server, date/time formatting: Settings > Time & language > Date & time
  • Number and currency formats: Settings > Time & language > Language & region > Region
  • Unicode UTF-8 toggle: Settings > Time & language > Language & region > Language
  • Copy language and region settings: Settings > Time & language > Language & region > Additional settings

If a setting does not appear immediately, using the Settings search box with keywords like “additional clocks,” “time server,” “AM/PM,” or “UTF-8” should surface the relevant page. When Settings lacks an option, the classic Control Panel (accessible via control.exe or direct applet GUIDs) remains the fallback.

Broader Context and Verified Claims

The moves in Build 27928 are part of a migration that began over a decade ago and has gained momentum in Windows 11. Independent reporting from Windows news outlets and community trackers confirms the same list of relocated items and places them within the larger timeline of Control Panel consolidation. Microsoft’s official Windows Insider Blog post for Build 27928, published August 20, 2025, is the authoritative source for these placements.

Windows 10’s end of mainstream support on October 14, 2025, adds urgency for enterprises already planning upgrades. Microsoft is incentivized to ensure that users migrating to Windows 11 encounter a polished, unified configuration experience. The Extended Security Update (ESU) program provides a bridge for organizations that need more time, but the message is clear: Settings is the way forward.

Cross-checking confirms that no specific dates for final Control Panel removal have been announced. Claims about eventual retirement remain projections based on observable trends rather than official timelines. For compliance or procurement decisions, organizations should rely on Microsoft’s published documentation and licensing guidance.

The Road Ahead

Build 27928 is a milestone in the ongoing evolution of Windows configuration. By moving six everyday controls into Settings, Microsoft delivers immediate usability gains while reinforcing its commitment to a single, modern configuration surface. For everyday users, it means fewer clicks and simpler search flows. For IT professionals, it is a prompt to audit scripts, update documentation, and prepare for a future where Settings is the default destination for system tuning.

The migration will continue, and the next phases will likely tackle deeper administrative controls and more complex legacy applets. How Microsoft communicates deprecation timelines and provides policy equivalents will determine whether this long transition concludes smoothly or leaves lingering fragmentation. For now, the path is incremental but unmistakable: Settings is no longer just an alternative — it is the primary interface for configuring Windows.