Avast Browser Addon not verified (Firefox 50.0, Addon 12.0.88)

[REDACTED]

Wont load.
Computer formatted today.
Fresh Install of Windows, Firefox and Avast.

And here's the results: (Screenshots) https://goo.gl/photos/SPEMYVtuuSJZ44bFA

There's no enable button, and since Firefox 48, the xpinstall.signatures.required "False" flag has been disabled and no longer works.

Any ideas?

[Eddy]

Just as information: https://wiki.mozilla.org/Add-ons/Extension_Signing

[DavidR]

What avast version are you using ?
Avast 12.3.2280 is the latest and that may reflect if your Avast Browser Add-on is signed or not.

[MrMaxaMan]

Same problem for me. After the WOT privacy issues I tried to install the Avast browser addon but Firefox said it isn't signed. I'm using the latest versions of Firefox & Avast.

[REDACTED]

What avast version are you using ?
Avast 12.3.2280 is the latest and that may reflect if your Avast Browser Add-on is signed or not.

I see you didn't look at the screenshots.

So, lets go through it again.

Computer Formatted.
Brand new install of Windows 7.
Firefox 50 installed from the latest installer from Firefox.com
Latest version of Avast downloaded from avast.com and installed.
Avast confirms it's up to date.
Firefox confirms that there's no addon updates available, and that they are all running the latest version.
Firefox also confirms that the addon was last updated Today, 25th, November, 2016.

Addon does not work. says it's not verified and has been disabled.

All programs are up to date.

Since that computer last night, i have checked all my other ones, including ones running Avast Business. ALL OF THEM SHOW THE ADDON IS DISABLED. and all show many different versions of the update, from 10.* through to 12.3.*
If there is an update to the addon that is signed, then Avast update itself is Not Installing it, nor is it updating it.

[Eddy]

As it is a new version of AOS, it can be Mozilla hasn't verified it yet.

[Asyn]

...since Firefox 48, the xpinstall.signatures.required "False" flag has been disabled and no longer works.

Side note, the workaround still works with Firefox ESR.

[DavidR]

...since Firefox 48, the xpinstall.signatures.required "False" flag has been disabled and no longer works.

Side note, the workaround still works with Firefox ESR.

Whilst I used that xpinstall.signatures.required "False" flag, in the past (see attached image) - even though Mozilla disabled this - and it still appears to work, as AOS is still functioning for me.

@ DazzaJay
I do look at images that are attached to the post/topic. On occasion I also look at off site images, less so when they are on shortened url links when I have no idea where they will be taken.

I don't know why mine still works as the xpinstall.signatures.required "False" flag is still in about:config.

[bob3160]

I like David have no problems with FF 50. and AOS

[MrMaxaMan]

I just tried to install it again, Firefox still disables it.

[DavidR]

I just tried to install it again, Firefox still disables it.

What happens if you close firefox, uninstall the Security Browser Extension from the avastUI > Settings > Components. Restart your system, open firefox and check if the add-on was removed. If it has (close firefox again) try installing the Security Browser Extension again from the avastUI and restart.

Check it is now back on firefox and if it is enabled.

[MrMaxaMan]

What happens if you close firefox, uninstall the Security Browser Extension from the avastUI > Settings > Components. Restart your system, open firefox and check if the add-on was removed. If it has (close firefox again) try installing the Security Browser Extension again from the avastUI and restart.

Check it is now back on firefox and if it is enabled.

I gave that a try, but it's still disabled.

[DavidR]

I'm at a loss on what else to suggest, I was hoping that any remnant of the old add-on would have been cleared.

I can't see why firefox is disabling it, given that the AOS add-on is (or should be) signed.

[Eddy]

As it seems a new version of AOS was released yesterday (25 november), that could have something to do with it.

[MrMaxaMan]

As it seems a new version of AOS was released yesterday (25 november), that could have something to do with it.

Maybe, but I tried to install the addon about a week ago so there was still a problem then.