Microsoft is testing a set of AI-powered shortcuts directly inside the Windows 11 File Explorer right-click menu, turning the decades-old file manager into a quick-launch hub for image editing and visual search. The features—including background removal, object erasing, blur effects, and Bing-powered reverse image lookups—began surfacing in recent Insider builds and represent a dramatic shift in how the operating system surfaces generative AI.

The new “AI actions” submenu appears when you right-click any supported image file, such as a JPG or PNG. From there, users can launch a Bing Visual Search using the selected photo as the query, or instigate one-click edits like blurring a background, erasing unwanted objects, or removing the background entirely. These shortcuts don’t perform the magic inside File Explorer itself; instead, they route the request to the appropriate store app—Photos handles blur and erase operations, Paint takes care of background removal, and the built-in Bing UI fires up visual search.

What’s Actually in the Right-Click Menu

Insider participants running recent Canary or Dev channel flights—community reports spotlight Build 27938 as an early vessel—have noticed a new “AI actions” entry when clicking an image file. The initial set of image-oriented tasks includes:

  • Bing Visual Search: Uses the image as the search input, returning visually similar images, shopping results, landmarks, and extracted text.
  • Blur Background: Launches the Photos app with a background blur effect pre-applied; users can adjust blur intensity or refine the mask with a brush.
  • Erase Objects: Opens the generative erase workflow inside Photos, letting you brush over distractions to remove them.
  • Remove Background: Sends the image to Paint’s automatic background removal, delivering a clean cutout in seconds.

These options appear only for common raster formats—.jpg, .jpeg, .png—and Microsoft has telegraphed that document-level actions such as “Summarize” or “Create an FAQ” will come next for Microsoft 365 files, though those will be gated behind Copilot licensing for commercial customers initially.

The Plumbing: Local vs. Cloud and Why It Matters

The context menu entries act as shell hooks: Explorer hands off to the relevant app or a platform API, which then performs the model-driven operation. Whether that processing happens on-device or in the cloud depends on hardware, licensing, and the specific action. On Copilot+ certified PCs with dedicated NPUs, on-device inference is possible for certain edits; other devices and operations may fall back to cloud processing. Microsoft has not yet published an exhaustive per-action locality guarantee, and early Insider testing suggests that even on the same build, behavior can vary due to server-side gating and staged rollouts.

This hybrid model introduces a crucial privacy dimension: if an image contains sensitive content, a cloud-based edit or a Visual Search query could result in an inadvertent upload. The new workflows are low-friction by design—a single right-click can initiate a network call—so the risk of accidental exposure rises when users aren’t fully aware of the data path.

A New Settings Panel for Generative AI Control

Alongside the contextual actions, Microsoft has added a privacy surface under Settings > Privacy & security > Text and image generation. The page shows a recent-activity log of apps that have invoked Windows-provided generative models and offers per-app toggles to allow or block access. Enterprise-focused controls—likely via Group Policy and MDM—are expected to follow, giving administrators the ability to govern model access across fleets.

This visibility layer is a welcome first step. As generative AI moves from discrete apps into the platform itself, the number of third-party and first-party processes that can call those models expands dramatically. A centralized kill switch and audit view help mitigate the risk of shadow usage, but they don’t yet constitute a full audit trail suitable for regulated environments.

The Productivity Pitch

Microsoft frames these features as part of a broader effort to eliminate context switching. Instead of opening a browser, navigating to Bing Images, and dragging a file into a search box, users can kick off a visual lookup from the folder they’re already in. Similarly, quick edits that were previously buried in the Photos or Paint apps are now two clicks away.

For everyday tasks—scrubbing a license plate from a screenshot before sharing, creating a transparent product image for a quick listing, or finding similar items from a reference photo—the time savings are real. Design professionals will still rely on dedicated suites for non-destructive editing, but the micro-workflow approach fits the way millions of Windows users handle casual photo tasks.

Catch the Gates and Gaps

Despite the clear benefits, several rough edges and unanswered questions remain:

  • Licensing Complexity: Document-level AI actions will be restricted to Microsoft 365 commercial accounts with active Copilot entitlements. Consumer support is planned later, but for now the menu will be fragmented based on account type.
  • Fragmented Experiences: Because the features depend on Photos and Paint app versions, users who haven’t updated those store apps may see missing functionality or broken flows. Server-side gating further means two machines on the same Insider build may show different menus.
  • Accidental Cloud Uploads: The Visual Search option, in particular, lacks a clear “this will upload your image” warning at the moment of right-click. Microsoft’s privacy documentation will need to spell out retention policies and region handling for these queries.
  • Menu Clutter: Power users are already hunting for registry edits to hide the new entries. Without a user-facing toggle, the right-click menu could balloon, especially once document and Copilot actions join the party.

Enterprise Considerations

For IT departments, the Insider preview offers a critical evaluation window. Administrators should:

  • Test how the Text and image generation setting interacts with existing MDM or Group Policy restrictions. Microsoft has indicated that organization-wide deny/allow rules are in development.
  • Assess data residency risk. If a Visual Search or Copilot action routes through Microsoft’s cloud, regulated industries must verify that processing occurs in compliant geographies and that retention policies align with internal rules.
  • Plan for licensing gating. Document actions will not appear for users without the correct Microsoft 365 Copilot add-on, which could create support tickets if employees see coworkers with a richer menu.
  • Conduct controlled pilots. Because features can appear via server-side toggle, a small, monitored test group is the safest way to observe real behavior before broad rollout.

How to Test (and Lock Down) the Feature Right Now

Curious Insiders can try the AI actions by joining the Dev or Canary channel and updating to the latest build. If the menu doesn’t appear, remember that Microsoft stages rollouts—you may need to wait or, for adventurous users, use community-shared ViveTool feature IDs to force-enable the experiment (with the usual stability caveats).

To minimize data exposure:

  • Avoid using Visual Search on sensitive images until locality guarantees are clear.
  • Regularly check Settings > Privacy & security > Text and image generation for recent app activity and block any untrusted apps.
  • Prefer offline, local-only editors for confidential work, and disable on-device generative features through policy when available.

To hide the AI actions menu entirely, advanced users have posted registry modifications; always test such changes in a non-production environment first.

What Microsoft Got Right

Credit where it’s due: the implementation shows smart architectural choices. By leaning on Photos, Paint, and Bing as the engines, Microsoft avoided bloating File Explorer with heavyweight editing code. The shared “recent activity” settings pane brings some badly needed transparency to OS-level AI. And the use of Insider channels with gradual flighting allows the company to gather telemetry and user feedback before a wider release.

The Road Ahead

The experiments are still in flux. Key signals to watch:

  • Official confirmation from the Windows Insider Flight Hub of the exact builds that deliver these features to each channel.
  • Expanded documentation clarifying per-action locality, data flow diagrams, and tenant-level privacy controls.
  • The arrival of document-level AI actions and whether they remain locked to Copilot commercial accounts or trickle down to consumers.
  • Any rollout to the Beta or Release Preview channels, which would herald a near-final state.

Bottom line: Microsoft is betting that AI belongs in the places where users already manage their files, not just in a dedicated Copilot sidebar. The File Explorer right-click menu is the next frontier, and this Insider test shows both the promise and the pitfalls of embedding generative tools that close to the file system. For Windows enthusiasts and enterprise planners alike, now is the time to kick the tires, raise the hard questions, and shape the configuration before these features land on every Windows 11 desktop.