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

Avatar for Username

Etsi tuesta

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.

Lue lisää

Ketju on arkistoitu. Esitä kysymys, jos tarvitset apua.

Thunderbird does not accept changes (140.1.1esr)

  • 1 vastaus
  • 0 henkilöllä on sama ongelma
  • 59 näyttöä
  • Viimeisin kirjoittaja Matt
  • Arkistoitu

Enzo Baldazzi
Enzo Baldazzi

Hi,

since Thunderbird updated to version 140.1.1esr, the changes I made (language changes, display settings, etc.) aren't permanent. That is, every time I close and reopen Thunderbird, the changes disappear.

I disabled my antivirus, but it didn't help.

I found an online guide that suggested checking to make sure the "prefs.js" file wasn't read-only, which it isn't. I have several "prefs" files, but the most recent one is from 2024!

Thanks for any help!

EB

Hi, since Thunderbird updated to version 140.1.1esr, the changes I made (language changes, display settings, etc.) aren't permanent. That is, every time I close and reopen Thunderbird, the changes disappear. I disabled my antivirus, but it didn't help. I found an online guide that suggested checking to make sure the "prefs.js" file wasn't read-only, which it isn't. I have several "prefs" files, but the most recent one is from 2024! Thanks for any help! EB

Kaikki vastaukset (1)

Matt
Matt
  • Top 25 Contributor

The appearance of multiple prefs.js files (numbered) is indicative of an issue with contention. That is, another activity is preventing access to the file for it to be saved on shutting down Thunderbird. Hence the recommendation that the antivirus be disabled as it is the most frequent at accessing files at the same time as Thunderbird. However having the files on a remote location, either through a network device or some form of cloud sync is frequently a cause these days. The cottage industry that has sprung up for synced home drives with Microsoft or Google is really a mess.

Other causes can include the power just being pulled as a method of shutting the system down so the changes never get saved (this does not make numbered files, but you have had no new ones in years apparently), the system security blocking writes to the location used to store the profile, incremental backups of the file system and I am sure other things I have not thought of.