Microsoft has temporarily disabled the updated battery iconography in its latest Windows 11 Canary Channel build, reverting to the previous icon design while engineers refine the feature based on telemetry and usability data. Released on August 20, 2025, Insider Preview Build 27928 also pushes forward the long-running program to relocate legacy Control Panel controls into the modern Settings app, moving a cluster of time, date, language, and regional settings that until now required hopping between two separate configuration surfaces.

For the roughly 15 million Windows Insiders enrolled in the Canary Channel, Build 27928 is a compact but telling flight — one that omits splashy new features in favor of measured iteration and a set of targeted reliability fixes. The build number itself places it squarely in the earliest testing ring, where code churn is high, experiments can appear and vanish without warning, and stability is explicitly not guaranteed. The two most consequential changes — the battery icon rollback and the Settings migration — each illuminate a different aspect of how Microsoft is developing Windows 11 in 2025: rapid, telemetry-driven UI experimentation on one hand, and a steady, multi-year effort to modernize the operating system’s configuration guts on the other.

Battery Icon Experiment Paused: What Happened and Why It Matters

Earlier Canary builds had introduced an updated battery icon system that used color states (green, yellow, red) and offered an optional taskbar battery percentage. It was a small change with outsized practical impact — laptop users could gauge remaining battery life at a glance without hovering over the icon or opening the battery flyout. The design also included subtle animation refinements and was meant to align with Windows 11’s broader push toward more informative, glanceable status indicators.

Build 27928 explicitly disables that experiment. Microsoft’s release notes are blunt: “The updated battery icons … are temporarily disabled in this build.” Devices that had the new icons are rolled back to the classic white battery indicator. The company has not published a specific list of bugs that prompted the move, but the decision almost certainly stems from aggregated telemetry. Common culprits in such rollbacks include rendering glitches on certain display scaling factors, inconsistent colors in high-contrast or dark modes, or erroneous state reporting that could mislead users about actual charge levels. The fact that the toggle was removed rather than left as an A/B test suggests the issue affected a meaningful slice of the Canary population and was severe enough to pull the feature wholesale.

This is Canary Channel behavior working as designed. The ring exists so that Microsoft can light up experimental code, collect feedback and crash data, and kill or revise features before they ever reach the Dev or Beta Channels. For Insiders who had grown accustomed to the color-coded battery icon, the sudden disappearance is jarring but instructive: Canary builds are not daily-driver material, and any one flight may yank a feature back without ceremony.

Accessibility experts have been watching the battery redesign closely. Color alone is insufficient for users with color vision deficiencies; a numeric percentage provides a critical fallback. The rollback raises the possibility that the percentage label wasn’t rendering correctly across all Windows themes and assistive technology stacks. Microsoft has said it will re-enable the updated icon in a future flight, but until then, Insiders are left with the status quo.

Control Panel-to-Settings Migration Gains Steam

While the battery icon takes a step back, Build 27928 takes a measurable step forward in the decadelong project to sunset the Control Panel. Microsoft has been chipping away at legacy applets since the Windows 10 era, and this flight relocates several practical, frequently used controls into the Settings app. The moves are incremental rather than transformative, but their cumulative effect is to reduce the number of reasons a user must open the Control Panel at all.

Newly surfaced or relocated items include:

  • Additional clocks — previously tucked inside the Control Panel’s “Date and Time” dialog, now accessible under Settings > Time & language > Date & time.
  • NTP server selection — the ability to change your time synchronization server, a staple for forensic examiners and enthusiasts, moves into Settings.
  • Date and time formatting overrides — including the AM/PM symbol, short/long date patterns, and first day of the week — are now editable directly in Date & time.
  • Number and currency formatting — decimal symbols, digit grouping, list separators, and currency symbols — shift to Settings > Time & language > Language & region.
  • Unicode UTF-8 worldwide language support toggle — previously a checkbox in the legacy “Region” dialog — is now a simple switch in Settings.
  • Copy user language and region settings to the welcome screen, system accounts, and new user accounts — a one-click option that admins and multi-user households will appreciate.

