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!

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

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

This thread was archived. Please ask a new question if you need help.

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

  • 2 replies
  • 1 has this problem
  • 6 views
  • Last reply by 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?

Chosen solution

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

Thanks

Read this answer in context 👍 0

All Replies (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 Question owner
more options

Chosen Solution

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

Thanks