Avast not installing Firefox protection

Hi. I noticed the latest version of Avast and Firefox having issues. The Avast web protection and web reputation extensions are not there. When opening Firefox it never prompted me to enable any of the Avast extensions. This is with both Windows 7 and Windows 8. The Avast extension does show up in Internet Explorer. Help getting the extensions loaded in Firefox is greatly appreciated. Thank you!

Today the extension was detected and installed by Firefox, but now when I click on the “Settings Page” associated with Avast I get a blank page “avast://settings.” Also a “Launch Application” prompt comes up in Windows 8 saying “This link needs to be opened with an application. Choose An Application. Send to:”

What’s the deal?

Any Avast tech support staff out there? Thanks!

Same here on 4 computers running various versions of Windows.

I can get Avast to load in Firefox but the extension still doesn not do anything. It always says that there are zero website tracking me.

Avast browser protection is just not compatible with the latest version of Firefox yet.

I have actually disabled the extension on all 4 computers because Until avast fixes it there is absolutely no reason using the extension.

There is really no reason to even use this extension, WOT is based on users and is better…

But to troubleshoot go type about:addons in to the address bar and go to Avast! WebRep. Enable it if it is disabled. Check for updates. If it is still not working, disable it again and find some other kind:

  1. WOT- WebRep with a larger community
  2. Adguard Adblocker- Ad Blocker with Malicious and Phishing Website Block
  3. Do Not Track Me- An Anti-Track extension

WebRep has never (yes never) blocked any access while WOT has saved me from a malicious site already. WOT marked a real malicious site red while WebRep marked it green!

Same section can be accessed via Tools, Addons in Firefox and there’s no “updating” it. The main reason to get this fixed it to disable that price/shop baloney. Regardless (good or bad feature) it’s an obvious issue that needs addressed.

Works fine for me on Firefox 29.