Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

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

How to stop Firefox from checking for add-on compatibility every time it opens?

  • 2 tontu
  • 4 am na jafe-jafe bii
  • 25 views
  • i mujjee tontu mooy Dummy88

more options

How to stop Firefox from checking for add-on compatibility every time it opens?

How to stop Firefox from checking for add-on compatibility every time it opens?

Saafara biñ tànn

That can be a problem with the compatibility.ini file in the Firefox profile folder. Try to rename (or delete) the compatibility.ini file in the Firefox profile folder to see if that helps.

You can use this button to go to the currently used Firefox profile folder:

You can also check for problems with preferences.

Delete possible user.js and numbered prefs-##.js files and rename (or delete) the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in the current Firefox release.

Jàng tontu lii ci fi mu bokk 👍 1

All Replies (2)

more options

Saafara yiñ Tànn

That can be a problem with the compatibility.ini file in the Firefox profile folder. Try to rename (or delete) the compatibility.ini file in the Firefox profile folder to see if that helps.

You can use this button to go to the currently used Firefox profile folder:

You can also check for problems with preferences.

Delete possible user.js and numbered prefs-##.js files and rename (or delete) the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in the current Firefox release.

more options

Deleting all the .js files in the profile cleared all the session start problems that I was experiencing following the update to 34.0.5