Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Why am I forced to update?

  • 4 antwurd
  • 1 hat dit probleem
  • 3 werjeftes
  • Lêste antwurd fan James

more options

After the forced update, some plugins have failed! I just want to stay at 56, why is it forced to update to the latest version every time? Why not give a manual update, so forced, secretly updated like this?!!! ...

After the forced update, some plugins have failed! I just want to stay at 56, why is it forced to update to the latest version every time? Why not give a manual update, so forced, secretly updated like this?!!! ...

Bewurke troch James op

Alle antwurden (4)

more options

Information has been posted for repairing most Firefox versions old and new.

https://support.mozilla.org/en-US/questions/1258165#answer-1218833 fixed the issue for my v54.

more options

Did you enable "Resist Fingerprinting" (troubleshooting data shows: Firefox 60 ESR on Windows 7)?

You can check this pref on the about:config page to see if resist fingerprinting (RFP) is enabled and if this pref is user set (bold) reset to false via the right-click context menu.

  • privacy.resistFingerprinting = false

See also:


There has been an unfortunate incident with an intermediate certificate that had expired recently and this certificate was used to verify the signatures of extensions hosted on the Add-ons website. This expired intermediate certificate caused Firefox to distrust and disable all installed extensions. There have been Firefox updates released to address this issue (66.0.5 and 60.6.3 ESR).

more options

Although change can be understandably frustrating, updates are an important part of staying safe when browsing the internet. Updates contain fixes for hundreds of security and privacy flaws, not to mention great features that are added.

<strike>In your case, the plugins stopped working because Firefox no longer supports NPAPI plugins. Plugins are a massive security risk and performance hindrance. None of the major internet browsers support this outdated technology anymore.</strike>

EDIT: The user is likely referring to extensions, not "plugins".

Bewurke troch Wesley Branton op

more options

Wesley Branton said

In your case, the plugins stopped working because Firefox no longer supports NPAPI plugins.

The OP was very likely referring to Extensions.

The Flash Player Plugin from Adobe has been the only NPAPI Plugin allowed to run since Firefox 52.0 Release.

Though the Flash Player Plugin (NPAPI) will be allowed under increasing restrictions over time. https://developer.mozilla.org/en-US/docs/Plugins/Roadmap