Copilot conversation corrupted after update

Export the Copilot activity history immediately, then report the inaccessible conversation from Copilot so Microsoft can investigate the account-side migration or loading failure.

1. Preserve the conversation data

For a personal Microsoft account:

1. Sign in to the Microsoft privacy dashboard using the same account used for that conversation.
2. Open Privacy → Empower your productivity → Copilot → Your Copilot app activity history → Copilot apps.
3. Select Export all activity history.
4. Save the downloaded CSV somewhere safe and check whether it contains prompts and responses from the inaccessible conversation.

The export is non-destructive; do not select Delete all activity history. Microsoft documents the export as the supported way to obtain a copy of Copilot app activity history.^1^

The export may preserve the text but is not documented as a way to restore the conversation inside Copilot.

2. Report the failed conversation

Since refreshing has already failed:

1. Keep a copy of the conversation URL shown in Edge.
2. In Copilot, select … in the upper-right corner.
3. Select Send feedback → Report a problem.
4. Include:
   • “Unable to load the content” for one specific conversation.
   • The approximate date the conversation began and when it last opened successfully.
   • That it stopped loading after the updated Copilot experience appeared.
   • Whether the same failure occurs in both the Windows app and web version.
   • Windows and Edge versions.
   • The screenshot and conversation URL.
   • Whether the conversation appears in the exported activity file.

This is Microsoft’s documented escalation path for content problems in the updated Copilot app.^2^

3. Check the migration state without changing data

Microsoft says chats automatically move to the updated app, but migration can take time and may temporarily leave content unavailable.^2^

Check these conditions once:

• Confirm Copilot is signed in with the exact original sign-in method. For example, if the chat was created using Continue with Google or Continue with Apple, use that same button rather than entering the address through another sign-in route.
• If multiple personal accounts are involved, open a new private browser session, visit copilot.microsoft.com, and sign in with the original account. If it remains on the older experience, check whether the conversation opens there; if redirected to copilot.com, that account has moved or is completing migration.^2^
• Use any in-app link offered for accessing previous chats while migration completes.

Do not delete the history, reset the account, or remove the visible history entry while recovery is being investigated. Copilot normally retains the last 18 months of interactions, so a conversation running for approximately one year can still fall within the documented retention window, although its oldest messages may depend on their individual dates.^3^

There is no documented user-side command that repairs one conversation that remains listed but cannot load. If it does not return after migration finishes, the feedback report—with the URL, screenshot, timestamps, and export result—is the appropriate route for backend investigation.

References

1. Manage your Copilot activity history in the privacy dashboard | Microsoft Support
2. Troubleshoot Your Content in the Updated Copilot App | Microsoft Support
3. Conversation history in Microsoft Copilot | Microsoft Support