Few things are more annoying than clicking a feature your laptop advertised and being greeted with “AI component not found.” You bought the Copilot+ PC, you saw the demos, and now Recall or Click to Do refuses to open with an error that sounds like Windows lost part of itself. It feels like a fundamental break, but it is usually a missing puzzle piece rather than a broken machine.

The error appears because Windows AI features are split in two: the visible feature you click, and a background component pack doing the neural-network work on the NPU. That pack is delivered and serviced separately through the Microsoft Store and Windows Update. When it fails to install, gets removed by a cleanup tool, or corrupts during a feature update, the visible feature survives but its engine is gone — and Windows reports it as a missing component.

The path back is straightforward: identify which feature is complaining, confirm the hardware qualifies, then repair or reinstall the component pack. If Click to Do’s summarize-PDF action is also failing , treat that as confirmation — both features drink from the same component well, as does the Snipping Tool’s missing Copilot actions . And if your machine throws unrelated surprises too — say Genshin Impact crashing on an ARM laptop — fix the AI components first anyway, since a healthy baseline helps everything.

Why this happens

  • Component pack never installed: On some machines the AI components are an optional payload that only arrives after the first full Store update cycle. If that cycle never completed, the feature exists but its engine never landed.
  • Corrupted by a feature update: Major Windows updates replace much of the component store. An interrupted update can leave the AI pack half-present, which reads as “not found.”
  • Removed by debloating or cleanup tools: Privacy scripts and aggressive cleaners target AI components deliberately. The feature shell remains, so the error only surfaces when you try to use it.
  • NPU driver failure breaks registration: Components register against the neural processor at install time. If the NPU driver was broken during that window, the pack reports itself missing.
  • Store cache or licensing glitch: A corrupted Store cache or licensing hiccup can make an installed component unreadable, which Windows interprets as absent.
  • Insufficient disk space during install: The AI models are large. If the drive was nearly full when Windows staged them, the install silently aborted and left the feature shell pointing at nothing.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Identify exactly which feature is failing

Different AI features depend on different sub-components, so the fix lands only when you know which feature raised the error.

  1. Note the exact feature showing the error — Recall, Click to Do, Live Captions with translation, or Studio Effects.
  2. Try a second AI feature; if all of them fail, the shared component pack is the problem rather than one feature.
  3. Check Settings > Windows Update for failed or pending updates mentioning AI, Copilot, or Recall.
  4. Write down what you find before changing anything — matching the fix to the symptom avoids reinstalling the wrong package.

Fix 2: Confirm the hardware and NPU still qualify

No point repairing a pack for hardware that cannot run it — verify the foundation first.

  1. Confirm the laptop is a Copilot+ PC with a 40+ TOPS NPU, and check Task Manager’s Performance tab for a healthy NPU tile.
  2. In Device Manager, verify the NPU entry shows no warning icon; reinstall the driver from the manufacturer’s support page if it does.
  3. Check the BIOS for an NPU or AI accelerator toggle and make sure it is enabled.
  4. If the hardware checks out, proceed; if not, the error is Windows being honest about an unsupported configuration.

Fix 3: Update Windows and the Microsoft Store completely

The component pack is serviced through these two channels, and many “not found” errors are simply a stalled delivery.

  1. Open Settings > Windows Update, install everything offered, restart, and repeat until no updates remain — Microsoft’s Windows 11 support hub covers the process if an update sticks.
  2. In the Microsoft Store’s Library, install all pending updates, watching for AI, Copilot, or system component entries.
  3. After both channels are fully current, restart once more and retry the failing feature before assuming deeper damage.
  4. If an update fails repeatedly, note its error code instead of skipping it — a stuck update is often the actual root cause.

Fix 4: Repair or reinstall the AI component pack

When updating does not deliver the missing pieces, force the issue by repairing the package directly.

  1. Open Settings > Apps > Installed apps, search for AI, Copilot, Recall, or Click to Do entries, and repair each via the three-dot menu.
  2. If repair is unavailable, uninstall the broken entry and reinstall from the Store for a clean package.
  3. If no entry appears at all, search the Store for the AI components — the pack may need an explicit first install.
  4. Restart and test the original feature; this resolves the majority of remaining cases.

Fix 5: Clear the Store cache and check system files

A corrupted Store cache can make a perfectly installed pack unreadable. This fix is safe and takes two minutes.

  1. Press Win + R, type wsreset.exe, and press Enter — a blank Store window opens and closes when the cache clear finishes.
  2. Reopen the Store, check Library for updates, and let anything AI-related reinstall.
  3. Run the system file checker from an elevated terminal to catch broader component-store damage.
  4. Restart and retry the feature; if the error is gone, only the registration was broken.

Fix 6: Free disk space, then reinstall as a last resort

Large AI models need staging room, and a full drive is a quiet saboteur. If space was the blocker, the reinstall finally lands here.

  1. Check the system drive’s free space — under 20 GB can alone explain a failed component install.
  2. Run Disk Cleanup on the system drive, targeting temporary files and old Windows Update leftovers.
  3. With space restored, repeat Fix 4’s Store reinstall of the AI component pack.
  4. If the error still survives, do an in-place Windows reinstall from the Windows 11 download page — keep your files while the component store is refreshed.

Closing

“AI component not found” sounds catastrophic, but it is one of the more honest errors Windows produces — it tells you exactly what is wrong. In the overwhelming majority of cases the fix is a repaired or reinstalled component pack — not new hardware, not a full reinstall. Work the list in order and the feature that refused to open will be back doing the NPU-powered work your laptop was built for.

Frequently asked questions

What does 'AI component not found' actually mean?
A Windows AI feature — Recall, Click to Do, Live Captions translation, or Studio Effects — tried to load its supporting package and found it missing or broken. The feature shell is installed, but its engine is gone, so Windows refuses to start it.
Is this error caused by my hardware?
Sometimes. If the NPU driver is broken or the machine is not a Copilot+ PC, the components may never have installed. On qualifying hardware it is usually a corrupted or half-removed component pack, fixable without touching hardware.
Can I ignore the error and keep using Windows normally?
Yes for everything except the AI features themselves — no files, apps, or stability are affected. Still, fixing it is worthwhile because one broken pack often backs several features at once.
Do I need to reinstall Windows to fix it?
Almost never. Repairing or reinstalling the AI component pack through the Microsoft Store and Windows Update resolves the vast majority of cases. A full reinstall is a last resort for a damaged component store.