An application or feature powered by Windows Copilot to assist users with tasks and productivity
Microsoft does not document a user-facing command to resync or restore one Copilot conversation, so check for the migration-only legacy-chat link, preserve the available records, and escalate the specific conversation for back-end investigation.
Check the migration access link
If Copilot displays a “coming soon,” migration, or content-moving message, open any link in that message for accessing existing or previous chats, then try the affected conversation there. Microsoft documents this as the temporary access path while content is still moving. Migration duration can vary with the amount and type of content involved.^1^
If no such message or link appears, there is no documented way to trigger it manually.
Preserve what is still available
- Do not delete the conversation or clear Copilot activity history. Deletion controls can remove individual chats or the entire history.^2^
- Save:
- A screenshot showing the conversation title in the history list.
- A screenshot of “Unable to load the content.”
- The conversation URL, copied from the browser address bar if one exists.
- The approximate date and time it last opened successfully.
- The migration/update date and the date the failure began.
- If this is a personal Microsoft account, export the account’s Copilot activity:
- Open the Microsoft privacy dashboard.
- Go to Privacy → Empower your productivity → Copilot → Your Copilot app activity history.
- Select Copilot apps → Export all activity history.
Microsoft states that signed-in Copilot conversation history retains the last 18 months of interactions. However, the fact that this chat remains listed does not prove that its complete content is currently retrievable or that it can be restored.^2^
Escalate the existing failure, not local troubleshooting
Since the same chat fails in the Windows app, web client, and Incognito while other chats migrated, further sign-in, refresh, or browser-cache troubleshooting is unlikely to distinguish the problem.
If the earlier Support contact produced a case, update that case; otherwise open a support case. Include this wording:
One specific legacy Copilot conversation remains visible in history but returns “Unable to load the content” in both the Windows app and web client after migration. Other conversations migrated successfully. Please investigate the conversation’s back-end migration/indexing state and determine whether it can be reprocessed, resynchronized, or restored.
Affected conversation title: [title]
Conversation URL or identifier: [URL, if available]
Last opened successfully: [date/time/time zone]
Failure first observed: [date/time/time zone]
Account type and sign-in method: [personal Microsoft/Google/Apple or work/school]
Clients tested: Windows app, web, private browsing
Feedback submission dates/IDs: [details]
Attach the screenshots and ask whether the feedback IDs can be associated with the support case. Microsoft’s reporting guidance specifically requests the start time, device and operating system, and a screenshot.^1^
For a work or school account, ask the Microsoft 365 administrator to check Health → Service health and open a service request through Help & Support in the Microsoft 365 admin center. Copilot interaction data for organizational accounts is stored and can be searched by authorized administrators using Microsoft Purview, subject to the organization’s retention policies and permissions.^4^
What is and is not currently established
- Microsoft says chats and most eligible content should migrate automatically, while migration can take time and functionality gaps can occur during rollout.^5^
- Similar reports exist for individual old chats failing after an update, but the available public Q&A cases do not contain an accepted or recommended resolution.^6^
- There is no public confirmation here of an active incident specifically affecting oversized conversations.
- No documented self-service resync, reindex, or single-chat restore process is available. Support can investigate the back-end state, but repair or restoration is not guaranteed.
References
- Troubleshoot Your Content in the Updated Copilot App | Microsoft Support
- Conversation history in Microsoft Copilot | Microsoft Support
- Manage your Copilot activity history in the privacy dashboard | Microsoft Support
- Data, Privacy, and Security for Microsoft Copilot
- Copilot App Updates for Personal, Work, and School Accounts | Microsoft Support
- After a recent update of Copilot it cannot load an old chat