Preferences not saved: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
m (→‎Corrupt prefs.js file: added another forum reference)
Line 9: Line 9:
A corrupt [[prefs.js file]] can prevent preference changes from being saved.  [http://forums.mozillazine.org/viewtopic.php?f=38&t=892825] [http://forums.mozillazine.org/viewtopic.php?t=661250]  Close your Mozilla application and,
A corrupt [[prefs.js file]] can prevent preference changes from being saved.  [http://forums.mozillazine.org/viewtopic.php?f=38&t=892825] [http://forums.mozillazine.org/viewtopic.php?t=661250]  Close your Mozilla application and,
* If you have a current [[profile backup]],  replace the prefs.js file in your [[profile folder]] with the backup copy.  
* If you have a current [[profile backup]],  replace the prefs.js file in your [[profile folder]] with the backup copy.  
* If you have no backup,  open the profile folder and rename prefs.js to prefs.jsOLD.   
* If you have no backup,  open the profile folder and rename prefs.js to prefs.jsOLD.  A new prefs.js file will be generated when you next open your Mozilla application.  All preferences will be reset to default values but future changes will be saved.
A new prefs.js file will be generated when you next open your Mozilla application.  All preferences will be reset to default values but future changes will be saved.


==Other software prevents preference changes==
==Other software prevents preference changes==

Revision as of 13:42, 21 October 2008

This article deals with changes to options or preference settings not being saved after you restart your Mozilla application. If Firefox toolbar customizations are not being saved, see this article.

Read-only or locked preference file

The inability to save any preference changes can be caused by having a read-only or locked prefs.js file or "prefs.js.moztmp" file in the profile folder. You may receive an error similar to "Failed to save the preferences file. Any preference changes will be lost at the end of the session" [1]. You may also find multiple files named "prefs-<n>.js" (where <n> is a number) in the profile folder. Check the file properties of the prefs.js file (and "prefs.js.moztmp" file, if found) and make sure that the "read-only" attribute is not set. You can also delete any "prefs-<n>.js" file copies.

See Multiple profile files created for more information about locked or multiple files in the profile.

Corrupt prefs.js file

A corrupt prefs.js file can prevent preference changes from being saved. [2] [3] Close your Mozilla application and,

  • If you have a current profile backup, replace the prefs.js file in your profile folder with the backup copy.
  • If you have no backup, open the profile folder and rename prefs.js to prefs.jsOLD. A new prefs.js file will be generated when you next open your Mozilla application. All preferences will be reset to default values but future changes will be saved.

Other software prevents preference changes

  • Dell Network Assistant can lock or "protect" the preferences file. If you have this program, try disabling or uninstalling it. [4]
  • McAfee Privacy Service can disable your Mozilla browser's popup blocker. If you use McAfee, you will need to select the option to block popup ads within the McAfee Security Center settings. See this article for details.
  • Norton 360 includes a "Firefox Privacy Cleanup" feature that, if enabled, overrides your Firefox Privacy settings and prevents you from keeping your Browsing History, Cookies or other private data between sessions. If you use Norton 360, deselect the "Firefox Privacy Cleanup" option in your Norton 360 settings. [5]
  • Various other computer "cleanup" programs can override your Mozilla browser's Privacy settings and remove private data. [6]

User.js file locks certain preferences

If you are able to change some preference settings but not others, look for a user.js file in your profile folder (Windows users, read this for help finding it). The user.js file does not exist by default; it is created by users and, in a few cases, by some software programs, so that certain settings get written back to the prefs.js file each time you restart your Mozilla application If you find a user.js file, either remove it from the profile folder or edit the file to remove any unwanted settings. See Resetting preferences for more information.

Other solutions

  • Problematic extensions can change to certain preferences settings, causing your changes not to be saved [7]. To see if an extension is causing the problem, try disabling your extensions or uninstall unneeded extensions and then make your preference changes.
  • The Standard diagnostic provides a basic troubleshooting guide if the preceding suggestions do not fix the problem.

See also

Locking preferences

External links

Preferences are not saved (Firefox Support)