Microsoft has shipped a new Windows 11 Canary build that finally restores the ability to see seconds in the expanded clock view, a long‑requested feature missing since the launch of Windows 11. But the build, reportedly numbered 27938, also pushes deeper into AI territory: File Explorer now offers right‑click AI actions for images, and a new Settings page gives users visibility and control over apps that tap into the operating system’s generative AI capabilities.

The clock restoration is an elegant olive branch to power users and anyone who missed the granular timekeeping available in Windows 10. Meanwhile, the AI additions signal a more ambitious shift—placing intelligent image editing tools directly in the file manager, alongside new transparency and governance controls that enterprise administrators will scrutinize.

The seconds clock returns, winning back user goodwill

When Windows 11 launched, Microsoft stripped the extended clock flyout of its seconds display, replacing it with a cleaner—but less functional—minimalist look. The move frustrated a vocal subset of users who relied on that precision for everything from synchronized testing workflows to resetting physical timers. For four years, the feedback persisted.

Build 27938 in the Canary channel finally adds a toggle under Settings > Time & language > Date & time that enables a larger clock in the Notification Center, complete with a ticking seconds field (HH:MM:SS) above the calendar. This is separate from the taskbar seconds option Microsoft added earlier; it specifically restores the expanded flyout behavior that many missed.

“It may seem like a pretty minor change, but there are plenty of fans of this feature who have called for Microsoft to add it,” notes the Windows Insider community. The implementation is opt‑in, so users who prefer a distraction‑free calendar can keep the toggle off.

Practical uses for the seconds display

  • Script testing and troubleshooting: Developers and IT pros often need second‑level accuracy to measure execution times or correlate log entries.
  • Physical clock synchronization: Setting analog watches or oven timers demands that precise second hand.
  • Accessibility: Some users with cognitive conditions benefit from the continuous visual cue.

Because the rollout is staged through Canary and Dev channels, not everyone on the same build will see the feature immediately; Microsoft gates these experiments server‑side.

AI actions land in File Explorer’s right‑click menu

The headline feature of this build is the integration of generative AI shortcuts directly into File Explorer. For supported image types—initially .jpg, .jpeg, and .png—a new “AI actions” submenu appears in the context menu, offering four one‑click flows:

  • Bing Visual Search: Uses the image as a search query, returning visually similar images, shopping matches, and extracted text.
  • Blur background: Calls into the Photos app to automatically blur the background behind detected subjects, with options for manual correction.
  • Erase objects: Invokes generative erase in Photos to intelligently remove distractions and fill the gap plausibly.
  • Remove background: Routes into Paint’s background removal to quickly isolate the subject and produce a cutout.

These actions aren’t new editors built into the shell; they leverage existing app engines. For example, “Erase objects” opens a Photos workflow that uses AI to inpaint the removed area. The idea is to shorten the distance between seeing an image in Explorer and performing a quick, common edit, all without launching a separate app.

Why the approach makes sense

  • Reduced friction: Most image edits are small touch‑ups, not full creative sessions. Right‑click actions collapse multiple steps into one.
  • Consistency: The features rely on Photos and Paint, which receive continuous improvements and share a familiar interface.
  • Discoverability: Placing AI tools where users already manage files lowers the barrier to adoption, especially for those unaware of Windows’ built‑in editing capabilities.

Current limitations

  • Format support: Only JPEG and PNG files are supported. RAW, TIFF, and other professional formats are excluded.
  • Host app dependency: Results depend on the versions of Photos and Paint installed; outdated apps may not support the full feature set.
  • Potential clutter: Power users often prefer lean context menus. Microsoft may need to provide per‑entry toggles or Group Policy controls to manage the noise.

Generative AI gets its own Settings page and governance controls

Alongside the user‑facing features, Microsoft has introduced a new privacy surface: Settings > Privacy & security > Text and image generation (or simply “Generative AI”). This page records recent activity—which apps have used Windows’ on‑device generative models—and provides per‑app toggles to allow or block access. Enterprise customers can manage the same controls through Group Policy or MDM.

This transparency move addresses a growing need as AI moves from optional cloud services into core platform APIs. IT administrators now have an auditable log and selective blocking, while users get a clear view of which software might be processing their data through AI.

What the Settings page reveals

  • App activity: A rolling list of applications that made calls to Windows‑provided generative models, along with timestamps.
  • Permission toggles: Individual apps can be denied access to text or image generation features without affecting other functionality.
  • Policy integration: Templates for Group Policy and MDM allow organizations to enforce AI access rules centrally.

Important caveats

