You open Recall, ready to search your timeline, and instead of your snapshots you get a demand: sign in with a Microsoft account. You are already signed in — or you use a local account on purpose — and Recall refuses to proceed either way.

Here is the honest baseline: Microsoft requires a Microsoft account for Recall. That part is by design — sign-in gates access to the encrypted snapshot store, and a local-only account genuinely cannot enable the feature. But when you are signed in and Recall still asks, or the sign-in loop never completes, that is a fixable identity problem, not policy.

This guide gives you six fixes in order: confirm the requirement applies to you, repair the sign-in state, fix account mismatches, and clear corrupted identity data. If you are on a local account by choice, the guide also lays out your real options.

Why this happens

  • Signed in with a local account: Recall requires a Microsoft account. On a local-only Windows profile, the prompt is correct behavior — the feature cannot initialize without it.
  • Stale or expired sign-in token: Windows thinks you are signed in, but the cached token Recall checks has expired or corrupted, so the prompt reappears endlessly.
  • Multiple accounts confusing Recall: A personal Microsoft account, a work account, and a local profile on one PC can leave Recall checking the wrong identity.
  • Corrupted identity or credential state: Damaged entries in Credential Manager or the identity service make sign-in appear to succeed while Recall still sees you as signed out.
  • Work/school policy blocking Recall: Organization-managed devices can disable Recall via policy, and the account prompt is sometimes the surface symptom.
  • Windows Hello or PIN state broken: Recall ties snapshot access to Windows Hello sign-in. A broken PIN or Hello setup can cascade into account prompts.

How to fix it

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

Fix 1: Verify which account Windows is actually using

The prompt is legitimate on a local account — so first confirm what you are actually signed in with. Many “I am signed in” cases turn out to be a local profile with a Microsoft account only in the Store.

  1. Open Settings > Accounts > Your info. If it says “Local account”, Recall’s prompt is by design — skip to Fix 6 for your options.
  2. If it shows a Microsoft account email, note exactly which one — you will compare it against what Recall expects in Fix 3.
  3. Check Settings > Accounts > Email & accounts for stale or duplicate entries that could confuse the identity check.
  4. If the displayed account is correct and current, the sign-in token itself is the suspect — continue to Fix 2.

Fix 2: Sign out and back in to refresh the token

A stale cached token is the most common cause of the endless prompt on already-signed-in PCs. A clean sign-out/sign-in cycle forces Windows to issue a fresh one.

  1. Go to Settings > Accounts > Your info and sign out of the Microsoft account (choose the option that keeps your local profile data).
  2. Restart the PC — this clears cached identity state that a simple sign-out misses.
  3. Sign back in with the same Microsoft account and complete any verification prompts. If sign-in itself errors, Microsoft’s Windows support hub has the account troubleshooter.
  4. Open Recall. If the prompt is gone, the stale token was the entire problem.

Fix 3: Remove duplicate or conflicting accounts

When personal and work accounts coexist, Recall can check the wrong identity and keep asking. Simplify to one authoritative account.

  1. Open Settings > Accounts > Email & accounts and review every listed account.
  2. Remove old, duplicate, or unused Microsoft accounts — especially ones that match the email Recall seems to expect.
  3. If a work or school account is present and the device is organization-managed, check with IT whether Recall is policy-disabled before going further.
  4. Restart, confirm only the intended personal Microsoft account remains, and test Recall again.

Fix 4: Clear corrupted credentials and reset the sign-in state

Damaged credential vault entries can make sign-in look successful while Recall still fails its check. Clearing them forces a clean rebuild.

  1. Open Credential Manager from the Start menu and inspect Windows Credentials for stale Microsoft identity entries (Generic Credentials tied to MicrosoftAccount).
  2. Remove the obviously stale Microsoft account credential entries — Windows recreates them at next sign-in.
  3. If Recall-adjacent AI features also misbehave after cached-state corruption, the Copilot app cache clear fix uses the same clear-and-rebuild logic for the Copilot app.
  4. Sign out, restart, sign back in, and check whether Recall now accepts your account.

Fix 5: Repair Windows Hello and the PIN

Recall gates snapshot access behind Windows Hello. A broken PIN or Hello enrollment can surface as an account prompt rather than a Hello error, misleading the diagnosis.

  1. Go to Settings > Accounts > Sign-in options and check the status of PIN and Windows Hello.
  2. Remove the PIN and re-add it, then re-enroll fingerprint or face if you use them.
  3. Restart and sign in with the repaired Hello method.
  4. Open Recall — if the account prompt clears now, the broken Hello state was masquerading as a sign-in problem.

Fix 6: Decide your path on a local account

If you use a local account deliberately, no repair will make Recall work — the Microsoft account requirement is architectural. You have three honest options.

  1. Switch to a Microsoft account: In Settings > Accounts > Your info, choose “Sign in with a Microsoft account instead” and convert the profile — files and apps carry over.
  2. Keep local and skip Recall: If you prefer local-only, Recall simply is not available to you; the prompt will persist by design. Note that a missing NPU driver produces similar-looking Recall failures, so rule out code 28 driver issues before concluding it is purely the account.
  3. Use a secondary profile: Some users keep a local daily profile and a separate Microsoft-account profile just for Recall — workable but clunky, since snapshots are per-profile.
  4. If Click to Do’s Copilot drafting features are also gated the same way, the draft with Copilot missing fix covers the parallel sign-in dependency.

Closing

Recall’s Microsoft account requirement is real and non-negotiable — snapshots stay local, but sign-in gates the encrypted store. If you are signed in and still prompted, it is almost always a stale token, a conflicting account, or a broken Hello state, all fixable in minutes. On a local account, the prompt is telling the truth: convert the profile or accept that Recall is not for that setup.

Frequently asked questions

Does Recall really require a Microsoft account?
Yes. Microsoft requires sign-in with a Microsoft account to use Recall — it is part of how the feature gates access to the encrypted snapshot store. A local-only account cannot enable Recall, and this is by design, not a bug.
Are my Recall snapshots uploaded to Microsoft?
No. Snapshots are stored and processed locally on your Copilot+ PC. The Microsoft account requirement is for sign-in and feature gating; it does not mean your timeline is synced to the cloud.
Can I use Recall with a work or school account?
Recall is designed around personal Microsoft accounts on Copilot+ PCs. Work or school accounts managed by an organization may have Recall disabled by policy entirely.
I am signed in — why does Recall still ask?
Usually a stale sign-in token, a secondary account mismatch, or a corrupted identity state. The fixes below refresh the sign-in and clear the stuck prompt.