Hiya,
My searches didn’t yield a post on this so forgive me if it already exists and I missed it.
I recently updated my Avast Premier to version 11.1.2241 and noticed that since then my Firefox (version 42.0) no longer seems to be working with Avast Online Security (version 10.3.3.13). I tried disabling it, restarting Firefox, then re-enabling it / restarting Firefox to no avail. Afterwards I tried to remove it and re-acquire it by logging in (you know…the message that appears on the bottom when showing your account that lets you download / install it) and all to no avail.
Is there any known work-around or fix in the works for this? Would it be better to revert to an older version of avast (I still have an old installer executable) since it did seem to actually work with Firefox 42.0 before the update? Thanks to all that respond / in advance for all help offered!
(BTW: I tried it on Windows 7 x64 & 8.1 x64 with same versions…oddly enough it does still work with Internet Explorer 11.0.9600.18097 but I don’t regularly use IE to be honest.)
P.S. - I wanted to add that I tried installing the plugin via by going to (my.avast.com) and logging in that way and downloading the plugin and so still nothing, It does show up under my Add-ons>Extensions but nothing works!
I went ahead and followed your instructions to the T and it reinstalled the firefox extension but so far I’m not seeing the little avast icon pop up or anything. I’m using the 64-bit version of firefox I can go ahead and try installing the 32-bit and see if makes any difference or not and let you know on that.
I don’t believe it works with the 64bit version of Firefox 42 as it is still a relatively new release, though I could be wrong. I don’t know if avast have a 64bit version of the avast online security (AOS) add-on, which I believe is a requirement for 64bit browsers.
I’m sure there has been something related to this in the forums, though it may a bit hard getting the right search string to turn it up.
Thanks for your replies (Rednose & DavidR), your help is much appreciated!
On Windows 8.1 I tried it on both 64bit and 32bit versions of Firefox to no avail.
On Windows 7 the browser was strictly 32bit however I did attempt the steps previously mentioned with no luck either.
-Surfblue714
(Edit: Modified the first message adding that I tried going to my.avast.com the first time as well as tried going to add/re-add it via control panel…just in case since I realized I was a bit unintentionally vague.)
Ah I see, thanks again!
Any word on just the 32bit version since Windows 7 was always running 32bit Firefox and I uninstalled 64bit Firefox on Windows 8.1 to replace it with 32bit… all to no avail. I kinda miss those little green check marks next to my google search results.
It should be fine, my win7 32bit starter edition netbook I had it installed (for testing) with firefox. The issue as far as I recall was previously it wasn’t signed (but now it is by all accounts), so it should work with firefox 42.0.
That said I had previously made some changed to the firefox about:config (see image) to get round the requirement.
Here’s what I’ve got (see attached). My searches did yield that it was a potential issue but not immediately one, especially since my xpinstall.signatures.required is set to false by default. Is it an issue with Windows 64 bit or something since my Windows 7 x64 Ultimate with SP1 seems not to run it on 32bit Firefox 42.0? Anyways thanks again for all your help and any future help as well. It is really appreciated!
When firefox finally moves to signed add-ons only I believe it is this area where changes are likely to be made. Firefox had originally intended to have signing committed by a certain version originally that was I believe 42.0, but it looks like that has been pushed back. It is still just warning about unsigned ones - soon it won’t allow unsigned ones.
That is why I have done the image of my existing settings so I can watch out for them as I have some old (unsupported/no longer developed) add-ons that I find invaluable.
This isn’t something that I’m totally sure on as my win7 system is 32bit. A 64bit OS can run 32bit apps and that should be no different for the 32bit firefox/chrome/opera/IE browsers, etc. However, add-ons for the 64bit version of firefox need to be 64bit signed add-ons, but I don’t see how this would impact 32bit browser add-ons.
Quite true that it was originally planned for 42.0 but delayed. I searched high and low without a reasonable explanation for what could be causing my AOS Add-On to not be working properly. I am running 32bit Firefox on both Windows 8.1 & 7, it shouldn’t make a difference that the operating system is 64bit since it was all working perfectly fine before I updated to the newest version of Avast.
I suppose if anyone has any other suggestions then I would be immensely grateful to even be able to try them but otherwise I hope that this is something the Avast team is aware of and working on since right now the only thing that I can get to resolve it is to downgrade software (Firefox and/or Avast) which is not something I would particularly prefer.
So does anyone else have any other methods worth trying? Only option I thought of was downloading a really old version of Mozilla Breadsticks 26.0 and trying to install AOS to that version then doing a straight upgrade!
Those that want the AOS alerts in firefox before waiting that AOS is meeting firefox development signing demands can use Safe Preview 1.1.2.1-signed which has Google Advisory, McAfee, NortonSafe Web, WOT, Avast!, TrustWave an DrWeb online check aboard.
Are we talking about the Avast program or the new add-on. I have Avast Premier and it seems to work fine, but I can't get Firefox
to accept the add-on. If they don't want to accept it for security reasons I don't want to force it. I'm quite happy with Firefox's
browser. It seems like all the companies involved with browsers want to take control of the search engines and other browser functions.
Is it the Avast program we're talking about or the add-on?
Btw, it’s interesting that the OP states that IE is the only browser where the Avast add-on works for him because in my case it will invariable crash my IE11 if I enable the add-on. I still have the AOS add-on installed in my FF browser, but then I’ve stopped version updates for FF as of version 40.0.3 because of post changes and don’t really use FF anymore and instead have as of October switched to Pale Moon as my default browser and have never been happier as a result. I really appreciate the greater flexibility in as much as I prefer a more configurable browser which I’ve found the stability to be very robust and with far better support than I could ever get with the FF browser.
