Mozilla will shut down Pocket’s services on July 8, 2025. At that time users will no longer be able to access the Pocket website, apps and API. You can export your saved items and API data until October 8, 2025 before they are permanently removed. For more information, see this article.

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 replies
  • 4 have this problem
  • 30 views
  • Last reply by Dummy88

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?

Chosen solution

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.

Read this answer in context 👍 1

All Replies (2)

Chosen Solution

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.

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