That "Learn about this picture" prompt is a Windows feature called Visual Search, and you get rid of it by turning off the visual search setting in Windows Settings or Edge. Microsoft enabled it by default on many Windows 11 and 10 machines starting in 2023, so it usually comes back after updates unless you disable the setting at the policy level.

The button shows up as a small icon or overlay on desktop wallpapers and in some Edge contexts. It lets you reverse-image-search whatever is behind it through Bing, but most people find it intrusive. The fix is short, the reasons it reappears are technical, and the edge cases matter.

How the Visual Search Trigger Actually Works

Windows runs a component that detects images under your cursor and offers a Bing Visual Search shortcut. The feature is bundled with the Edge browser stack: version releases serving feature ID and allowed actions through separate flags on different keys, then the operating system surfaces an affordance. The relevant system setting is a registry value under the Explorer policy area, and the user-facing control sits in Settings under Privacy and Security.

The trigger is a lightweight content sniff: Windows checks whether the pointer rests over a rendered image region and whether the Bing Visual Search order is enabled. When both are true, the overlay appears. Nothing is uploaded until you click. That distinction matters, because the persistent fear that Windows is "sending your wallpaper to Microsoft" is misplaced until interaction.

After a click, the clicked region is sent as a query to Bing, which returns similar images and detected objects. The result is a web page, which is why the feature survives on machines with no Microsoft account. Microsoft's own documentation frames this as part of the Search highlights and search surface in Windows, and the company has shipped registry and Group Policy controls specifically to turn it off Microsoft Support.

Plain language: the button is a shortcut to a Bing image lookup, and it stays dormant until clicked.

Version History and Where the Setting Lives

The feature first appeared widely in Edge around 2022 and expanded to the Windows desktop in 2023. Microsoft enabled it through a staggered rollout, which is why two apparently identical PCs on the same build can disagree. Rollout flags are served from the cloud, so the setting can flip on after a routine update even if you never touched it.

The registry key most commonly cited is under HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE in the Explorer Policies path, with a DWORD named for the Bing Visual Search order. A value of 1 disables the feature for the relevant user or machine, and 0 or absence leaves it enabled. Group Policy equivalents exist for managed fleets, and Microsoft publishes the exact policy name in its administrative template documentation.

If the setting is missing from Settings, the cause is usually one of three things: an older build that predates the toggle, a cloud policy forcing the feature on, or a managed device where an administrator locked it. Checking Windows Update first resolves most of these.

Timeline of the rollout and control changes:

Period What changed Practical effect
2022 Visual search surfaces in Edge Browser-only prompt during early rollout
2023 Desktop wallpaper prompt expands Button appears on Windows 11 desktops
Mid-2023 Settings toggle documented Users gain a clear off switch
Late 2023 Registry and Group Policy controls Managed fleets can disable centrally
2024 Rollout continues on Windows 10 Older machines start showing it
2025 Feature persists in updates Setting must be rechecked after major upgrades

The counterintuitive part: even after you flip the toggle off, the cloud-served rollout can re-enable the surface on a future build. That is a policy behavior, not a bug, and it is why the registry method is more durable than the Settings toggle alone.

Why It Reappears and What Counts as "Off"

There are three independent switches, and each must be off for the button to vanish. The Settings toggle governs the current user. The registry value governs the policy layer. The Group Policy or cloud policy governs the machine and can override both. This layered design is deliberate: it lets IT departments enforce a consistent experience, but it also means a single off switch is not always enough.

Edge also carries its own visual search setting separate from the Windows one. If the button appears inside the browser but not on the desktop, the Edge setting is the culprit. If it appears on the desktop but not in Edge, the Windows setting is the one to check. That split explains most support threads where "I turned it off" did not work.

Red flags that point to a managed device rather than a user setting:

The Settings toggle is grayed out or missing entirely. The registry value resets after a reboot or policy refresh. An organization name appears in Windows settings. Edge shows "managed by your organization." The feature returns within hours of being disabled.

If any of those apply, the fix belongs to the administrator, not the user. Attempting to force the registry on a managed device can be overwritten silently.

Methods Compared: Settings, Registry, and Policy

The three removal methods differ in scope, durability, and risk. The Settings toggle is the safest and least durable. The registry edit is durable for a local user but requires care. Group Policy is the correct approach for fleets and is the only method that survives cloud-served rollouts reliably.

Comparison of removal approaches:

Method Scope Durability Reversible Risk
Settings toggle Current user Low, resets on update Yes Minimal
Registry DWORD User or machine Medium to high Yes, if backed up Low with backup
Group Policy Machine or domain High Yes Requires admin
Edge browser setting Browser only Medium Yes Minimal
Third-party tool Varies Unpredictable Usually Higher, avoid

One caveat professionals raise: registry edits must target the correct hive and path. A DWORD placed in the wrong key does nothing and can confuse later troubleshooting. Export the key before editing so the change is reversible in seconds. That single habit prevents most "how do I undo this" problems.

Practical Steps to Remove It Cleanly

Start with the toggle, confirm the result, then harden with policy if needed. Do the steps in order so you can tell which one worked.

Open Settings, go to Privacy and Security, then Search permissions or the General privacy area depending on build, and turn off the visual search or "Search highlights" toggle. Sign out and back in, or restart Explorer, since the overlay is cached per session. If the button reappears, open the registry editor and export the Explorer policy key, then set the Bing Visual Search DWORD to 1. On a managed device, ask IT to apply the Group Policy equivalent rather than editing the registry. Check Edge's own settings for a separate visual search toggle. After major Windows updates, recheck the setting once; updates are the most common cause of return.

A threshold worth knowing: if the button returns within one reboot cycle, the cause is almost certainly a policy or cloud flag, not a missing toggle. Treat that as a signal to escalate rather than repeat the same fix. If it survives more than 30 days and two reboots with the registry set, a managed policy is overriding it.

Concrete check: open the registry path and confirm the DWORD name and value match Microsoft's documented entry exactly. A single character off in the name yields no effect, and the setting looks correctly applied when it is not.

Limits, Caveats, and What This Does Not Solve

Disabling the button does not remove Bing Visual Search from Edge's context menu, and it does not stop search highlights elsewhere in the Start menu or taskbar search. Those are separate surfaces with separate controls. The feature can also return on a new device or a reset profile, because the setting is per-profile and per-machine.

The professional caveat: Microsoft's rollout behavior is not fully transparent. Cloud-served flags can change without a visible update, and Microsoft adjusts which builds receive the surface. No article can promise the button stays gone permanently on every build. The honest position is that policy-level disabling is the most durable available method, and it still requires periodic verification.

Microsoft support documents recommend checking the Windows release notes and the Edge policy documentation when a setting behaves unexpectedly. Those are the authoritative sources for exact registry paths and policy names. Do not rely on third-party registry cleaners, which commonly misplace keys and are not auditable.

Educational information only, not IT policy or security advice. For managed devices, consult your organization's administrator before editing system settings, and verify current paths against Microsoft's official documentation.