Recall opens fine, but the timeline is empty — no new snapshots are being saved. The feature looks alive while silently capturing nothing. This is a different problem from Recall not working at all : the app launches, the requirements pass, but the capture pipeline is stalled somewhere between your screen and the database.

Snapshot saving depends on a chain: the capture service running, storage available, content filters allowing the current screen, and a healthy database. Break any link and saving stops. Work through these in order.

Why this happens

  • Save snapshots toggled off: The master switch is off — by user action, debloat script, or policy.
  • Paused manually: Recall’s pause (from the system tray) persists until resumed; users forget they paused it.
  • Disk space exhausted: No room means no new snapshots, often with no clear error.
  • Corrupted snapshot database: A damaged database accepts no new writes.
  • Content filtering: DRM, private windows, and excluded apps/websites are skipped by design.
  • Snapshot service crashed: The background capture service can die while the Recall UI stays open.
  • Storage allocation set to zero: The max-storage slider can end up at minimum, choking new saves.
  • Windows Hello signed out: If Hello authentication lapses, Recall may pause capture until you sign back in.

How to fix it

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

Fix 1: Check the master switches

The embarrassingly common causes first — verify before assuming complexity.

  1. Settings, Privacy & security, Recall & snapshots — confirm “Save snapshots” is ON.
  2. Click the Recall icon in the system tray — make sure it is not paused; resume if it is.
  3. Check the snapshot storage allocation slider — ensure it is not set to minimum.
  4. If you previously disabled Recall , reverse those steps fully.
  5. Toggle saving off and on once to restart the capture pipeline.

Fix 2: Free disk space

The silent killer of snapshot saving.

  1. Settings, System, Storage — check free space on C:; Recall needs tens of GB.
  2. Empty Recycle Bin, run Storage Sense, move large personal files to another drive.
  3. In Recall settings, delete old snapshots to reclaim space immediately.
  4. Reduce the maximum snapshot storage so future accumulation stays bounded.
  5. Our Recall disk usage guide has deeper storage tuning.

Fix 3: Restart the snapshot service

A dead capture service looks exactly like this.

  1. Open Task Manager, Services tab — look for Recall/snapshot-related services.
  2. Restart any that show Stopped or odd states.
  3. Alternatively, reboot — the simplest service restart there is.
  4. After reboot, use the PC normally for 5 minutes, then check the Recall timeline for new entries.
  5. If the service dies repeatedly, check Event Viewer for the crash reason — note it for Fix 5.

Fix 4: Clear content filters and exclusions

Maybe Recall is saving — just not what you are looking at.

  1. In Recall settings, review the excluded apps and websites list — remove anything you actually want captured.
  2. Test with a plain app (Notepad, File Explorer) — if those save but your browser does not, it is filtering.
  3. Remember: private/incognito windows and DRM video are never captured, by design.
  4. Temporarily disable any “privacy” utilities that might block screen capture APIs.
  5. If plain apps save fine, your Recall is healthy — adjust exclusions, not the feature.

Fix 5: Rebuild the snapshot database

Corruption blocks writes; a fresh database unblocks them.

  1. Settings, Recall & snapshots — “Delete snapshots” to wipe the database.
  2. Toggle “Save snapshots” off, reboot, toggle back on.
  3. Wait 10-15 minutes of active use for the fresh database to populate.
  4. Check the timeline — new snapshots should now appear.
  5. If saving worked briefly after an update then stopped, see Recall not working after update — updates can re-corrupt the database.

Fix 6: Check for policy or update blocks

External forces can silently disable saving.

  1. On work machines, ask IT whether Recall snapshotting is policy-disabled — it often is.
  2. Check Windows Update history for recent updates coinciding with the stoppage.
  3. Install all pending updates — Microsoft fixes snapshot pipeline bugs in cumulative updates.
  4. Run sfc /scannow in admin Command Prompt to repair system file damage affecting the capture stack.
  5. If nothing helps on qualifying hardware, file Feedback Hub feedback with your timeline — include when saving stopped.

Closing

Snapshots not saving is a pipeline problem: the switch, the service, the storage, or the database. Check the toggles, free the disk, restart the service, and rebuild the database — in that order — and saving resumes in the large majority of cases. Remember that some gaps are by design (locked screen, private windows, DRM), so judge “not saving” against what Recall is actually supposed to capture, not against an expectation of total surveillance. When in doubt, the 10-minute active-use test after each fix tells you definitively whether that fix worked.

Frequently asked questions

How often should Recall save snapshots?
By default every few seconds while you are actively using the PC. Gaps during idle time are normal — Recall pauses when the screen is locked, during private browsing, or when you pause it manually.
Do snapshots save when the laptop is asleep?
No. Recall only captures while Windows is active and unlocked. Sleep, hibernate, and lock screen all pause snapshotting by design.
Can DRM or private windows block snapshots?
Yes. Recall deliberately skips DRM-protected content and private/incognito browser windows. If snapshots are missing only for certain apps or sites, that filtering — not a bug — is usually why.
Will deleting snapshots fix saving issues?
Often, yes. A corrupted snapshot database can block new saves; wiping it gives Recall a clean slate. You lose old history, but saving resumes.