Microsoft’s Canary-channel release of Windows 11 Insider Preview Build 27928 lands with a pair of understated but strategically loud changes: six legacy Control Panel modules covering time, date, and regional settings are now found in the modern Settings app, and a separate Copilot update brings semantic file search to Copilot+ PCs along with a redesigned home experience. The moves are incremental, but together they accelerate two long-running Microsoft objectives—dismantling the decades-old Control Panel and embedding AI into everyday workflows.

Build 27928 was pushed to the Canary Channel on August 20, 2025. It is a compact release focused on housekeeping and UX consolidation. The build itself is not packed with flashy features; instead, it continues the painstaking migration that has been underway for over a decade. The significance lies in the specific settings that moved and the timing: with Windows 10 end-of-support looming in October 2025, Microsoft wants users migrating to Windows 11 to land in a unified configuration surface, not a bifurcated maze of Control Panel applets and Settings pages.

What moved: clocks, time servers, and regional formats

The official changelog lists six items that now live primarily—and in some cases exclusively—under Settings > Time & language.

  • Add and manage additional clocks: Users can now add up to two extra clocks that appear in the Notification Center clock flyout and the taskbar tooltip. Previously, this required a trip to Control Panel’s Date and Time applet.
  • Change the time server (NTP): The Network Time Protocol server selection has been moved to Settings > Time & language > Date & time, tucked under “Additional settings.” Power users who sync their system clock to a custom NTP source no longer need to open the legacy dialog.
  • Date/time formatting: Custom regional formatting—including AM/PM symbols—is relocated from Language & region to the Date & time section. It sits alongside the existing regional calendar and first-day-of-week pickers.
  • Number and currency formats: Regional formatting for numbers, currency, and measurement systems is now found in Settings > Time & language > Language & region, under the Region dropdown. The old per-format customization dialog remains accessible but is no longer the primary path.
  • Unicode UTF-8 toggle: A user-facing switch to enable UTF-8 for worldwide language support is exposed under Language & region. This previously required fiddling in the legacy Region settings or the system locale.
  • Copy language/region to system and new user accounts: An admin option to copy the current user’s language and region settings to the welcome screen, system accounts, and newly created profiles is now available in Settings. This simplifies provisioning for multi-user devices and kiosks.

These are not headline-grabbing features. They are practical parity moves that reduce the friction of bouncing between two UIs to accomplish common tasks. Every one of these options has a Control Panel equivalent that Microsoft intends to deprecate—not immediately, but by making the Settings path the canonical entry point. The company’s incremental approach avoids the catastrophic loss of niche controls that would anger power users and admins.

Why these moves matter now

Consolidating date, time, and language controls into Settings delivers three immediate benefits:

  • Discoverability: Casual users expect to find everything in one place. Sending them to Control Panel for extra clocks or formatting undermines that expectation. Now, a single search in the Start menu for “clocks” or “UTF-8” will lead to the right page.
  • Accessibility and consistency: The modern Settings app inherits Windows 11’s theming, high-DPI scaling, and assistive technology support. Control Panel applets, built on older frameworks, often lag in accessibility and can appear broken under dark mode.
  • Documentation simplicity: Microsoft’s support articles and third-party help guides can now point to a single Settings path rather than listing alternatives. Over time, this reduces help-desk tickets and confusion.

Behind the scenes, the Settings app is built on modern telemetry hooks and feature-gating infrastructure that makes iterative improvements and A/B testing easier. The legacy Control Panel, by contrast, is a collection of COM-based applets that are difficult to maintain. Microsoft’s migration strategy is less about killing the old UI overnight and more about starving it of relevance.

Copilot gets semantic search and a new home

While the settings migration is the hardware of Build 27928, the software is a separate Copilot app update that began rolling out to Insiders at the same time. The update introduces semantic file search to Copilot+ PCs and a redesigned Copilot home that surfaces recent apps, files, and conversations.

Semantic search lets users query their local files using natural language. Instead of typing a filename or date, you can ask Copilot to “find the file with the chicken tostada recipe” or “find images of bridges at sunset on my PC.” The feature works across multiple file types—.docx, .pdf, .xlsx, .csv, .json, .txt, and common image formats—and relies on the neural processing unit (NPU) inside Copilot+ PCs to perform on-device indexing and inference.

Key details of the Copilot update:

  • Hardware gate: Semantic search requires a Copilot+ PC with the necessary NPU hardware. It builds on the improved Windows Search semantic indexing preview that Microsoft shipped to Snapdragon-based Copilot+ devices earlier in 2025. Intel and AMD Copilot+ machines are expected to follow.
  • Permission model: The Copilot app shows files from the user’s Recent list but does not automatically scan or upload the entire disk. Files are only processed when the user explicitly attaches them to a conversation or grants Copilot access. A Permission settings pane inside the Copilot app lets users control what the assistant can see.
  • New home experience: The redesigned Copilot home surfaces three sections: recent apps (clicking one starts a Vision session where Copilot guides you through the app), recent files, and recent conversations. It is meant to turn Copilot into a contextual launcher and assistant, not just a chat window.
  • Rollout mechanism: The update is delivered through the Microsoft Store and is rolling out gradually to Insiders across all channels, not just Canary. Microsoft describes it as a “staged rollout” to monitor quality and gather feedback.

