Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Ahmmad Hegazy on February 19, 2017, 01:43:34 PM
-
please I'm asking about avast free 2017 , when I installed it , it doesn't install the security browser extension in mozilla firefox ?
anyone please help me
-
Which version of FF..?
32 or 64 Bit..?
-
64 bit
-
FF64 bit is not supported in the latest stable build.
It is in the latest Beta > https://forum.avast.com/index.php?topic=197296.0
-
Avast 17.1.2286 couldn't install AOS on 64bit versions of firefox.
This was meant to change in the latest avast beta 2287, but I found I couldn't even install it on 32bit versions of firefox.
-
Avast 17.1.2286 couldn't install AOS on 64bit versions of firefox.
This was meant to change in the latest avast beta 2287, but I found I couldn't even install it on 32bit versions of firefox.
(http://screencast-o-matic.com/screenshots/u/Lh/1487511462928-43359.png)
This is what I got after I allowed it:
(http://screencast-o-matic.com/screenshots/u/Lh/1487511703611-6663.png)
-
Yep, it should work with the latest beta.
-
Yep, it should work with the latest beta.
Still the same bloody state, avast says its installed, firefox has no entry for it.
Several restarts, uninstalls and reinstalls AOS isn't there. I give up, life's to short for this nonsense.
-
Yep, it should work with the latest beta.
Still the same bloody state, avast says its installed, firefox has no entry for it.
Several restarts, uninstalls and reinstalls AOS isn't there. I give up, life's to short for this nonsense.
Maybe one of your many extensions is blocking it ???
-
Extensions don't block the installation of other extensions (they are generally blocking web content), plus none of my extensions have ever done this and none of those have changed and they haven't stopped it before.
Not to mention you should still get the firefox intervention about installing a 3rd party extension as in your image 1 in Reply #5, nada, nothing, zero.
-
Not to mention you should still get the firefox intervention about installing a 3rd party extension as in your image 1 in Reply #5, nada, nothing, zero.
As mentioned in the main beta thread, you need to wait for 12 hours according to the devs.
-
Not to mention you should still get the firefox intervention about installing a 3rd party extension as in your image 1 in Reply #5, nada, nothing, zero.
As mentioned in the main beta thread, you need to wait for 12 hours according to the devs.
I hadn't opened FF since early yesterday and didn't have the extension there yesterday.
-
Not to mention you should still get the firefox intervention about installing a 3rd party extension as in your image 1 in Reply #5, nada, nothing, zero.
As mentioned in the main beta thread, you need to wait for 12 hours according to the devs.
It has been days not hours and it still doesn't bloody work. The main topic introducing the 17.2.2287 beta was posted on 17 February 2017, (17:28:14 UK local time).
I have seen nothing from the developers, only your posts stating that they have said something about 12 hours and it has been close to 1 day and 22 hours since then.
If the devs are going to introduce delays/invites or whatever, then it should be in the MAIN post of the introductory topic, so users aren't wasting their time.
I'm done wasting any more time on this after having uninstalled it from the avastUI.
-
I have seen nothing from the developers, only your posts stating that they have said something about 12 hours and it has been close to 1 day and 22 hours since then.
It was posted on Slack, if you join us there, I'll gladly provide the link. :)
-
I have seen nothing from the developers, only your posts stating that they have said something about 12 hours and it has been close to 1 day and 22 hours since then.
It was posted on Slack, if you join us there, I'll gladly provide the link. :)
I don't really care where it was posted, if it isn't in the avast forums and there are restrictions to a beta or regular release, then users/beta testers should be made aware of it.
I don't feel I should have to join slack or any other medium to find out information that should be released to avast users/beta testers in the forums.
-
Since this effects all beta testers even those that don't have access to slacker,
this definitely needs to be listed in the beta notice. It's OK to discuss the problem and find a solution on slacker or any place else but,
it needs to be disclosed in the Beta section.
-
1. I don't really care where it was posted, if it isn't in the avast forums and there are restrictions to a beta or regular release, then users/beta testers should be made aware of it.
2. I don't feel I should have to join slack or any other medium to find out information that should be released to avast users/beta testers in the forums.
1. Well, I told you (and all others) in the beta thread.
2. No problem Dave, that's up to you. :)
-
Well as I said it has been way longer than 12 hours and it still doesn't work, not that this matters any longer as it is history, enough time wasted on it.
-
Well as I said it has been way longer than 12 hours and it still doesn't work, not that this matters any longer as it is history, enough time wasted on it.
As it doesn't work on FF ESR yet, I also dropped it.
-
You should also get the notification on Google Chrome/Firefox (12 hours after installtion) to install AOS however you will not if you've ever removed the extension or declined to install in past.
If in the past on Chrome or any devices which are synced to Google Chrome account had removed AOS or declined to install... Chrome would change the AOS state to removed thus leading to all devices on the Google account to not get any notifications of the plugin in the future. It's a feature of Google..., I'm pretty sure the same applies to Mozilla but can be customized.
One more thing to note here is plugin notifications are delayed for 12 hours after installing Avast. I'm not impressed by this and it actually makes users think it's not working. I've asked on Slack if there's any chance of changing that in the past.
Alternatively, you can get AOS for Chrome from here if you don't get the notification: https://chrome.google.com/webstore/detail/avast-online-security/gomekmidlodglbbmalcneegieacbdmki?hl=en
-
You should also get the notification on Google Chrome/Firefox (12 hours after installtion) to install AOS however you will not if you've ever removed the extension or declined to install in past.
<snip>
This (if completely correct) further compounds the (unknown) delay issue as those who try to get it installed and working are going to be removing/uninstalling it from avast, restarting avast/firefox and rebooting ,etc.
Which will further frustrate users, who no fault of their own in trying to get it to work, if it subsequently stops them ever installing it.
Totally bloody crazy.
-
You should also get the notification on Google Chrome/Firefox (12 hours after installtion) to install AOS however you will not if you've ever removed the extension or declined to install in past.
<snip>
This (if completely correct) further compounds the (unknown) delay issue as those who try to get it installed and working are going to be removing/uninstalling it from avast, restarting avast/firefox and rebooting ,etc.
Which will further frustrate users, who no fault of their own in trying to get it to work, if it subsequently stops them ever installing it.
Totally bloody crazy.
I completely agree with you. What I've stated is correct and confirmed for Chrome, I'll need to ask about Firefox to be 100% sure on that.
Well, the 12 hours delay is the decision of Avast.
Regarding AOS not installing on Chrome/Firefox after a user has removed/declined in past - we can't really blame Avast. That's a setting of the web browsers and that's not under Avast control.
-
<snip quotes>
Regarding AOS not installing on Chrome/Firefox after a user has removed/declined in past - we can't really blame Avast. That's a setting of the web browsers and that's not under Avast control.
Well I really can't say avast are blameless, if it is known to avast about uninstalling/rejecting the AOS extension. This would really impact beta testers who are frequently going to be running tests and may well uninstall many components.
This is the first time I have ever heard of this potential blockage if having declined or removed AOS and I have never experienced this issue. So why now is my question, what has changed.
-
I've had the AOS extension on Firefox since I installed the latest stable version of Avast on Feb. 7