Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

"Plugin Check" page comes up every time I open Firefox. How do I stop this?

  • 4 antwoorden
  • 64 hebben dit probleem
  • 1 weergave
  • Laatste antwoord van cor-el

more options

Every single time I open Firefox, the "Plugin Check" page opens in a second tab. I do not need to check my plugins. They're all up to date. Why does this page continue to come up and how do I stop it from opening?

Every single time I open Firefox, the "Plugin Check" page opens in a second tab. I do not need to check my plugins. They're all up to date. Why does this page continue to come up and how do I stop it from opening?

Alle antwoorden (4)

more options

Type about:config in the URL bar and hit Enter.
If you see the warning, you can confirm that you want to access that page.

Pref = plugins.update.notifyUser -- if it shows as True, double-click that pref to toggle it to False

more options

I've tried the suggestion of using the settings in "about:config" and the plugin tab still appears every time. I may resort to calling in Mozilla.

more options

Actually when I toggled every link with the world "plugin" to False it seemed to work.

more options

You can correct this issue by forcing the file blocklist.xml to update or wait until Firefox updates the file.
That update will remove the severity="0" flags in the file that cause the problem.

See:

  • Bug 663722 - The blocklist output is including severity="0" where it shouldn't be