Microsoft has quietly begun testing a fresh Canary-channel build that weaves AI-powered image tools directly into File Explorer’s context menu and restores a seconds hand to the Notification Center clock. An early report from Neowin details Windows 11 Insider Preview Build 27938, a release that surfaces quick edits and visual search inside the shell while giving users visibility into which apps tap the operating system’s on‑device generative models. Although official documentation remains elusive—the build does not yet appear in Microsoft’s public Flight Hub or Windows Insider Blog—the feature set aligns with months of incremental Dev‑ and Canary‑channel experiments aimed at making Windows a first‑class AI canvas.

The Insider community has been anticipating this moment. For over a year, Microsoft has signaled that Copilot, “Click to Do,” and on‑device AI agents would eventually land in everyday workflows. Build 27938 is the latest proof that the company means it: right‑click an image and a new “AI actions” submenu offers Bing Visual Search, background blur, generative erase, and one‑click background removal. It is a practical, friction‑reducing design that keeps users in the same window—no need to launch a separate app just to clean up a photo before attaching it to an email or posting it to Teams.

AI Actions Land in File Explorer

At the heart of the update is an AI actions entry that appears when you right‑click a supported image file (.jpg, .jpeg, or .png). Instead of building new editing engines from scratch, the shell acts as a launcher, handing off the image to Microsoft’s Photos and Paint apps for the heavy lifting. The initial four actions are:

  • Bing Visual Search: submit the image to Bing to find similar pictures, products, landmarks, text extraction, or faces. This turns any local file into a web‑search catalyst without opening a browser.
  • Blur Background: opens Photos and automatically applies a background blur. Users can adjust intensity and use a brush tool for manual refinements—ideal for quickly obscuring sensitive details or adding a professional bokeh effect to a headshot.
  • Erase Objects: invokes the generative erase flow in Photos, letting you remove distracting elements like passersby, power lines, or trash from a scene with a few clicks.
  • Remove Background: routes to Paint’s automatic background removal, delivering a clean subject cutout in seconds. The feature has been a staple in Paint since late 2023 and now becomes more discoverable.

The engineering choice is deliberate. By keeping the image‑editing logic inside Photos and Paint, Microsoft avoids bloating Explorer while ensuring that the actions’ behavior stays consistent with the Store‑app versions users already have. That means Insiders must keep Photos and Paint updated to see the latest flows; older app versions may produce unexpected results. At launch, only the three common image formats are supported, so photographers working with RAW or PSD files will still need dedicated tools.

A Smaller Usability Win: The Clock Shows Seconds Again

For years, Windows 10 power users have mourned the loss of a system‑tray clock that displays seconds. Build 27938 partly answers that nostalgia with a toggle tucked inside Settings > Time & language > Date & time: “Show time in the Notification Center.” Flipping it on enlarges the clock in the Notification Center flyout and adds a steady seconds counter above the date and calendar. It is a small affordance, but one that matters when you are timing a script, troubleshooting latency, or simply prefer the granularity. The option is being introduced gradually via server‑side feature flags, so not every Insider will see the toggle immediately. If it is missing, patience—or a calculated risk with ViVeTool—is the only workaround.

A New Privacy Pane for On‑Device AI

As generative models move onto local hardware, transparency becomes paramount. Build 27938 adds a “Text and image generation” page under Privacy & security. This dashboard lists recent app activity that used Windows‑provided generative models and provides toggles to block access on a per‑app basis. Administrators will eventually need Group Policy and MDM controls to enforce rules across fleets, but the consumer‑facing page is a meaningful first step. It does not yet clarify retention periods for activity metadata or whether any signals leave the device, but it at least gives users a window into which third‑party applications are invoking on‑device AI.

What Else Is Fixed (and What Is Still Broken)

Canary builds inherently mix progress with regressions. According to the release notes shared by Neowin, Build 27938 ships with several fixes:

  • File Explorer thumbnail generation should no longer hang or produce blank icons.
  • WMI scanning performance has improved, reducing CPU spikes during remote management queries.
  • A Task Manager freeze that occurred when switching between tabs has been addressed.

But the list of known issues is equally noteworthy:

  • Installation rollbacks: Some Insiders report rollbacks with error codes 0xC1900101‑0x20017 or 0xC1900101‑0x30017. Repeated attempts may lead to the same failure. Microsoft is investigating, so do not install this build on a device you rely on for daily work.
  • Audio driver headaches: Device Manager may show yellow exclamation marks on audio devices such as “ACPI Audio Compositor,” accompanied by the message “Windows cannot load the device driver for this hardware.” The documented workaround is to manually update the driver via Device Manager and select the most recent compatible driver from the local list.
  • PIX GPU capture playback broken: Developers using Microsoft’s PIX tool for DirectX 12 diagnostics will encounter playback issues. A future PIX update is expected to resolve the incompatibility. Until then, holding off on Canary upgrades is advisable if GPU captures are essential to your workflow.
  • Screen flicker and DWM instability: Some testers have observed display flickering when browsing, a telltale sign of desktop window manager regressions. Graphics driver updates rarely cure these issues in early flights, so Feedback Hub reports are the best medicine.

Verification Gap: Treat Community Reports as Tentative

Microsoft’s Flight Hub and Windows Insider Blog are the canonical sources for build announcements. At the time of writing, neither lists a dedicated entry for Build 27938, even though neighboring builds in the 27800 and 27900 ranges have been acknowledged. This could mean the build is rolling out in phases, or that an official post is delayed. The Neowin report is detailed and aligns with Insider program patterns, but without a direct Microsoft link, the information should be treated as likely but not yet fully corroborated. Readers who require authoritative confirmation should monitor Flight Hub and the Insider Blog before deploying.

Practical Guidance for Insiders and IT Admins

Given the experimental nature of Canary builds, different audiences should approach Build 27938 with different strategies.

For enthusiasts and hobbyists:
- Use a non‑critical PC, virtual machine, or spare laptop. Canary builds can and do break essential functions.
- Keep Photos and Paint updated via the Microsoft Store so AI actions work as intended.
- If you do not see the seconds‑clock toggle, wait—feature flags ramp slowly.

For power users and developers:
- Availability of AI actions may differ between machines on the same build due to server‑side flags. Do not expect uniformity.
- PIX users should pause Canary upgrades until Microsoft’s PIX team confirms a compatible release.

For IT admins and enterprise pilots:
- Validate any build against Flight Hub before approving for a pilot group. Re‑check that an official post exists.
- Assemble a pilot group that mirrors your hardware mix: Copilot+ devices, legacy machines, and varying Microsoft‑365 license tiers all behave differently.
- Audit the new Text and image generation activity page to understand which third‑party apps might be tapping the OS generative models.
- Update help‑desk runbooks with steps for audio‑driver recovery and install‑rollback workarounds. Document the driver‑update procedure: open Device Manager, right‑click the affected device, choose “Update driver” > “Browse my computer for drivers” > “Let me pick from a list of available drivers on my computer,” then select the most recent compatible driver.

Risks, Tradeoffs, and Unanswered Questions

The arrival of AI actions inside File Explorer raises several long‑term concerns:

  • Hardware and licensing fragmentation: Microsoft has already indicated that some future AI features—such as document summarization—will require a Microsoft 365 Copilot subscription or a Copilot+ PC with a neural processing unit. That creates a two‑axis gate that will complicate support and user expectations in organizations with mixed fleets.
  • Privacy telemetry: The new Settings activity page provides visibility, but questions remain about what metadata is collected, how long it is retained, and whether any of it leaves the device. Regulated industries will need answers before embracing on‑device AI broadly.
  • Context‑menu clutter: Power users already have dense right‑click menus. Adding an AI actions submenu is reasonable for images, but if the same approach expands to documents, videos, or folders, a global toggle to hide AI entries would become essential.
  • Canary stability: Early adopters accept risk, but widespread regression reports in a Canary build can foreshadow painful months in the Dev and Beta channels. Organizations that need reliability should stay on the Release Preview track.

Why This Build Matters

Microsoft’s decision to embed AI shortcuts directly in the shell is more than a gimmick. It acknowledges that most users do not consciously “do AI”; they want tasks completed with minimal friction. By placing quick edits and visual search one right‑click away, the barrier to entry vanishes. The return of the seconds clock, meanwhile, shows that product managers are still listening to long‑standing community requests—no feature is too small if it improves daily rhythm.

Together, these changes hint at a Windows 11 that gradually blends intelligence into the places you already work. The challenge is execution: rolling out features smoothly, providing clear admin controls, and being transparent about telemetry. Build 27938, even if unofficial, offers a preview of that future. Test it with curiosity, but always with a backup plan.