You open Recall expecting to scroll back through yesterday’s work, and there is nothing there — gaps in the timeline, or a completely empty history where snapshots used to be. It is unsettling, because Recall’s entire promise is that everything is captured locally on your device and stays searchable. When snapshots go missing, the feature feels broken.

The good news is that snapshots rarely vanish at random. In most cases something specific stopped them from being saved, hid them from view, or removed them on a schedule you never noticed. Your Recall privacy settings are the first place to look — filters for apps and websites silently exclude whole chunks of activity — followed by storage limits and a paused capture state.

This guide walks through diagnosing exactly where your snapshots went and getting capture running again, starting with the quick checks and moving into storage and filters. If you have also noticed Recall draining your battery faster than expected, that can be related, since heavy snapshot processing sometimes coincides with capture problems. And if snapshots were never saved at all rather than disappearing later, see our guide on Recall snapshots not saving .

Why this happens

  • Capture is paused: Recall can be paused from its system tray icon or quick settings. While paused, no new snapshots are taken, so the timeline develops gaps that look like missing data.
  • Storage allocation is full: Recall keeps snapshots until it reaches its storage cap, then silently deletes the oldest ones first. If the cap is small, weeks of history can disappear.
  • Apps or websites are filtered: Any app or website on your filter list is never snapshotted. If the missing period lines up with time spent in a filtered browser or app, the snapshots were never taken.
  • Snapshots deleted by date range: Recall lets you delete snapshots from a time range. An accidental or scheduled deletion wipes that window permanently.
  • Storage Sense removed snapshot data: Aggressive Storage Sense or manual Disk Cleanup runs can remove data Recall depends on, especially after a big cleanup.
  • Corrupted snapshot database: If the local snapshot index corrupts — often after a crash or failed update — Recall may show an empty timeline even though capture is on.
  • Recall was reset or reinstalled: Resetting Recall or reinstalling Windows clears the snapshot store. There is no cloud backup to restore from, by design.

How to fix it

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

Fix 1: Confirm Recall is on and not paused

Recall’s pause control is almost too convenient: one click on the tray icon or quick-settings tile silences capture indefinitely, with no loud reminder that it is off. Many users pause it for a sensitive meeting and forget for days. Resuming restarts capture instantly, and new snapshots start flowing within minutes.

  1. Open Settings with Win + I, then go to Privacy & security > Recall & snapshots.
  2. Check that the main Recall toggle is On.
  3. Look at the Recall icon in the system tray — if it shows a paused state, click it and choose Resume.
  4. Use your laptop normally for 10–15 minutes, then reopen Recall and check whether new snapshots appear.

Fix 2: Check the snapshot storage limit

Recall treats its storage allocation as a hard ceiling. Once snapshots fill the cap, the oldest history is deleted automatically and quietly in the background. A small cap — or one shrunk by a settings reset — can erase weeks of history. Raising the cap stops the bleeding, though nothing deleted comes back.

  1. In Settings > Privacy & security > Recall & snapshots, find the storage allocation section.
  2. Note the maximum storage Recall is allowed to use and how much is currently used.
  3. If usage is at or near the cap, increase the maximum storage using the slider or dropdown.
  4. Free up general disk space too — Recall needs breathing room on the system drive to keep saving.

Fix 3: Review filtered apps and websites

Filters are the silent killers of timelines. Anything on your filtered-apps or filtered-websites list is never captured at all, so there is no gap or error — that activity simply never existed as far as Recall is concerned. Browsers are the most common accidental entry, which makes entire browsing sessions vanish. Reviewing the list takes a minute and explains a large share of ‘missing’ history.

  1. In the Recall settings page, open the filters section for apps and websites.
  2. Remove anything you actually want captured — browsers are a common accidental entry.
  3. Check the sensitive-content filtering option as well; it can exclude screens containing things like passwords or ID numbers.
  4. After changing filters, give Recall some time and confirm new snapshots include the previously missing apps.

