Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus
Ouvert

History being wiped whenever Firefox updates

Firefox Récupérer des données
jbr a répondu
safetykittenjake
safetykittenjake

So, whenever my Firefox updates, it seems that it completely wipes my history, and deletes all my tabs, despite it being set to "re-open previous tabs on launch".

This has happened multiple times now and is really not fun. Do I just need to make bookmark folders for everything I do? Because having everything randomly delete itself, without even a session restore in the backups folder of my firefox profile, isn't ideal.

I do have a sessionstore error for this, where I presume the problem is laid out.

1784409622095 SessionStore WARN SessionWriter.write, Caught exception:: NotFoundError: Could not move `C:\Users\SUCKS TO SUCK\AppData\Roaming\Mozilla\Firefox\Profiles\sphzxgst.dev-edition-default\sessionstore.jsonlz4' to `C:\Users\SUCKS TO SUCK\AppData\Roaming\Mozilla\Firefox\Profiles\sphzxgst.dev-edition-default\sessionstore-backups\previous.jsonlz4': source file does not exist (NS_ERROR_FILE_NOT_FOUND) No traceback available 1784409622095 SessionStore ERROR Could not write session state file : NotFoundError: Could not move `C:\Users\SUCKS TO SUCK\AppData\Roaming\Mozilla\Firefox\Profiles\sphzxgst.dev-edition-default\sessionstore.jsonlz4' to `C:\Users\SUCKS TO SUCK\AppData\Roaming\Mozilla\Firefox\Profiles\sphzxgst.dev-edition-default\sessionstore-backups\previous.jsonlz4': source file does not exist (NS_ERROR_FILE_NOT_FOUND) No traceback available

So, whenever my Firefox updates, it seems that it completely wipes my history, and deletes all my tabs, despite it being set to "re-open previous tabs on launch". This has happened multiple times now and is really not fun. Do I just need to make bookmark folders for everything I do? Because having everything randomly delete itself, without even a session restore in the backups folder of my firefox profile, isn't ideal. I do have a sessionstore error for this, where I presume the problem is laid out. 1784409622095 SessionStore WARN SessionWriter.write, Caught exception:: NotFoundError: Could not move `C:\Users\SUCKS TO SUCK\AppData\Roaming\Mozilla\Firefox\Profiles\sphzxgst.dev-edition-default\sessionstore.jsonlz4' to `C:\Users\SUCKS TO SUCK\AppData\Roaming\Mozilla\Firefox\Profiles\sphzxgst.dev-edition-default\sessionstore-backups\previous.jsonlz4': source file does not exist (NS_ERROR_FILE_NOT_FOUND) No traceback available 1784409622095 SessionStore ERROR Could not write session state file : NotFoundError: Could not move `C:\Users\SUCKS TO SUCK\AppData\Roaming\Mozilla\Firefox\Profiles\sphzxgst.dev-edition-default\sessionstore.jsonlz4' to `C:\Users\SUCKS TO SUCK\AppData\Roaming\Mozilla\Firefox\Profiles\sphzxgst.dev-edition-default\sessionstore-backups\previous.jsonlz4': source file does not exist (NS_ERROR_FILE_NOT_FOUND) No traceback available

Toutes les réponses (1)

jbr
jbr
  • Les 10 premiers contributeurs

How do the other timestamps look like in your profile folder? No other issues with the roaming profile, or the system in general? Was the error captured above really meant to happen on the timestamp logged, which presumably is mid–July?

Notably the sessionstore files and folders do not contain history, that's in places database — so if you're losing both, there's wider profile directory corruption going on than a single feature–specific issue:(

Could you open a bug to make sure engineers can get in touch with you in case they'd want to inspect the profile data or logs more closely, so this is tracked?

If you're having repeated problems with the updater writing the roaming location, consider using the Microsoft Store–provided Firefox installation, which, while having also the same opaque profile folder handling as the roaming profiles, manages the updates on its own, so these should be completely invisible to the actual browser.

Poser une question

Vous devez vous identifier avec votre compte pour répondre aux messages. Veuillez poser une nouvelle question, si vous n’avez pas encore de compte.