Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Updated to FireFox 11 and I keep getting "checking compatibility of add-on" when I start the browser.

  • 5 Antworten
  • 14 haben dieses Problem
  • 5 Aufrufe
  • Letzte Antwort von cor-el

more options

I just updated to FireFox 11 and whenever I start the browser, I get that annoying window that checks for the compatibility of add-ons.

I have looked around for solutions and have tried the following: 1. Deleting several extension files from the profile folder. 2. Going to about:config to disable the extension:checkcompatibility (does not exist there).

None of these worked.

I just updated to FireFox 11 and whenever I start the browser, I get that annoying window that checks for the compatibility of add-ons. I have looked around for solutions and have tried the following: 1. Deleting several extension files from the profile folder. 2. Going to about:config to disable the extension:checkcompatibility (does not exist there). None of these worked.

Ausgewählte Lösung

Did you try to delete the file prefs.js?

Which security software (firewall, anti-virus) do you have?

Some security software has virtualization features that can cause problems by protecting and restoring files in the Firefox profile folder.

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (5)

more options

Ausgewählte Lösung

Did you try to delete the file prefs.js?

Which security software (firewall, anti-virus) do you have?

Some security software has virtualization features that can cause problems by protecting and restoring files in the Firefox profile folder.

more options

Prefs.js didn't fix it. But the removal of user.js did. Thank you!

more options

You're welcome.

Do you know which line(s) in the user.js file were causing the problems?

A user.js file is only present if you or another extension or program have created such a file.

more options

No, sorry I don't. Without opening it, I just deleted that file expecting a new one would generate when I restart FireFox like the Prefs.

If I get the same issue again on the next FireFox update, I will look into it and post it.