Data loss with new update

Title: Lost all conversation history, pinned chats, and knowledge graph data — Amazon Quick Desktop (Windows)

Body:

I’ve lost all of my Amazon Quick desktop conversation history. This includes:

  • All pinned conversations (I had multiple active projects)
  • Full conversation history and context
  • Knowledge graph data (projects, entities, relationships)
  • Any saved agent files from past sessions

The only conversations visible now are from today — everything prior is gone. There are no deleted conversations in the recovery queue either.

I did not perform a manual data reset or clear data from Settings. I’m unsure what caused this — possibly an app update or profile migration.

I checked the local sessions database (xxx) and confirmed:

  • The database was created on August 31, 2026
  • It contains only 3 sessions (all from today) and 16 messages
  • Zero deleted conversations exist
  • The profile ID is xxx — a previous profile may have existed with my data

This is a significant loss as those conversations contained extensive iterative work across multiple projects.

Questions:

  1. Is there any way to recover data from a previous profile?
  2. Is conversation data backed up server-side?
  3. Has anyone else experienced this after an update?

Platform: Windows

Hi @atijason and welcome to the Quick Community!

This could be more of a profile switch rather than actual data loss. Amazon Quick Desktop stores everything locally under C:\Users\<username>\.quickwork\profiles\<profile-id>\. Each sign-in identity gets its own profile folder, and updates can sometimes create or switch to a new profile, which makes it look like a fresh install. The fact that your sessions database was created on August 31 with only today’s conversations confirms this is what happened.

To recover, close Amazon Quick completely and navigate to C:\Users\<username>\.quickwork\profiles\. You should see at least two profile folders there. Check the size of each. The larger one contains your full history, knowledge graph, and agent files. Once you’ve identified the old (larger) profile, back up the new profile’s contents first (rename it or copy it elsewhere), then copy the entire contents of the old profile folder into the new one. This ideally should restore everything.

To answer your other questions: conversation data on Quick Desktop is stored locally only with no server-side backup, and yes, quite a few people have run into this exact issue after updates. If the steps above don’t resolve it, I’d recommend opening an AWS Support case where the team can dig into the specifics of your setup.

Hope this helps!