Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

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.

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

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

All Replies (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.