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.

Webroot oking checkmark of website gone after firefox removed addon? How do I get this back?

  • 1 respuesta
  • 1 tiene este problema
  • 1 visita
  • Última respuesta de the-edmeister

jlbarker
jlbarker
more options

I received a notice popup that Firefox was removing an add on from Webroot. When I went to my search engine I noticed that the green check mark that Webroot would put up to indicate that this was a safe site was gone. I assume that since this has never before been a problem that the removal by Firefox of this "add on" is what is causing this. FYI- If I go on I.E., I do not have this problem

I received a notice popup that Firefox was removing an add on from Webroot. When I went to my search engine I noticed that the green check mark that Webroot would put up to indicate that this was a safe site was gone. I assume that since this has never before been a problem that the removal by Firefox of this "add on" is what is causing this. FYI- If I go on I.E., I do not have this problem

Todas las respuestas (1)

the-edmeister
the-edmeister
  • Moderator
more options

Did Firefox actually remove that Webroot add-on, or is it disabled now?

If an add-on isn't up-to-date for the latest version of Firefox, it will be disabled. All that's needed is that add-on needs to be updated, either by the program that installed that add-on (Webroot in this case) or by the user manually.

Right-click that add-on (if it's in the Addons Manager) and use Find Updates. Hopefully the developer of the add-on didn't disable that standard feature of the Addons Manager.