Recall is supposed to introduce itself: a dedicated opt-in screen explaining what it captures, where the data stays, and asking for your explicit consent before the first snapshot is ever taken. On your machine, that screen never appeared. Now Recall sits in Settings in a half-configured limbo — not capturing, not properly set up, and not offering you the consent flow it owes you.

The missing opt-in is a symptom, not the disease. Windows shows that screen only when everything upstream is ready: the hardware qualifies, security prerequisites are met, setup components are intact, and no policy suppresses it. When any of those fail, Windows skips the screen silently instead of explaining why.

This guide gives you six fixes in technician order: verify requirements, check security prerequisites, repair setup components, and manually re-trigger the consent flow. Work through them in sequence.

Why this happens

  • Hardware requirements not met: Recall requires a Copilot+ PC — Snapdragon X series, AMD Ryzen AI 300 series, or Intel Core Ultra 200V series with an NPU. On non-qualifying hardware, the opt-in never appears because Recall is unavailable.
  • BitLocker or Secure Boot not enabled: Recall’s security model requires device encryption and Secure Boot. Without them, Windows withholds the opt-in rather than offering a feature it cannot secure.
  • Damaged setup components: The first-run experience components that render the opt-in flow can corrupt during updates, leaving Settings able to show the Recall page but unable to launch the consent screen.
  • Opt-in skipped during Windows setup: If you rushed through the out-of-box experience, the Recall step may have been dismissed — and Windows does not always surface it again on its own.
  • Policy suppressing the prompt: Group Policy or MDM settings can disable Recall or suppress its setup prompts, particularly on work or school machines.
  • Stale Windows build: The Recall opt-in flow evolved across Windows 11 builds; an outdated build may lack the current consent experience entirely.

How to fix it

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

Fix 1: Verify your PC actually qualifies for Recall

No fix can conjure the opt-in screen on hardware Windows does not support. Two minutes of verification here saves you from chasing a screen that was never going to appear.

  1. Open Settings > System > About and note your processor — Recall needs a Copilot+ class NPU (Snapdragon X, AMD Ryzen AI 300, or Intel Core Ultra 200V series).
  2. Check Settings > Privacy & security > Windows Security > Device security and confirm Secure Boot is on.
  3. Confirm BitLocker/device encryption is enabled — Recall’s consent flow is gated on it, as the BitLocker-related Recall guide explains in depth.
  4. If any requirement fails, that is your answer: meet the requirement first (enable Secure Boot/encryption where possible), then re-check for the opt-in.
  5. Microsoft lists the full requirement set in its Windows support hub — compare your machine against it before proceeding.

Fix 2: Trigger the opt-in flow from Settings manually

If your hardware qualifies, the consent flow may simply need a manual nudge. The Recall settings page can re-launch setup even when the automatic prompt never fired.

  1. Go to Settings > Privacy & security > Recall & snapshots.
  2. Look for a setup, “Get started,” or enable prompt on the page — on qualifying machines this launches the consent flow directly.
  3. If the page shows Recall as available but no setup prompt appears, toggle Recall on — the opt-in screen should appear as part of enabling it.
  4. Read the consent screen carefully when it appears; it explains capture scope, storage, and your controls. This is the screen that was missing.
  5. Complete the flow and confirm the timeline begins populating — the opt-in is only real once captures start.

Fix 3: Repair the first-run experience components

When the settings page cannot launch the consent screen — clicking does nothing, or the screen flashes and vanishes — the setup components themselves are damaged. Repairing them restores the flow.

  1. Open an elevated Command Prompt and run sfc /scannow to repair corrupted system files, including setup-experience components.
  2. Follow with DISM /Online /Cleanup-Image /RestoreHealth if SFC reports errors it cannot fix.
  3. Restart with a full shutdown (hold Shift while clicking Shut down) so the repaired components reload cleanly.
  4. Return to Settings > Privacy & security > Recall & snapshots and attempt the manual trigger from Fix 2 again.
  5. If a different window-management quirk has been bothering you, live captions windows that won’t move are a separate UI issue with their own guide.

Fix 4: Update Windows to a build with the current Recall experience

The opt-in flow is build-dependent. An outdated Windows 11 may predate the current consent experience or carry a buggy early version of it that never renders.

  1. Go to Settings > Windows Update and install all pending updates, then check your build number with winver.
  2. Compare against the current Recall-capable builds documented in the Windows support hub — Recall’s setup experience matured significantly across 2024–2025 builds.
  3. Install any pending feature updates, not just cumulative ones; the consent flow lives in the feature layer.
  4. After updating, restart and check Settings > Privacy & security > Recall & snapshots for the setup prompt.
  5. Hardware-adjacent faults on ARM machines follow the same update-first discipline — see the USB dock issues on ARM laptops guide for another example of the pattern.

Fix 5: Reset Recall’s configuration state and start clean

If requirements are met, components are repaired, no policy blocks it, and the build is current — yet the opt-in still will not appear — the configuration state itself is wedged. Clearing it forces Windows to treat Recall as never-configured.

  1. In Settings > Privacy & security > Recall & snapshots, turn Recall off if it shows as on.
  2. Use Delete snapshots > Delete everything to clear any partial configuration state (there should be little or nothing if the opt-in never completed).
  3. Restart with a full shutdown, then return to the Recall settings page — Windows should now present the first-run consent flow.
  4. Complete the opt-in carefully; declining or dismissing it returns you to the exact limbo you started in.
  5. If the screen still refuses to appear after all six fixes, file the pattern in Feedback Hub under Privacy > Recall with your hardware details — you have eliminated every documented local cause.

Closing

The missing opt-in screen is Windows silently telling you something upstream is not ready — hardware, encryption, components, policy, or build. Verify the requirements, repair the setup path, clear policy suppression, and re-trigger the flow manually. The consent screen exists to protect you; getting it to appear means Recall starts on your terms, with your explicit permission.

Frequently asked questions

What is the Recall opt-in screen?
The consent screen Windows shows during Recall setup, explaining what Recall captures and asking explicit permission before it starts. Recall cannot begin capturing until you complete it.
Why did I never see the Recall opt-in screen?
Usual reasons: the PC does not meet Recall’s hardware or security requirements, setup components are damaged, a policy suppresses the prompt, or you skipped it during Windows setup and it never reappeared.
Can I bring back the opt-in screen after skipping it?
Yes. These fixes re-trigger the setup flow — through Settings, by repairing setup components, or by meeting the requirements that were blocking it.
Is Recall running if I never saw the opt-in screen?
No. Without your explicit opt-in, Recall captures nothing. Check Settings > Privacy & security > Recall & snapshots — the toggle will show it as off.