These are operational gains, not cosmetic ones. Setting up a secondary clock for a remote team, switching to a European date format, or forcing UTF-8 encoding for legacy applications are tasks that previously required navigating the Control Panel’s labyrinthine dialogs. By bringing them into Settings, Microsoft improves discoverability, searchability, and consistency for users who have never touched a classic .cpl file. It also paves the way for future Group Policy and mobile device management (MDM) integration, as Settings pages are typically easier to target with modern management tooling than the Control Panel’s loose collection of snap-ins.

Critically, none of the underlying Control Panel pages have been removed in this build. Enterprise administrators who rely on legacy paths for scripting or documentation are not forced to change behavior overnight. The migration is additive: new surfaces appear in Settings while the old dialogs remain in place, at least for now.

Fixes: A Targeted Reliability Pass

Beyond the headlining changes, Build 27928 ships a clutch of fixes that address bugs Insiders have been flagging for weeks. Microsoft’s changelog lists the following, though the company’s own caveat — that fixes are “gradual rollouts” and may not appear on every device immediately — applies.

  • dao360.dll crash fix: An underlying issue with the DAO (Data Access Objects) runtime could cause certain legacy applications to crash. Microsoft’s notes say the fix “should resolve an underlying issue,” but the language is cautious. Because the DLL is decades old and used by a wide range of third-party software, community verification will be essential before declaring the problem fully squashed. Insiders who run database-connected utilities or older line-of-business apps should pay special attention.
  • Click to Do (Preview): Text and image actions in the Copilot-powered overlay have been repaired. The feature, still behind a preview flag, had been silently failing for some users.
  • File Explorer: Two long-standing annoyances are addressed. First, preview windows no longer appear for unrelated app icons when hovering over taskbar or desktop items. Second, the “Unblock” checkbox in file properties now persists correctly after the dialog is closed.
  • Taskbar: A click-and-slide bug that caused further clicks to stop working when thumbnails were dragged has been squashed.
  • Input: Crashes tied to textinputframework.dll — which could take down Sticky Notes, Notepad, and other text-centric apps — are mitigated.
  • Login and lock screen: “Just a moment” hangs when signing in after a fresh boot or resume have been reduced, and the taskbar now loads faster after waking from sleep.
  • Live captions: The opacity slider now works, allowing users to dim the caption background instead of being forced into full opacity.
  • Settings crash: Adding a security key under Accounts > Sign-in options no longer crashes Settings — a relief for users hardening their authentication with FIDO2 keys.

Each of these fixes addresses real-world pain points reported in the Feedback Hub, and their inclusion signals that Microsoft is paying attention to the seamlessness of fundamental interactions — file management, text input, sign-in — even in the rawest Insider channel.

Known Issues: The Canary Tax

No Canary build ships without a list of known rough edges, and Build 27928 is no exception. The most notable regressions Insiders should be aware of:

  • Storage scanning hangs: Opening Settings > System > Storage > Temporary files can freeze the scanning process indefinitely. In addition, the “Previous Windows installations” option may simply not appear, preventing users from reclaiming disk space after an upgrade. Microsoft offers no workaround for the latter.
  • cmd/Terminal regression: When an unelevated command prompt is launched from the Run dialog (Win+R → cmd), the system may open Windows Console Host (the old console) instead of Windows Terminal, even if Terminal is set as the default terminal application. Typing wt in the Run dialog is an explicit, if inelegant, workaround until the regression is fixed.
  • DWM crashes: Increased Desktop Window Manager instability is flagged in this build. DWM handles all visual compositing on the desktop, so crashes can manifest as black screen flickers, momentary loss of window borders, or outright session drops. Microsoft hasn’t isolated the cause, and Insiders experiencing frequent DWM failures should capture feedback immediately.

These issues reinforce the central truth of the Canary Channel: it is not a place for machines you depend on. The DWM instability alone could make a development laptop unusable for hours at a stretch, and the storage scanning bug erodes a core maintenance function.

Deeper Signals: What Build 27928 Says About Microsoft’s Windows Roadmap

