Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Søg i 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.

Læs mere

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

  • 2 svar
  • 4 har dette problem
  • 20 visninger
  • Seneste svar af 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?

Valgt løsning

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.

Læs dette svar i sammenhæng 👍 1

Alle svar (2)

more options

Valgt løsning

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