The visibility is limited to Windows‑provided models and APIs. Apps that make direct, out‑of‑band calls to cloud AI services (e.g., a third‑party app using its own Azure endpoint) are not tracked. Administrators must supplement this with network monitoring and app‑level audits. Moreover, even on‑device models may process sensitive content, so the Settings page is a helpful transparency tool—not a replacement for comprehensive privacy assessments.

Rollout realities: Canary experiments demand caution

The features described are shipping in the Canary channel, the most bleeding‑edge testing ring in the Windows Insider Program. Canary builds are intentionally unstable and intended for validation, not production machines. Microsoft uses server‑side gating to enable features on subsets of devices, meaning even if you install build 27938, you may not see the new clock toggle or AI actions immediately.

Community reports confirm that the features have staged appearances; some insiders see the expanded clock but not the AI submenu, or vice‑versa. This incremental rollout allows Microsoft to gather telemetry and fix regressions before broader deployment.

How to try these features safely

  1. Join the Windows Insider Program and opt into the Canary channel, but only on a non‑critical device.
  2. Ensure Photos and Paint are updated through the Microsoft Store—the AI actions depend on their latest versions.
  3. If you don’t see the features after updating, wait; forcing activation via third‑party tools like ViveTool is unsupported and can destabilize the system. Always back up data and create a system image before testing.

Enterprise and privacy implications

For IT decision‑makers, the introduction of OS‑level generative AI and a dedicated Settings pane is a welcome improvement—but it demands proactive policy updates.

  • Audit which apps request AI access: The activity log may not cover all AI calls, so supplement with endpoint detection and response (EDR) tools.
  • Apply Group Policy or MDM controls promptly: Use the new templates to block untrusted apps or enforce enterprise‑approved AI usage.
  • Update security baselines: Include AI‑specific risk assessments in change management processes, particularly around data exfiltration and model training.

Privacy‑conscious users should treat the Settings page as an early‑stage transparency tool. While it logs Windows‑provided AI invocations, it won’t capture everything. For sensitive workloads, combine it with network‑level monitoring and device‑wide privacy settings.

Strengths, risks, and what to watch

Immediate benefits

  • User goodwill: Restoring the seconds clock is a fast, low‑risk quality‑of‑life improvement that addresses years of feedback.
  • Lowered editing friction: AI actions in Explorer replace multi‑step workflows with a single right‑click for quick image touch‑ups.
  • Foundational governance: The Generative AI Settings page establishes a baseline for user consent and enterprise control, setting the stage for more granular policies.

Risks and unknowns

  • Feature fragmentation: Canary experiments may take months to reach production, and their final form could differ substantially.
  • Privacy gaps: The telemetry only covers Windows‑provided APIs, not direct cloud calls. Over‑reliance on the Settings page could create a false sense of security.
  • Context menu bloat: Without granular toggles, power users may grow frustrated. Future builds will likely need per‑action visibility controls or Group Policy exclusions.
  • Stability: Canary builds carry inherent risks of Explorer crashes, thumbnail generation issues, or other regressions. Testing on a spare machine is essential.

Practical verdict for different user profiles

  • Casual users: The seconds clock is a pleasant, low‑risk tweak. No rush to test Canary; wait for broader Dev or Beta rollouts if stability is a priority.
  • Power users and creators: The File Explorer AI actions will shave minutes off quick edits. Consider joining Dev or Canary on a secondary machine, and keep Photos/Paint updated.
  • Administrators and security teams: Treat the Generative AI Settings as a call to update policies, audit app behavior, and review data flow. Test Group Policy in a controlled environment before wide deployment.

Looking ahead: a pragmatic blend of nostalgia and AI

Microsoft’s latest Canary experiment encapsulates the dual nature of Windows 11’s evolution: restoring familiar usability while embedding AI where people already work. The seconds field in the Notification Center is a humble, user‑driven correction that proves the company still listens to its community. At the same time, the integration of AI actions into File Explorer and the introduction of governance controls reflect a strategic attempt to make AI feel like a natural extension of the operating system—not a bolted‑on afterthought.

The tradeoffs between discoverability, privacy, and control are not fully resolved, but the presence of toggles and enterprise policies signals that Microsoft understands the governance dimension. Iterative refinements, staged rollouts, and further policy polish are likely as these features graduate from Canary to wider Insider rings and, eventually, general availability.

For now, the message is clear: the little things still matter, and Microsoft is experimenting with where intelligence belongs—in the shell, in first‑party apps, or both. The clock is ticking again, and with it, a new era of context‑aware, OS‑level AI is beginning to take shape.