You changed your password — sensibly, after a security scare or a routine rotation — signed back in, opened Recall, and your timeline is empty. Weeks of snapshots that were there yesterday have vanished, and the timeline offers no error, just a blank stretch where your work used to be.

This is rarely a deletion. Recall snapshots live in an encrypted store that is unlocked by your sign-in credentials, and a password change can break that unlocking step.

This guide helps you tell them apart and recover what can be recovered: sign-in and Windows Hello checks first, then credential and encryption repair, and finally a clean restart of Recall if the old store is truly gone.

Why this happens

  • Snapshot encryption keys tied to old credentials: Recall encrypts snapshots with keys protected by your sign-in, so a password change that does not carry those keys forward leaves the store locked.
  • Credential reset instead of credential update: Some password changes, especially administrator resets, discard the old credential vault rather than re-encrypting it with the new password.
  • Windows Hello out of sync after the change: A PIN, fingerprint, or face sign-in that was set up under the old password may fail to unlock the snapshot store after the change.
  • Signed in with a different account: After a password change it is easy to land in a different Microsoft or local account, which has its own empty Recall store.
  • Recall paused by a security policy refresh: A password change can trigger a policy refresh that pauses snapshot saving or clears the timeline view until you re-confirm Recall settings.
  • Corrupted credential vault entry: A partially completed password change can leave a damaged vault entry that blocks Recall without affecting ordinary sign-in.

How to fix it

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

Fix 1: Confirm you are in the right account

This is the fastest win and the most embarrassing miss: a different account means a different, empty Recall timeline. Rule it out before touching encryption or keys.

  1. Open Settings > Accounts and confirm the account shown is the one that owned the missing snapshots.
  2. Check whether you have both a Microsoft account and a local account on the PC, and sign out and back in with the original one if needed.
  3. Open Settings > Privacy & security > Recall & snapshots and check the storage figure — a non-zero figure with an empty timeline points to a locked store, not a missing one.
  4. If the storage figure is zero, the store may genuinely be empty; still complete Fix 2 before concluding that.

Fix 2: Re-establish Windows Hello after the password change

Windows Hello is the key that unlocks Recall’s store on most Copilot+ PCs.

  1. Open Settings > Accounts > Sign-in options and check the state of Windows Hello PIN, fingerprint, and facial recognition.
  2. Remove the existing PIN, then set a new PIN under the new password when prompted.
  3. Re-add fingerprint or face recognition if you use them, completing the full setup prompts.
  4. Restart the PC, sign in with Windows Hello, and open Recall immediately — the store unlocks at sign-in.

Fix 3: Repair the credential vault and sign-in chain

When Hello alone does not restore the timeline, the credential vault itself may hold a stale entry from before the password change.

  1. Sign out of the Microsoft account in Settings > Accounts > Your info, then restart the PC.
  2. Sign back in with the new password, completing any verification prompt exactly as shown.
  3. Open Credential Manager from the Control Panel and look for obviously stale Windows credentials tied to the old sign-in, removing only entries you recognise as duplicates.
  4. Restart again, sign in with Hello, and check Recall — a rebuilt vault often unlocks the store on this second sign-in.

Fix 4: Check Recall settings, storage, and pause state

A policy refresh after a password change can pause Recall or hide its timeline without touching the data.

  1. Open Settings > Privacy & security > Recall & snapshots and confirm Save snapshots is On.
  2. Confirm Recall is not paused, filtered to a narrow date range, or limited to a different set of apps than before.
  3. Scroll the timeline without any search or filter to check whether older snapshots are present but hidden by a filter.
  4. Note the storage figure again — if it has not changed since Fix 1, the data is still on disk and the problem is access, not deletion.

Fix 5: Test whether the old store is recoverable or truly lost

At this point you need an honest verdict: locked or lost.

  1. Create a test snapshot by opening an app and waiting for Recall to capture it, then confirm the new snapshot appears in the timeline.
  2. If new snapshots work but old ones do not, the old keys are almost certainly unrecoverable — the store is intact for new data only.
  3. If even new snapshots fail, Recall itself is damaged, not just the old store — move to Fix 6 rather than deleting anything.
  4. Search Recall with no filters for a keyword you know appeared in an old snapshot; a complete absence confirms the old store is unreadable.
  5. Accept the verdict before acting: resetting a locked-but-present store destroys any remaining chance of a future key recovery — see Microsoft’s Windows support pages .

Fix 6: Reset Recall cleanly and protect the new store

If the old snapshots are confirmed unrecoverable, a clean reset gives you a healthy timeline going forward and stops the empty-store confusion. This step also applies when an account switch creates the same symptom, as explained in Recall not working after an account switch , and a related linking fault is covered in Link to Windows problems on ARM laptops . A different click-action fault with its own reset path is described in Click to Do open with not working .

  1. Open Settings > Privacy & security > Recall & snapshots and delete the existing snapshots.
  2. Restart the PC, sign in with Windows Hello, and confirm Save snapshots is On.
  3. Use the PC normally for a few hours, then verify new snapshots appear and survive a restart.
  4. Record your new password in a password manager and avoid administrator password resets where possible — they are the resets most likely to discard Recall keys.
  5. Going forward, change passwords through the normal account settings path rather than a forced reset, so Windows can re-encrypt the credential vault instead of discarding it.

Closing

Missing Recall snapshots after a password change usually mean locked keys, not deleted data — so check the account, rebuild Windows Hello, and verify the storage figure before you delete anything. If the old store proves truly unreadable, a clean reset restores a healthy timeline, and changing passwords through the normal path protects it next time.

Frequently asked questions

Why would changing my password delete Recall snapshots?
It should not delete them directly, but Recall snapshots are encrypted with keys tied to your sign-in credentials. If the new credentials fail to unlock the old keys, Recall cannot read the snapshots and they appear missing.
Can I recover snapshots after a Microsoft account password change?
Sometimes, yes — if you sign back in with the same account and Windows Hello unlocks the credential store cleanly. If the keys were reset during the change, the old snapshots may be permanently unreadable.
Does changing a local account password affect Recall?
Yes, it can. Recall encryption is tied to your Windows sign-in, so a local password change that resets credentials rather than updating them can break access to the existing snapshot store.
Should I delete snapshots if they will not come back?
Only after you have tried the sign-in and Hello fixes in this guide. Deleting the store is irreversible, so confirm the snapshots are truly unreadable before clearing them for a fresh start.