Click to Do is not just for text: select an image — or part of one — and you should get visual actions like visual search, background blur, erase objects, and copy as image. When images get no sparkle, no menu, nothing, half the feature is dark.
Image actions need the vision pipeline: the system must recognize the selection as an image, run it through on-device vision models, and offer the right actions. Text actions can work perfectly while the vision side is broken — they are separate models behind one menu. The same split-pipeline reality explains NPU usage spikes when idle , where one NPU workload misbehaves while others run fine.
Six fixes below: using the right selection method, verifying the vision components, repairing the pipeline, and testing across apps. Try an image in Edge’s image viewer after each step.
Why this happens
- Selecting images the wrong way: Click to Do on images often needs the Snipping Tool path or a specific gesture — selecting ‘around’ an image in some apps does not register as an image selection at all.
- Vision model components missing: Image actions need vision-capable on-device models. If those downloads failed, image actions vanish while text actions survive — the core of most Click to Do image actions missing reports.
- App rendering images opaquely: Apps that draw images through custom canvases (games, some editors, remote desktop) do not expose them to Windows’ image pipeline.
- NPU unavailable for vision models: Vision models are NPU-hungry; an unhealthy NPU degrades image actions first, since they are the heaviest Click to Do workload.
- Corrupt feature configuration: A damaged Click to Do menu configuration can drop the image-action set while keeping text actions.
- Image too small or too complex: Tiny icons or extremely busy images can defeat the vision model’s region detection, yielding no actions.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Use the Snipping Tool path for images
The most reliable image trigger is not selecting in-app — it is capturing with Snipping Tool.
- Press Win + Shift + S to open Snipping Tool and capture the image region.
- In the Snipping Tool preview, look for the Click to Do / text-action affordances on the capture.
- This path feeds Windows a clean image bitmap, bypassing app-rendering quirks entirely.
- If image actions work on snips but not in-app selections, the app was the blocker — use snips for that app.
Fix 2: Test on a clean, simple image
Rule out image-content issues with an ideal test case before touching settings.
- Open a clear photo in the Photos app or Edge — good lighting, single subject.
- Try the image gesture/selection there and check for image actions.
- Avoid tiny thumbnails and screenshots of dense dashboards for the test.
- Working on clean images but not your original means the content, not the feature, was the problem.
Fix 3: Verify vision AI components downloaded
Image actions need model files that text actions do not. Confirm they arrived.
- Install all pending Windows updates — vision components ship through Windows Update.
- Check Settings > Privacy & security > Click to Do for any component-download notices.
- Stay plugged in and online for an hour after updates; large model downloads take time.
- Interface-level affordances matter too — pinning the Copilot app to the taskbar shows how a missing UI entry point hides a working feature.
Fix 4: Check NPU health under vision load
Vision models stress the NPU hardest. Verify it is up to the task.
- Open Task Manager > Performance > NPU and confirm the tab exists and responds.
- Trigger an image action and watch for NPU activity — flat zero during a vision task is suspicious.
- Check Device Manager > Neural processors for driver warnings.
- Fix NPU driver issues first; vision actions typically recover as soon as the NPU does.
Fix 5: Reset Click to Do and test across apps
A corrupt menu configuration or a single bad app can both hide image actions. Separate the two.
- Toggle Click to Do off and on in Settings, then restart the PC.
- Test image actions in Photos, Edge, and Paint — three different rendering pipelines.
- If it works in two of three, the odd app out has a rendering incompatibility.
- If it fails everywhere, continue to the system repair step.
Fix 6: Repair Windows AI components
System-wide image-action failure after the above means the vision stack itself needs repair.
- Run
DISM /Online /Cleanup-Image /RestoreHealththensfc /scannowelevated. - Install every pending Windows update and restart.
- Create a new local user profile and test there to rule out profile corruption.
- If the new profile works, migrate your data rather than fighting the old profile’s damage.
Closing
Click to Do on images fails at the vision pipeline: wrong selection method, missing model components, opaque app rendering, or a struggling NPU. Lead with the Snipping Tool path, test on clean images, confirm the vision downloads, and check NPU health. Text and image actions are siblings, not twins — fix the vision side on its own terms. System-wide vision-stack failures are documented at Microsoft’s Windows support hub .
