We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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.

Avatar for Username

Buscar en Ayuda

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

Este tema ha sido archivado. Haz una nueva pregunta si necesitas ayuda.

How do I disable the Plugin check at startup in 17.0.2 esr?

  • 2 respuestas
  • 1 tiene este problema
  • 6 visitas
  • Última respuesta de gormil4

gormil4
gormil4
more options

In testing the latest 17.0.2esr I keep getting the plugin check at startup. Even logged in as a Standard user with no Admin rights I still get this page which makes no sense since Standard users do not have permissions to install software. This is supposed to be the Enterprise version of Firefox which in my mind means that all updates and controls are left to the dicretion of an Administrator and not an end user. Is this a bug in ESR? How do I eliminate this?

In testing the latest 17.0.2esr I keep getting the plugin check at startup. Even logged in as a Standard user with no Admin rights I still get this page which makes no sense since Standard users do not have permissions to install software. This is supposed to be the Enterprise version of Firefox which in my mind means that all updates and controls are left to the dicretion of an Administrator and not an end user. Is this a bug in ESR? How do I eliminate this?

Solución elegida

Looks like I got my answer here: http://kb.mozillazine.org/Plugin_scanning

Thanks

Leer esta respuesta en su contexto 👍 0

Todas las respuestas (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

This can happen if there are plugins installed that are block-listed by Mozilla.

gormil4
gormil4 Autor de la pregunta
more options

Solución elegida

Looks like I got my answer here: http://kb.mozillazine.org/Plugin_scanning

Thanks