This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ค้นหาฝ่ายสนับสนุน

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.

เรียนรู้เพิ่มเติม

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

  • 5 การตอบกลับ
  • 14 คนมีปัญหานี้
  • 5 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย 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.

วิธีแก้ปัญหาที่เลือก

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.

อ่านคำตอบนี้ในบริบท 👍 0

การตอบกลับทั้งหมด (5)

more options

วิธีแก้ปัญหาที่เลือก

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.