Micro-migrations are the new velocity metric. For years, the Settings app languished as a half-baked copy of the Control Panel. Build 27928 shows that the pace of migration has quickened — perhaps driven by internal deadlines to reach feature parity before the broader deprecation of legacy components. Moving date formatting, NTP selection, and UTF-8 toggles may seem mundane, but they address the “long tail” of settings that power users and admins actually need. Each relocation improves the odds that a user can configure their PC without ever opening the Control Panel.

Experimentation is gated by hard telemetry. The battery icon rollback proves that even small UI changes are subject to rigorous — and sometimes ruthless — data-driven decision-making. Microsoft’s willingness to yank a feature mid-flight suggests the telemetry pipeline is catching problems quickly and that the company is prioritizing stability over novelty, at least in the near term. For Insiders, this means that positive early reactions to a feature are no guarantee it will stick around if the numbers behind the scenes are unfavorable.

Accessibility is still a hurdle for visual changes. The battery icon redesign, which leaned on color and optional percentages, was explicitly lauded by accessibility advocates. Its temporary removal highlights how difficult it is to thread the needle between glanceable design, theme compatibility, and inclusive defaults. Until Microsoft can demonstrate the redesigned icon working flawlessly across high-contrast modes, scaling factors, and screen reader/Magnifier contexts, the old icon will remain.

Enterprise impact is gradual but real. For IT departments, Build 27928 doesn’t represent a sudden break, but it continues a trend that will eventually require documentation updates and script remediation. Organizations that have built workflows around Control Panel paths — such as setting regional formats via intl.cpl — should begin auditing those workflows now. The Settings app is becoming the authoritative configuration surface, and when the Control Panel finally shuts its doors, the transition will be less painful for those who prepared early.

Practical Guidance for Insiders and IT Pros

Checking your build and battery icon state: Go to Settings > Windows Update and confirm you’re on Build 27928 (released August 20, 2025). If your battery icon no longer shows color or a percentage, the rollback is active. Microsoft has not provided a timeline for re-enabling the new design, but Insiders should expect it in a future Canary flight after refinements.

Workaround for the cmd/Terminal regression: Press Win+R, type wt, and press Enter to launch Windows Terminal directly. Avoid using cmd from the Run dialog until the fix ships.

Locating the moved Settings items: Navigate to Settings > Time & language. Under Date & time, you’ll find additional clocks, NTP server settings, and date/time format overrides. Under Language & region, you’ll find number/currency formatting, the UTF-8 toggle, and the option to copy settings to system accounts. Familiarize yourself with these new locations; bookmark them for future reference.

Reporting feedback: Use the Feedback Hub (Win+F) and file issues under the appropriate category — Install and Update for general build problems, Desktop Environment > Taskbar or File Explorer for those fixes, and Settings for the migrated controls. Include screenshots, repro steps, and whether you’re using a standard or high-contrast theme. For DWM crashes, note the time and any patterns (e.g., after waking from sleep).

Enterprise checklist:
- Map existing scripts that call control.exe timedate.cpl, intl.cpl, or timedate.cpl to their Settings alternatives.
- Update internal documentation and help desk knowledge bases with screenshots of the new Settings pages.
- Test the UTF-8 toggle behavior with legacy applications that may not handle the encoding change gracefully.
- Do not pilot Canary builds broadly — wait for these migrations to land in Dev or Beta before including them in organizational testing rings.

Looking Ahead

Windows 11 Build 27928 is a snapshot of a platform in motion — not a milestone. The battery icon will return, likely with tweaks that address whatever telemetry red flags triggered its rollback. The Control Panel migration will inch forward, one applet at a time, until the day the legacy console is finally deprecated. In the meantime, Insiders who stick with the Canary Channel will continue to see churn, quick reversals, and occasional breakage — the price of an early ticket to Windows’ future.

For the rest of the user base, the build’s real story is one of quiet competence: the steady drumbeat of fixes, the unglamorous relocation of regional settings, and the invisible pipelines of crash dumps and diagnostic data that tell engineers what to fix next. That’s not flashy, but it’s exactly the kind of work that makes Windows 11 more coherent and reliable over the long haul.