External reporting confirms the strategy. The Verge noted that the AI-powered file search “takes things a step further by allowing you to describe what you’re looking for,” while PCWorld highlighted the feature’s potential to “save time sifting through forgotten filenames.” Microsoft’s own blog post emphasizes on-device processing and user permission, framing Copilot as a privacy-conscious assistant.

Privacy and permissions: the messaging and the gaps

Microsoft has been careful to present the Copilot file search as permission-bound and locally anchored. The official messaging includes several reassurances:

  • Copilot only accesses files from the Recent list and only uploads or processes contents when a user explicitly attaches a file.
  • Users can configure permissions inside Copilot Settings, including the ability to revoke access or remove files from the Recent list.
  • The semantic search engine runs locally on the NPU, minimizing data that leaves the device. However, for cloud-dependent Copilot experiences, file analysis may involve uploading to Microsoft servers; this is gated by explicit user action.

These promises are important, but they are not a substitute for enterprise-grade governance. IT administrators will need to answer hard questions: How does Copilot’s file listing interact with data loss prevention (DLP) policies? What happens when a managed user attaches a corporate document containing sensitive data? Can administrators centrally enforce Copilot permissions via Group Policy or MDM? Microsoft has not yet provided detailed enterprise guidance, but the fact that controls live inside the Copilot app suggests manageable policy pathways will emerge.

Enterprise and power-user considerations

The dual push—settings consolidation and AI feature expansion—creates both opportunities and risks for organizations.

Opportunities

  • Streamlined support: A unified Settings app reduces the number of support articles and training materials needed for help desks. Users can be directed to a single location for clock, format, and language changes.
  • Modern management hooks: Settings items are increasingly backed by MDM policies and PowerShell cmdlets, making remote configuration easier. The Copilot permission model could become manageable through Intune or GPO once templates are published.
  • AI-powered productivity: Semantic search promises genuine time savings for knowledge workers who struggle with file retrieval. Summarization of attached documents could reduce the chore of scanning lengthy PDFs or spreadsheets.

Risks and friction points

  • Feature parity gaps: Some legacy Control Panel options—advanced regional overrides, custom list separators, or obscure time zone tweaks—may not yet have Settings equivalents. Organizations that rely on these must test thoroughly before retiring scripts.
  • Automation breakage: Scripts and help-desk workflows that target Control Panel applets or specific registry keys may need reworking. For example, a PowerShell script that opens the legacy Date and Time dialog to adjust the NTP server will no longer work.
  • Group Policy compatibility: Microsoft has historically maintained backward-compatible policy pathways, but each migration step must be validated. Admins should verify that existing GPOs for regional settings or language preferences apply correctly to the new Settings paths.
  • Copilot governance blind spots: Without centralized policy controls, Copilot could become a shadow-IT risk. Files attached to Copilot conversations might violate data sovereignty or confidentiality rules. Until DLP integration is confirmed, enterprises should tread carefully.

Canary Channel builds are experimental and subject to rollback. Build 27928 itself included a temporary rollback of a redesigned battery icon due to visual regressions—a reminder that even small UI changes can trigger edge-case problems. Enterprises should use Canary builds as early warning systems to identify gaps, not as deployment vehicles.

What to expect next

The trajectory is clear. Expect a steady drip of Control Panel features moving into Settings over the next several months. Priority areas likely include more regional and language parity, device and hardware pages (such as printer management), and enterprise-facing cards inside Settings that surface policy compliance status.

On the Copilot front, broader hardware support is the immediate milestone. Once semantic search works reliably on Intel- and AMD-based Copilot+ PCs, Microsoft will have a larger install base to justify deeper integration—such as search across cloud storage providers or integration with Microsoft 365 Copilot. Administrative controls and DLP integration will be critical for enterprise adoption, so watch for MDM templates and Group Policy updates in Insiders builds.

Public response will shape the final design. Microsoft’s Canary model is iterative: features land in limited form, telemetry pours in, and the company refines or rolls back. The battery icon snapback is a healthy example of this feedback loop. Users and admins who want to influence the direction should file feedback via the Feedback Hub.

Practical advice for now

  • For Insiders: Keep a dedicated test machine. Use Build 27928 to verify that your common clock, format, and language workflows still function. Check whether tools that relied on legacy Control Panel entry points are broken.
  • For everyday users: You no longer need to remember multiple locations. Start in Settings > Time & language for anything related to clocks, dates, or regions. The Control Panel still exists, but it is no longer the first stop.
  • For IT admins: Begin auditing your environment for dependencies on legacy dialogs. Test Copilot’s file attachment behavior on a managed device with a representative DLP policy. Monitor Microsoft’s Insider blog and Group Policy reference pages for updates. Do not assume that Copilot respects existing file-level policies out of the box.

Build 27928 is quiet infrastructure work that signals a louder future. The settings consolidation shrinks the Control Panel’s footprint one practical chunk at a time, while Copilot’s semantic search hints at a desktop where AI handles the grunt work of finding and summarizing files. Both threads will continue to intertwine as Windows 11 evolves into a more cohesive, AI-augmented operating system.