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.

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

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

Every time I start up Firefox, it checks for plugin updates. All my plugins are up to date, but it continues to load the plugin site. How do I make it stop?

  • 2 fhreagra
  • 26 leis an bhfadhb seo
  • 4 views
  • Freagra is déanaí ó cor-el

more options

Starting on Fri. 6/10/11, every time I start up Firefox 3.6.17, it loads the plugin update site. Initially, it said my Adobe reader plugin was out of date. Therefore I updated that plugin, yet that did not fix the problem. So I was finally forced to disable the plugin. After doing this, the plugin updates check still runs every time I start FF. However, they all come back up to date.

So my question is how do you make this plugin update check stop running. I had made no changes to firefox prior to this.

Starting on Fri. 6/10/11, every time I start up Firefox 3.6.17, it loads the plugin update site. Initially, it said my Adobe reader plugin was out of date. Therefore I updated that plugin, yet that did not fix the problem. So I was finally forced to disable the plugin. After doing this, the plugin updates check still runs every time I start FF. However, they all come back up to date. So my question is how do you make this plugin update check stop running. I had made no changes to firefox prior to this.

All Replies (2)

more options

There's a fault with the blocklist.xml file which was updated on Friday, it should be fixed on Monday and you should get the updated file on Monday or Tuesday.

more options

You can fix this problem with forcing the file blocklist.xml to update.

That update will remove the severity="0" flags in the file that cause the problems.

See: