This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Updates wipe all data

  • 1 reply
  • 1 has this problem
  • 12 views
  • Last reply by sfhowes

paulbardsley2002
paulbardsley2002
more options

Hi We (my company) switched to ubuntu, and have been using Thunderbird for a year or so. We really like the app, but on more than one occasion, on launching Thunderbird we get the "This installation of Thunderbird has a new profile. It does not shore email..." message and all our emails and profiles are lost. I'm assuming this is when Thunderbird has been updated. Is there any way we can stop this from happening in the future? As I say, I'm new to ubuntu and don't really know any code, I just know I hate windows. Cheers Paul

Hi We (my company) switched to ubuntu, and have been using Thunderbird for a year or so. We really like the app, but on more than one occasion, on launching Thunderbird we get the "This installation of Thunderbird has a new profile. It does not shore email..." message and all our emails and profiles are lost. I'm assuming this is when Thunderbird has been updated. Is there any way we can stop this from happening in the future? As I say, I'm new to ubuntu and don't really know any code, I just know I hate windows. Cheers Paul

All Replies (1)

sfhowes
sfhowes
  • Top 10 Contributor
more options

It's unlikely that your data have been deleted, but rather TB has lost the location of the profile. You might be able to restore it by replacing a corrupt prefs.js:

https://support.mozilla.org/en-US/questions/1324156

and as the cited kb article suggests, changing the name of the profile to a non-default name can possibly avoid this happening again.