Fix 4: Look for time-based deletions

When a specific date range is empty but everything around it is intact, those snapshots were deleted rather than never captured. Recall’s date-range deletion is precise and permanent, and it is easy to select a wider range than intended. There is no recycle bin, so the honest answer here is usually acceptance plus better habits going forward — not a technical recovery.

  1. In Recall settings, open the option to delete snapshots and check whether a time range was cleared.
  2. Ask anyone else who uses the laptop whether they deleted snapshots — deletion is permanent.
  3. Going forward, avoid bulk date-range deletions unless you are sure you will not need that history.
  4. There is no recycle bin for snapshots, so treat deletion as final.

Fix 5: Keep Storage Sense away from Recall data

Storage Sense and Disk Cleanup do not know which files matter to Recall. An aggressive cleanup can remove data the snapshot pipeline needs, or damage the store itself — usually after a forgotten ‘free up space’ session. Excluding Recall’s data from future cleanups prevents a repeat.

  1. Open Settings > System > Storage and review your Storage Sense configuration.
  2. Turn off automatic cleanup of temporary files if it runs frequently, or at least run it manually.
  3. Never manually delete files from Recall’s data folders under your user profile.
  4. After a cleanup-related loss, re-enable capture and let Recall rebuild its store going forward.

Fix 6: Reset the snapshot store as a last resort

When capture is on, filters are clean, and storage is available yet the timeline stays empty, the local snapshot database is corrupt — typically after a crash or failed update. Resetting gives Recall a brand-new store: you lose old history, but capture starts working again immediately.

  1. In Recall settings, use the option to delete all snapshots and reset Recall.
  2. Restart your laptop after the reset completes.
  3. Reopen Recall and let it capture for at least 30 minutes before judging.
  4. If even a fresh store will not capture, check for pending Windows updates at Microsoft’s Windows support hub and install them, since Recall fixes ship through Windows Update.

Fix 7: Check Event Viewer for capture errors

Guessing wastes time when Windows keeps receipts. The Event Viewer logs application and system errors with exact timestamps, so you can find what broke at the precise moment snapshots stopped — a disk error, a crashed service, a failed update. An event ID turns a mystery into a searchable, solvable problem and tells you whether you are fixing storage, services, or hardware.

  1. Press Win + R, type eventvwr.msc, and press Enter.
  2. Open Windows Logs > Application and look for errors timed to when snapshots stopped.
  3. Check Windows Logs > System for disk or service errors in the same window.
  4. Double-click any Recall- or store-related error and note its event ID and message.
  5. Search that event ID online or compare it against your symptoms to pick the right fix.

Closing

Missing Recall snapshots almost always trace back to a paused state, a full storage cap, or a filter doing its job a little too well. Work through the checks above and capture should resume cleanly. If a fresh snapshot store still will not record anything, that points to a deeper system problem — a corrupted Windows installation or failing drive — and it is worth having the hardware checked before you rely on Recall again.

Frequently asked questions

Where are Recall snapshots stored on my laptop?
Recall snapshots live only on your device’s system drive, encrypted and tied to your Windows sign-in. Microsoft does not upload them to the cloud, which is why there is no way to restore snapshots after they are deleted or the drive is wiped.
Does Recall automatically delete old snapshots?
Yes. When snapshots reach the maximum storage allocation you set, Recall deletes the oldest snapshots first to make room for new ones. Raising the storage cap keeps more history, at the cost of disk space.
Can I recover snapshots I deleted by accident?
No. Deleting snapshots — whether a date range or the whole store — is permanent. There is no recycle bin and no cloud backup, so only delete snapshots you are certain you will not need.
Why are snapshots missing only for certain apps?
Those apps or websites are almost certainly on your Recall filter list, or they were showing sensitive content that Recall’s content filter excluded. Check Settings > Privacy & security > Recall & snapshots > Filters and remove anything you want captured.