You ask Copilot a follow-up question, and it responds like you’ve never spoken — no memory of the project you described or the preferences you set. The history panel is empty, and every conversation starts from zero. For a tool that’s supposed to learn your context, this amnesia makes it feel broken.
Copilot’s memory is a chain: signed in, history enabled, personalization allowed, uncorrupted app data. Break any link — a reset toggle, a second account, a corrupt cache — and Copilot forgets everything. Old privacy settings can quietly block recall too.
This guide rebuilds that chain link by link, from quick settings checks to deeper repairs. Work through the fixes in order and test with a simple check — tell Copilot your name, start a new chat, and ask if it remembers. One of these steps will bring its memory back.
Why this happens
- Chat history is turned off: one toggle controls whether Copilot saves anything; when off, every session is amnesiac by design.
- You’re signed in with a different account: memories belong to one Microsoft account, so a second account starts blank.
- Personalization is disabled: long-term memory needs explicit permission to store facts about you across sessions.
- The app’s local data is corrupted: a damaged cache can block history from loading even when the server has it.
- An update reset your settings: Copilot app updates occasionally flip history or privacy toggles back to defaults.
- You’re using Copilot without signing in: anonymous sessions deliberately keep no history and no memory between chats.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Turn chat history and memory back on
The most common cause is also the fastest fix: the history toggle got switched off after an update or someone else’s settings change. With history off, Copilot is brilliant within one chat and blank in the next. Re-enable it, and also check the separate memory toggle for cross-session recall.
- Open the Copilot app and go to Settings.
- Find the chat history option and turn it on.
- Find the personalization or memory option and turn it on.
- Send Copilot a test fact, like your favorite programming language.
- Start a new chat and ask about it to confirm memory works.
Fix 2: Make sure you’re on the right account
Memory is per-account, so the wrong Microsoft account looks exactly like amnesia — your history exists under a different login. If sign-in bounces you back to the login screen, fix the Copilot login loop on Windows 11 first; no memory feature works until sign-in is stable.
- In Copilot, open your profile and note the signed-in email address.
- Compare it with the account where your history used to appear.
- Sign out completely, then sign back in with the correct account.
- Check the history panel for your old conversations.
- If sign-in loops, resolve the login loop before continuing here.
Fix 3: Clear corrupted local data without losing server history
Sometimes the server has your history but the app can’t display it — history works at copilot.microsoft.com but not in the Windows app. Clearing local data forces a fresh download from Microsoft’s servers. Saved chats live in the cloud, so this doesn’t delete them.
- Test your history at copilot.microsoft.com in a browser first.
- If the browser shows history, open Settings > Apps > Installed apps.
- Find Microsoft Copilot, open Advanced options, and click Repair.
- If history still won’t load, return and click Reset.
- Reopen Copilot, sign in, and verify the history panel populates.
Fix 4: Review privacy settings that block recall
Windows 11 and Copilot privacy controls can silently disable memory — a toggle flipped months ago can break recall today, and Family Safety restricts memory on child accounts. Microsoft documents these controls on the official Windows support page .
- In Copilot Settings, confirm personalization and memory are enabled.
- Open Windows Settings > Privacy and security and review related toggles.
- For a family-managed account, ask the organizer to check restrictions.
- Turn the memory feature off and back on to refresh consent.
- Test with a new fact and a brand-new chat session.
Fix 5: Update or reinstall the Copilot app
Updates sometimes ship broken history sync or reset memory settings themselves. If Copilot forgot everything right after an update, the update is the likely culprit. A clean reinstall replaces damaged components — much like when an NPU disappears after a Windows update and the supporting stack needs rebuilding.
- Open the Microsoft Store and install any pending Copilot update.
- Test memory after updating — many sync bugs are fixed this way.
- If it still fails, uninstall Copilot from Settings > Apps.
- Restart the laptop, then reinstall Copilot from the Microsoft Store.
- Sign in, re-enable history and personalization, and test.
Fix 6: Rule out system performance issues masking as memory loss
Sometimes Copilot fails to load history because the system is too bogged down to complete the sync — heavy AI workloads, a bad NPU driver, or memory pressure can empty the history panel while the data is fine. A faulty NPU driver can even cause game stutter on AI PCs ; fixing performance often restores memory as a side effect.
- Open Task Manager and check CPU, memory, and NPU usage.
- Close heavy background apps and browser tabs, then reopen Copilot.
- Install any Windows updates that include driver fixes.
- If the NPU shows errors in Device Manager, update its driver.
- Retest Copilot’s history once the system runs smoothly.
Closing
Copilot’s memory is a chain: the right account, history enabled, personalization allowed, and healthy app data. Walk it from Fix 1 to Fix 6 to find the broken link. Once recall works, export important conversations periodically as cheap insurance.
