Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: MartinZ on April 07, 2020, 04:22:50 PM
-
Hi all,
we would like to announce that Avast versions 8.x and lower aren't supported anymore and we do not update virus definitions on them. We highly recommend to update to newer version as soon as possible.
Here is a guide how to update: https://support.avast.com/en-us/article/Update-Antivirus
Or you can simply download and install the latest version here: https://bits.avcdn.net/productfamily_ANTIVIRUS/insttype_FREE/platform_WIN/installertype_ONLINE/build_RELEASE/
Thank you!
-
And you thought the best time to announce this was now? One week after you stopped providing updates. In the midst of a public health crisis.
And you though this the best way to announce it? You could not be bothered to send email notifications to the affected subscribers, but instead chose to bury it in a forum post.
Please post directions on refunding the unused portion of our subscriptions.
-
Most pitiful !!!
That’s Avast !!!
Bye Bye on all my devices!!!
-
and here's the response from Avast regarding refunding the unusable portion of the subscription:
We are not able to submit refund requests if it is outside 30 days of purchase due to the Avast refund policy. Let me know if you need anything else.
That's the whole response.
Avast has behaved disgracefully. Martin, are you there? Anything you want to add?
-
I don't understand the logic of people. They wan to rely on something for protection, but for some reason run some years old version. It just makes absolutely no sense. And then they are outraged because the vendor phases it out. Sure, communication whatever it was, but YOU'RE RUNNING AN ANCIENT VERSION OF ANTIVIRUS for god sake. It's not like they charge you more for using newer version. The price is the same. And while I understand how people like interface of some version but no the other, but I don't understand that logic with antiviruses whose primary job is protection. And you're not getting the best protection with a version that's several years old now.
If you ask me, phasing out of consumer products should be much faster and strictly defined. Every version should get 3 years of support and then you'll have to upgrade to latest one. It's how you can evolve a product that needs constant evolving. Enterprise versions excluded because things move slower there as whole.
-
And that folks is a perfect example of the blinkered consumerist throw away attitude and why the world is filled with deliberately made redundant electronic waste, polluting every continent on the Earth.
New is not always better, particularly not for the consumer and the environment.
-
Highly questionable timing at this time of global crisis, and without warning...
People have other problems to deal with right now.
But some Avast decision-makers decided it was the right move at the right moment.
-
I can't understand the problem either, what is to stop an upgrade to a later version that 'is still' supported and would presumably be covered by existing licenses ?
-
I would like to emphasize a few words you used in your post, RejZoR, if you don't mind.
... the vendor phases it out.
I am wondering if this is a case of something being phased out, because I had the impression that when something is "phased out" there are steps to the whatever disappearing.
I'm just sort of wondering what steps we can identify in this particular case.
And there are some folks here that feel the timing is rotten, but this is very likely a management decision that was made some time back and now the company is probably having a hard time conducting meetings to review past decisions that are to be implemented during some difficult times. Somebody just made a recent decision that on this one they would just stick to the original plan, even though there are unusual events taking place present-day.
But there is one thing that I sense in your analyzation, RejZoR, that I hope you don't mind my addressing. You seem to be viewing this from a prospective of a true understanding of what a version is and what the purpose is of a program that uses that system of upgrades and all that is connected with such a program. That is kind of like somebody who knows what exactly is making a car run. Knows the engine and the transmission and all that.
The problem is that a whole lot of perfectly normal humans drive a car and don't have a clue why it is running. Something breaks and they take the car to a professional.
Same thing with digital programs, such as a software program that does the job of protecting their system.
That customer hasn't a clue why and how that program works and just does the most basic of stuff and, in this case, maybe it is set to an auto mode of some sort and maybe those people have even forgotten that program was installed on their computer by the daughter or son, or somebody.
Sure they are relying on it, but they may have even forgotten they are. And they sure don't know that there are versions or even any age thing. It's just there. A lot like the computer hardware itself that they just turn on and away they go doing whatever they want to do.
I think what I am trying to point out, RejZoR, is that you have the tech eye sort of thinking, but millions of customers do not. And the key word there is "customers" and it used to be that business folks were very nice to customers. There is a lot of that niceness missing in this computer world at the tech side because the tech folks think like tech folks and not like somebody who has other matters that they view as a whole bunch more important than some program that starts with an "A" and does some weird job of protecting from something they don't even know anything about.
And I also would bet that those same folks don't even know this forum exists and so is the announcement here is going to be of much help to alert a whole bunch of customers to this change that was decided upon a bit back?
I mean, how many customers does this company have? Is it in the millions? If so, then I would bet I can find at least a hundred thousand that haven't a clue what's going on with this product or even why it was installed by somebody on their computer.
I really think it might not be such a bad idea to give some of those folks some consideration. And I wonder if any of those same folks might own some significant stock in this company. That could make for some very uncomfortable talking at some stockholder's meeting if suddenly a big change was made and they were taken by surprise. I sure hope the message of this thread has been placed before some customers that are more interested in making money, and are good at that job, than being interested in why their computer works so well. And computer hardware has gotten mighty reliable and some computers can go for years and years before there is trouble, especially if everything is set at automatic.
Sometimes thinking like a tech pro isn't such a good idea. Be nice to that customer, especially if it might be a sort of not too bright customer, but one that has money.
My goodness, sorry this post got so long.
-
I am puzzled. By 'Windows 8' do you mean also Windows 8.1 which is in extended support from MS until 2023. Windows 7 of course is now out of support but there are still loads of computers in use with it, it is surely too early to end Avast support on that, you kept supporting XP for a very long time.
-
I am puzzled. By 'Windows 8' do you mean also Windows 8.1 which is in extended support from MS until 2023. Windows 7 of course is now out of support but there are still loads of computers in use with it, it is surely too early to end Avast support on that, you kept supporting XP for a very long time.
The subject of this topic is phasing out of support for Avast version 8, as in the first post of this topic, nothing to do with Windows 8.
Hi all,
we would like to announce that Avast versions 8.x and lower aren't supported anymore and we do not update virus definitions on them. We highly recommend to update to newer version as soon as possible.
<snip>
Thank you!
-
And that folks is a perfect example of the blinkered consumerist throw away attitude and why the world is filled with deliberately made redundant electronic waste, polluting every continent on the Earth.
New is not always better, particularly not for the consumer and the environment.
What "consumerism" and "throw away" attitude?! This is software, not piles of old computer hardware. Also, in case of antivirus/antimalware software, yes, NEW is by definition better. Antivirus software is not updated constantly because they are so bored, it's because it has to keep up with malware trends. And you can't be on top of latest malware threats with what, 5 years old antivirus even if it's getting the latest signatures. It just doesn't have half of the technology used in new versions. Like CyberCapture as well as other heuristics and I know there was a huge JS engine upgrade with merger of avast! and AVG. Not to mention Behavior Shield which is a behavior analyzer and blocker. Behavior Shield before AVG merger was in all honesty useless and did nothing at all. This new one actually detects a lot of stuff.
-
New is not better when it comes bundled with junk, unwanted features and removes previously useful options etc
I do not want AV or any other similar software running on my PCs continuously to do anything but what it is supposed to do: protect the system.
You want to know it is working and the presence of the tray icon confirms that. I do not need a pop up telling me about updates and all the things real and imagined it has detected. You want it to keep itself to itself and stay entirely in the background not interfering, at all, with your use of the PC. Not much to ask you would have thought.
Why are users still using older AVAST versions, which incidentally AVAST should actually be pleased about and proud of? It is because they still work more than adequately to protect users PCs yet are closer to that ideal than more recent versions.
It is bizarre when users, clearly loyal, are treated as annoying dinosaurs when they are actually the brand's best advocates.
-
I agree with Cluster-Lizard2014. I accept the offer of elective features with reasonable (if grumpy >:() grace because I use a free version.
Software maintenance of version 8 and earlier has already ceased a few years ago but the virus definition updates for old Avast versions are presumably unlikely to become functionally obsolete unless much more recent old versions are to be also designated as obsolete. Won't it be the case that virus definition updates for old Avast versions are distributed using automation and so there are only modest overheads entailed in their distribution?
I have a vested interest in Avast version 10(2015). It is my misfortune that my Windows XP SP3 system uses a non-SSE2 processor and so cannot use Avast 18.8.
Continued supply of virus definition updates for older versions offers peace of mind to users of older systems and to those who have found that more recent versions are troublesome.
-
Cluster-Lizard2014: I get the user interface part (and other "visible" features); for me personally, the best UI was the Enhanced UI of Avast 4.8 ;)
However, you're saying that it's supposed to "protect the system". And to do that job well, you do need the latest version. You're saying that the old versions work "more than adequately"... and I can't agree there. Yes, the changes in the user interface may be unnecessary or even unwanted for some users, but I'm afraid other changes/updates in the program (that you don't see) are very relevant, protection-wise.
Plus of course there are security vulnerabilities fixed in Avast every now and then - and you do need those as well.
-
I have a vested interest in Avast version 10(2015). It is my misfortune that my Windows XP SP3 system uses a non-SSE2 processor and so cannot use Avast 18.8.
Hi versions 9+ are still supported.
-
Won't it be the case that virus definition updates for old Avast versions are distributed using automation and so there are only modest overheads entailed in their distribution?
It's not about the distribution, it's about their actual creation or implementation. A big part of virus definitions are simply code - just like the program itself, only loaded from a newly created/updated folder every day.
That code has to be compiled with an old compiler (to work in those old programs), so it cannot use any new(er) features (that may have a performance or security impact). Some 3rd party libraries may have to stay on old (possibly buggy or insecure) versions because the new/fixed ones cannot even be compiled with that old compiler anymore.
The program provides a lot of functionality for the virus definitions (you could imagine the program being an array of sensors feeding information into the virus definition code where it gets evaluated, plus also providing "executive functions" that can be called when a decision was made. Those old program versions have less sensors, and they use different formats, so the code in the virus definitions gets complicated - and subsequently buggy (and of course takes longer time to write, and longer time to test). So as I wrote elsewhere, it slows down the development and release of updated protection for the new program versions.
-
Thanks Igor. That is interesting. I learned a lot from your insights of the production of virus definitions.
Inside the void within my skull which is my brain, I had naively assumed that virus definitions were at the level of templates. Now I learn that they possess the dynamic complexity of software so it is no wonder that old versions must eventually be discontinued. I should actually be saying "thanks" to Avast for so considerably prolonging the lives of older versions.
-
I agree with Cluster-Lizard2014. I accept the offer of elective features with reasonable (if grumpy >:() grace because I use a free version.
Software maintenance of version 8 and earlier has already ceased a few years ago but the virus definition updates for old Avast versions are presumably unlikely to become functionally obsolete unless much more recent old versions are to be also designated as obsolete. Won't it be the case that virus definition updates for old Avast versions are distributed using automation and so there are only modest overheads entailed in their distribution?
I have a vested interest in Avast version 10(2015). It is my misfortune that my Windows XP SP3 system uses a non-SSE2 processor and so cannot use Avast 18.8.
Continued supply of virus definition updates for older versions offers peace of mind to users of older systems and to those who have found that more recent versions are troublesome.
True, I totally agree ... Avast should respect its older customers and stop wanting to impose versions ... After all, they manufacture antivirus, not operating systems. Microsoft's shit is enough for us to download problem patches to make its slow, resource-consuming system worse.
-
I agree with Cluster-Lizard2014. I accept the offer of elective features with reasonable (if grumpy >:( ) grace because I use a free version.
Software maintenance of version 8 and earlier has already ceased a few years ago but the virus definition updates for old Avast versions are presumably unlikely to become functionally obsolete unless much more recent old versions are to be also designated as obsolete. Won't it be the case that virus definition updates for old Avast versions are distributed using automation and so there are only modest overheads entailed in their distribution?
I have a vested interest in Avast version 10(2015). It is my misfortune that my Windows XP SP3 system uses a non-SSE2 processor and so cannot use Avast 18.8.
Continued supply of virus definition updates for older versions offers peace of mind to users of older systems and to those who have found that more recent versions are troublesome.
True, I totally agree ... Avast should respect its older customers and stop wanting to impose versions ... After all, they manufacture antivirus, not operating systems. Microsoft's shit is enough for us to download problem patches to make its slow, resource-consuming system worse.
You still don't seem to understand that your old operating system can not run a version of Avast that can protect you.
It's time to upgrade your operating system in order to be protected against current vulnerabilities.
-
I agree Bob. Lack of ASLR is the bummer with XP and I am using it less and less. I definitely no longer use XP for anything which is even remotely connected with privacy. I am still waiting for a security event though. I feel quite left out. All the Windows 8.1 and 10 systems I have built and now support for friends and relatives have yet to suffer security events. I emphasise the use of the word 'yet'.
I have found that using the strictest degree of mandatory ASLR causes no operational problems yet (that word again) apart from preventing Malwarebytes AdwCleaner 8 from executing. Version 7 is unaffected.
You might have noticed that I no longer mention my XP system in my forum profile. This is because I am using another AV with XP, apparently the only AV product still to run with XP in its latest version form.
Keep safe Bob and Mrs Bob (I mean safe from COVID-19 :()
-
"Keep safe Bob and Mrs Bob (I mean safe from COVID-19 ) "
Thank you we are both fine. Hope you and your family are also doing well.
My youngest daughter is currently awaiting test results. We have our fingers crossed an
have many prayers being said.
-
In the case of the management console for Avast Business Pro vs. the SOA for Endpoint Protection Plus, new is definitely not better. The console is missing several features that were available in the SOA and this has made the system more time consuming for me to use. This is a primary reason why I have only been using Avast Business Pro with Windows 10 devices, because Endpoint Protection Plus won't work with that operating system. If people want to encourage rapid uptake of new versions, they need to make sure the new versions don't remove features that people rely on.
COVID may be affecting the efficiency of Avast's operations, and I am sympathetic because it is affecting my operation in a very serious way. But I doubt that is what stopped them from directly notifying its business customers of the date when they would stop supporting the older product. I should not have to monitor events on a website manned largely by volunteers on a daily basis to find out this kind of thing.
Given recent public disclosures regarding Avast's abuse of the personal information it has collected about users (at least those using the free version), I would suggest that the company be very careful and diligent about only taking such steps as will improve its standing among its customer base. Many people in the industry who had previously promoted Avast as one of the better anti-malware products have changed their positions as a result of this scandal. The company is probably very close to a tipping point in terms of loss or business as a result of this. The company cannot afford any further missteps. It should come completely clean about what it does with information collected from paying customers. And it should rapidly restore all features that were in the SOA to the Avast Business Pro console.
-
You might have noticed that I no longer mention my XP system in my forum profile. This is because I am using another AV with XP, apparently the only AV product still to run with XP in its latest version form.
Hi!
Just read your post here and I thought, I'll try to tell you, that there are a lot of members here, still using XP with Avast AV without any probs (see my sig).
But I invested a lot of time getting there and my experience is, that it depends on the hardware structure of the machines to find out the latest usable version of Avast.
Keep safe.
=Snake=
-
You might have noticed that I no longer mention my XP system in my forum profile. This is because I am using another AV with XP, apparently the only AV product still to run with XP in its latest version form.
Hi!
Just read your post here and I thought, I'll try to tell you, that there are a lot of members here, still using XP with Avast AV without any probs (see my sig).
But I invested a lot of time getting there and my experience is, that it depends on the hardware structure of the machines to find out the latest usable version of Avast.
Keep safe.
=Snake=
Well XP/Vista is supported up to Avast version 18.8, so there really shouldn't be any reason to stop with a very old Avast 8 version.
-
You might have noticed that I no longer mention my XP system in my forum profile. This is because I am using another AV with XP, apparently the only AV product still to run with XP in its latest version form.
Hi!
Just read your post here and I thought, I'll try to tell you, that there are a lot of members here, still using XP with Avast AV without any probs (see my sig).
But I invested a lot of time getting there and my experience is, that it depends on the hardware structure of the machines to find out the latest usable version of Avast.
Keep safe.
=Snake=
Well XP/Vista is supported up to Avast version 18.8, so there really shouldn't be any reason to stop with a very old Avast 8 version.
But version 18.8. didn't fit on those machines with XP or W7 caused by the implemented hardware. So the latest one was Avast free 10.4.2233!
-
You might have noticed that I no longer mention my XP system in my forum profile. This is because I am using another AV with XP, apparently the only AV product still to run with XP in its latest version form.
Hi!
Just read your post here and I thought, I'll try to tell you, that there are a lot of members here, still using XP with Avast AV without any probs (see my sig).
But I invested a lot of time getting there and my experience is, that it depends on the hardware structure of the machines to find out the latest usable version of Avast.
Keep safe.
=Snake=
Well XP/Vista is supported up to Avast version 18.8, so there really shouldn't be any reason to stop with a very old Avast 8 version.
But version 18.8. didn't fit on those machines with XP or W7 caused by the implemented hardware. So the latest one was Avast free 10.4.2233!
Fitted on mine, so it isn't all XP/Vista systems, which I was saying (not Win7).
Users should at least try to get the latest version that they can install, be that Avast 10 or 18 as support for Avast 8 will or has ended.
-
I am using v18.8 perfectly well on a old XP SP3 (now XP/Linux dual boot) machine. That is the version you should try first for XP/Vista then go backwards from that if it doesn't work on your particular machine. Later versions will provide better protection if not better UI. Protection not apperance is King here.
-
Hello there,
I noticed that after version 8 and below support was cut, mozilla firefox HTTPS traffic is not working properly.
For example, clicking on test viruses is no problem in HTTP
http://2016.eicar.org/download/eicar.com
But HTTPS does not detect traffic.
https://secure.eicar.org/eicar.com
I discussed this issue with firefox officers. The problem is a bilateral problem, but it seems to be avast.
That is, if I install with the latest 2020 setup file of avast, HTTPS detection works fine.
However, in avast version 9 and above, HTTPS traffic does not work properly.
I am satisfied with the avast 11 version, I use it.
It is noteworthy that it removes HTTPS when it uninstalls and reinstalls it, but it does not detect HTTPS scanning again when it receives VPS updates.
Apparently not only for avast 8 and below, support for 18 and below versions has been cut off, the VPS packages you provided are causing problems. This problem does not exist in versions 19 and 20. All the other sub-versions have the same problem.
HTTPS traffic runs smoothly in opera, but there is a problem in firefox. I should point out that this issue is not a simple certificate issue, but all certificates are complete.
The current 2020 version of avast with Firefox works flawlessly, but why does it not detect HTTPS traffic when the VPS update comes to other older versions?
Sorry my foreign language is not good, thank you for your understanding ...
-
I have a vested interest in Avast version 10(2015). It is my misfortune that my Windows XP SP3 system uses a non-SSE2 processor and so cannot use Avast 18.8.
Continued supply of virus definition updates for older versions offers peace of mind to users of older systems and to those who have found that more recent versions are troublesome.
Hi!
I agree with loungehake for I'm still using very old machines with non-SSE2 like him (see my sig). So there's nothing to write more.
=Snake=
-
Hello there,
I noticed that after version 8 and below support was cut, mozilla firefox HTTPS traffic is not working properly.
For example, clicking on test viruses is no problem in HTTP
http://2016.eicar.org/download/eicar.com
But HTTPS does not detect traffic.
https://secure.eicar.org/eicar.com
I discussed this issue with firefox officers. The problem is a bilateral problem, but it seems to be avast.
That is, if I install with the latest 2020 setup file of avast, HTTPS detection works fine.
However, in avast version 9 and above, HTTPS traffic does not work properly.
I am satisfied with the avast 11 version, I use it.
It is noteworthy that it removes HTTPS when it uninstalls and reinstalls it, but it does not detect HTTPS scanning again when it receives VPS updates.
Apparently not only for avast 8 and below, support for 18 and below versions has been cut off, the VPS packages you provided are causing problems. This problem does not exist in versions 19 and 20. All the other sub-versions have the same problem.
HTTPS traffic runs smoothly in opera, but there is a problem in firefox. I should point out that this issue is not a simple certificate issue, but all certificates are complete.
The current 2020 version of avast with Firefox works flawlessly, but why does it not detect HTTPS traffic when the VPS update comes to other older versions?
This has nothing to do with the end of v8 support (what you noticed has actually happened much sooner) - but otherwise it's a great example of why it's necessary to use the latest versions of your antivirus.
Browsers change continuously - and sometimes they change in a way that a particular Avast feature (such as https scanning) either stops working completely, or starts causing some problems (for example, it's not possible to open specific web pages). If that happens, we update the code to resolve that - and the fix is released in the next program update. However, we don't want to cause weird problems or conflicts for people that, for some reason, don't use the latest version of Avast - so we (if possible) restrict or disable the related Avast feature for those old program versions via virus definition updates.
-
Hello there,
I noticed that after version 8 and below support was cut, mozilla firefox HTTPS traffic is not working properly.
For example, clicking on test viruses is no problem in HTTP
http://2016.eicar.org/download/eicar.com
But HTTPS does not detect traffic.
https://secure.eicar.org/eicar.com
I discussed this issue with firefox officers. The problem is a bilateral problem, but it seems to be avast.
That is, if I install with the latest 2020 setup file of avast, HTTPS detection works fine.
However, in avast version 9 and above, HTTPS traffic does not work properly.
I am satisfied with the avast 11 version, I use it.
It is noteworthy that it removes HTTPS when it uninstalls and reinstalls it, but it does not detect HTTPS scanning again when it receives VPS updates.
Apparently not only for avast 8 and below, support for 18 and below versions has been cut off, the VPS packages you provided are causing problems. This problem does not exist in versions 19 and 20. All the other sub-versions have the same problem.
HTTPS traffic runs smoothly in opera, but there is a problem in firefox. I should point out that this issue is not a simple certificate issue, but all certificates are complete.
The current 2020 version of avast with Firefox works flawlessly, but why does it not detect HTTPS traffic when the VPS update comes to other older versions?
This has nothing to do with the end of v8 support (what you noticed has actually happened much sooner) - but otherwise it's a great example of why it's necessary to use the latest versions of your antivirus.
Browsers change continuously - and sometimes they change in a way that a particular Avast feature (such as https scanning) either stops working completely, or starts causing some problems (for example, it's not possible to open specific web pages). If that happens, we update the code to resolve that - and the fix is released in the next program update. However, we don't want to cause weird problems or conflicts for people that, for some reason, don't use the latest version of Avast - so we (if possible) restrict or disable the related Avast feature for those old program versions via virus definition updates.
Thanks for the answer.
Yes, using the latest version is of course the most correct.
But is it the problem of the user that one of the basic protection features such as HTTPS scanning is disabled?
We users trust this antivirus software and continue our lives.
Do you need to constantly monitor if the antivirus is working?
If Avast cannot perform its basic feature web protection properly, are we responsible for it?
If the important shields do not work properly, then formally state that you have completely discontinued support under the latest version.
I like avast version 11 as a user, it is plain and uses few resources.
I also know that HTTPS blocked websites as a result of hard work, users closed it ...
If you are providing support, give full support and we expect that HTTPS protection will be improved soon in avast version 9 and above.
Best regards...
-
"If Avast cannot perform its basic feature web protection properly, are we responsible for it?"
If your computer is so old that it's no longer able to run the current version of Avast, is that Avast's fault?
There comes a time when an antique (your old computer) needs to be used for show not for online exposure. IMHO
-
"If Avast cannot perform its basic feature web protection properly, are we responsible for it?"
If your computer is so old that it's no longer able to run the current version of Avast, is that Avast's fault?
There comes a time when an antique (your old computer) needs to be used for show not for online exposure. IMHO
Thanks for your ideas
My computer is not very old. This computer has been running avast free for about 10 years. I am satisfied with the old 11 versions of Avast.
What saddened me was that I had researched and learned this myself, I was safe in the old 11 version.
Unfortunately, I did not know, I am learning from the forum.
If the HTTPS traffic scan in the old version does not improve, I will have to upgrade to the 2020 version or another alternative software.
Thank you for your answer.
Best regards...
-
I was trying to describe the scenario that's happening.
1. Avast version X is released, https scanning works for the current version of the browser(s)
2. A new version of the browser is released - with internal changes that prevent Avast https scanning from working
3. Avast version X+1 is released, with updated code to make https scanning work again
There's no way to avoid that (it's happening because there's no "supported" way of scanning browser traffic, i.e. no API - so WebShield, and especially https scanning, has to rely on some internal stuff of the browsers).
So yes, Avast supports HTTPS scanning - by updating the code and releasing it as a new version.
In case you think that version 11 would somehow be updated... that's not possible, the versioning is linear. When version 11 was updated, after a few minor versions it became version 12. Then, after a few minor version, it became version 17... and now we're at version 20.3 We can't go back in time and release an update for version 11 - even if a specific problem was found affecting all versions 11 and later, the fix would be version 20.4 - with all the changes of the past few years.
In special cases it's possible to release emergency updates for a few versions back - but that is limited to small changes (which updating all the https support code for the latest browsers definitely would not be), and it certainly can't go back years old. I mean, we probably wouldn't be able to even compile those old versions, the tools have been updated many times since then. (I'm not even sure if version 11 had the emergency updater, for that matter.)
So I have to repeat again - the only way to stay as safe as possible is to use the latest versions of the program. If you stay on an older version, you are at risk that some features stop working (because of changes in 3rd party software, i.e. out of our control), the antivirus may not be effective against latest threats (of course the antivirus core responds to the latest development in the world of malware in each version - so older version may not be able to "see" some things), and you may be vulnerable to some security bugs in the antivirus itself (which again we fix once we learn them - and the fix is released as new versions).
-
I was trying to describe the scenario that's happening.
1. Avast version X is released, https scanning works for the current version of the browser(s)
2. A new version of the browser is released - with internal changes that prevent Avast https scanning from working
3. Avast version X+1 is released, with updated code to make https scanning work again
There's no way to avoid that (it's happening because there's no "supported" way of scanning browser traffic, i.e. no API - so WebShield, and especially https scanning, has to rely on some internal stuff of the browsers).
So yes, Avast supports HTTPS scanning - by updating the code and releasing it as a new version.
In case you think that version 11 would somehow be updated... that's not possible, the versioning is linear. When version 11 was updated, after a few minor versions it became version 12. Then, after a few minor version, it became version 17... and now we're at version 20.3 We can't go back in time and release an update for version 11 - even if a specific problem was found affecting all versions 11 and later, the fix would be version 20.4 - with all the changes of the past few years.
In special cases it's possible to release emergency updates for a few versions back - but that is limited to small changes (which updating all the https support code for the latest browsers definitely would not be), and it certainly can't go back years old. I mean, we probably wouldn't be able to even compile those old versions, the tools have been updated many times since then. (I'm not even sure if version 11 had the emergency updater, for that matter.)
So I have to repeat again - the only way to stay as safe as possible is to use the latest versions of the program. If you stay on an older version, you are at risk that some features stop working (because of changes in 3rd party software, i.e. out of our control), the antivirus may not be effective against latest threats (of course the antivirus core responds to the latest development in the world of malware in each version - so older version may not be able to "see" some things), and you may be vulnerable to some security bugs in the antivirus itself (which again we fix once we learn them - and the fix is released as new versions).
Thank you for your answer.
-
Because some people seem to not understand why developers push updates, it's not because they have nothing else to do, it's because old software:
- Opens you to security vulnerabilities
- Might be incompatible with future OS updates
- Might cause all sorts of system issues, including but not limited to Blue Screen of Death
- You can't expect ancient, 7-year-old software to do its job as effectively as current one
As soon as new version has been released, it's an absolute must that you update your software at your first convenience. Otherwise, there is no point of running security software at all, as it will only impact your performance, with near-zero improvement of your security posture.
The fuss being thrown here is absolutely unneeded to anyone, because:
-Avast already has a huge consumer base and whether or not 3-4 people will use it, doesn't concern them one bit. If you expect that they will refund you, or support the product specially for you, you are wrong.
-The version being phased-out is ancient, uses another engine and it's normal that the developer will end support, to relocate human resources towards current versions.
-
Because some people seem to not understand why developers push updates, it's not because they have nothing else to do, it's because old software:
- Opens you to security vulnerabilities
- Might be incompatible with future OS updates
- Might cause all sorts of system issues, including but not limited to Blue Screen of Death
- You can't expect ancient, 7-year-old software to do its job as effectively as current one
As soon as new version has been released, it's an absolute must that you update your software at your first convenience. Otherwise, there is no point of running security software at all, as it will only impact your performance, with near-zero improvement of your security posture.
The fuss being thrown here is absolutely unneeded to anyone, because:
-Avast already has a huge consumer base and whether or not 3-4 people will use it, doesn't concern them one bit. If you expect that they will refund you, or support the product specially for you, you are wrong.
-The version being phased-out is ancient, uses another engine and it's normal that the developer will end support, to relocate human resources towards current versions.
Posting in old topics that haven't had any activity makes no sense and serves no purpose other than activating an outdated topic.
-
Hi all,
we would like to announce that Avast versions 8.x and lower aren't supported anymore and we do not update virus definitions on them. We highly recommend to update to newer version as soon as possible.
Here is a guide how to update: https://support.avast.com/en-us/article/Update-Antivirus
Or you can simply download and install the latest version here: https://bits.avcdn.net/productfamily_ANTIVIRUS/insttype_FREE/platform_WIN/installertype_ONLINE/build_RELEASE/
Thank you!
Hello! I'm sorry to use this topic for other purpose, i'm new to forums and avast's support hasn't helped. I can't install Free Security for my mac 10.14.6, the installer only says "installation failed, contact software designer". The problem has repeated for over a year, and meanwhile i have no malware protection so i have to solve this fast. Anyone can give me a hand? Thank you for your time
-
Hi all,
we would like to announce that Avast versions 8.x and lower aren't supported anymore and we do not update virus definitions on them. We highly recommend to update to newer version as soon as possible.
Here is a guide how to update: https://support.avast.com/en-us/article/Update-Antivirus (https://support.avast.com/en-us/article/Update-Antivirus)
Or you can simply download and install the latest version here: https://bits.avcdn.net/productfamily_ANTIVIRUS/insttype_FREE/platform_WIN/installertype_ONLINE/build_RELEASE/ (https://bits.avcdn.net/productfamily_ANTIVIRUS/insttype_FREE/platform_WIN/installertype_ONLINE/build_RELEASE/)
Thank you!
Hello! I'm sorry to use this topic for other purpose, i'm new to forums and avast's support hasn't helped. I can't install Free Security for my mac 10.14.6, the installer only says "installation failed, contact software designer". The problem has repeated for over a year, and meanwhile i have no malware protection so i have to solve this fast. Anyone can give me a hand? Thank you for your time
Please post your question in the MAC section, https://forum.avast.com/index.php?board=5.0
-
Umm, correct me if wrong, but where is the 'proper' version number??
I am running version 21.2.2455 (build 21.2.6096.696) But it moans that it cannot update...
- I will NEVER update windows from V7, (only way up is Linux...) It runs very well, unlike the latest, where you get printer fails, sound fails, etc, etc!!!
https://www.avast.com/windows-7-antivirus says you are still supporting it, maybe i have the wrong version???
Please point me to the one that DOES NOT ask to 'upgrade the OS' ... :) :P
-
Umm, correct me if wrong, but where is the 'proper' version number??
I am running version 21.2.2455 (build 21.2.6096.696) But it moans that it cannot update...
Important notice for users of Windows 7
Due to an expiring Microsoft certificate for signing drivers, we had to block updates and installations from users with outdated/unpatched versions of Windows 7 (up to KB3033929). Unless they update their operating system, they will remain on version 21.2 of Avast and will not be able to perform future program updates.
-
I am using WINDOWS 7 SINCE 8 year+..
Now WIthout any latest update My pc running smoothly with Avast protetion,
Thanks Avast FOR SUpporting WIndows 7
Best Antivirus For windows 7 ever i see ;) ;) ;)
-
I am using WINDOWS 7 SINCE 8 year+..
Now WIthout any latest update My pc running smoothly with Avast protetion,
Thanks Avast FOR SUpporting WIndows 7
Best Antivirus For windows 7 ever i see ;) ;) ;)
There are limitations even for Avast when the OS is no longer supported and updated by MS.
-
Stopped updating antivirus signatures
Windows 8.1
Avast Free 23.3.6058
Belarus
What's happened? I've been using Avast since 2000 and it's such garbage
-
Stopped updating antivirus signatures
Windows 8.1
Avast Free 23.3.6058
Belarus
What's happened? I've been using Avast since 2000 and it's such garbage
Read the first post from 07 April 2020 again, it is talking about Avast 8 and NOT Windows 8. So your problem is something else an may well be your location.
So your problem is completely unrelated to this topic, which should be in its own new topic.
I can't understand your logic, if it is so garbage why would you be using it for 23 years !
-
I can't understand your logic, if it is so garbage why would you be using it for 23 years !
It's in the sense of "garbage happened." Never had a problem before and didn't think it was bad.
-
I can't understand your logic, if it is so garbage why would you be using it for 23 years !
It's in the sense of "garbage happened." Never had a problem before and didn't think it was bad.
I suggest that you start your own new topic and explain exactly what is happening and or warnings/errors that you are getting.
Given your location, I don't know (as an Avast user) if the issue might have to do with the ongoing situation in Ukraine and sanctions imposed (that too would be off-topic in this topic).
-
Want to share it here also:
https://www.techspot.com/downloads/2108-avast-virus-definitions-update.html
There is a new (vir-def list) update (for download) - December 26, 2023 - for Avast 5, 6, 7, 8. (And for all the versions up to 18+.)
Downloaded 1,964,997 times, until now.
-
Want to share it here also:
https://www.techspot.com/downloads/2108-avast-virus-definitions-update.html
There is a new (vir-def list) update (for download) - December 26, 2023 - for Avast 5, 6, 7, 8. (And for all the versions up to 18+.)
Downloaded 1,964,997 times, until now.
It's not updated, just providing old definitions. And the file is the same as my previous post on your topic.
Timestamp: 2020/04/01, same hash.
-
Oh. OK. Thank You this note.
So, this is staying confusing.
Because the last update in summer this year CAN only be newer as this update from 2020 ...
(This date I still did not realize. Thanks.)
So, with installing this 2020 version, the def-list is 3 years setted back. In my imagine.
And update - from looking from today - it may not be called anymore.
Wouh.
(And I remove the [Solved] note again, in my request post.)
-
Oh. OK. Thank You this note.
So, this is staying confusing.
Because the last update in summer this year CAN only be newer as this update from 2020 ...
(This date I still did not realize. Thanks.)
So, with installing this 2020 version, the def-list is 3 years setted back. In my imagine.
And update - from looking from today - it may not be called anymore.
Wouh.
(And I remove the [Solved] note again, in my request post.)
There is no solving what was't broke.
Support for this old version has ended. There are no more updates.
It also doesn't help to look for support based on a topic that goes back to 2020.
-
I am sorry.
I just did take that for serious:
"avast! Virus Definitions Update December 31, 2023" https://www.techspot.com/downloads/2108-avast-virus-definitions-update.html
-
I am sorry.
I just did take that for serious:
"avast! Virus Definitions Update December 31, 2023" https://www.techspot.com/downloads/2108-avast-virus-definitions-update.html
I think that relates to the latest version and or the last time the page was updated, any last versions for a particular version of Avast 'would have to be frozen' otherwise it could break an installation if the old program version didn't support the changes.
You are going to find problems going back so far even if a file repository (unrelated to Avast itself) said it was from a later date.
-
I think it is very reliable to subordinate, that a vir-def list with a date from December 31, 2023 which are presented ´does fit expressivly to the Avast versions 5 and 6 and 7 and 8´, they are the fitting versions and something as "otherwise it could break an installation if the old program version didn't support the changes." is really at all not to expact such.
-
I think it is very reliable to subordinate, that a vir-def list with a date from December 31, 2023 which are presented ´does fit expressivly to the Avast versions 5 and 6 and 7 and 8´, they are the fitting versions and something as "otherwise it could break an installation if the old program version didn't support the changes." is really at all not to expact such.
Sorry but trying to justify using outdated and unsupported AV protection makes no sense.
Outdated and unsupported = no actual reliable protection.
-
I think it is very reliable to subordinate, that a vir-def list with a date from December 31, 2023 which are presented ´does fit expressivly to the Avast versions 5 and 6 and 7 and 8´, they are the fitting versions and something as "otherwise it could break an installation if the old program version didn't support the changes." is really at all not to expact such.
You are fighting the help we are trying to give (to remain on an old unsupported version of Avast) and we have said finding old versions and or virus defs is going to be difficult.
The one thing you can't do is hold Avast accountable for what some other site prints. Avast has made it clear what versions are still supported (as has this topic), you either choose to go down that path or not.
-
"Outdated and unsupported = no actual reliable protection.":
That is the reason I do the effort I am doing here. To secure security.
I am not willing - after studying 2 Windows versions each about 5 years - to keep this effort going on.
XP is the last Windows version, where I did this effort.
I do not subdue this conditions of Microsoft, with every new version of Windows to have to face all the extreme changes from every new version again and again.
It is about 2 things, for me an OS is important, Browser and security, at most an anti-virus protection.
Browser for XP still is available.
Anti-virus now is Avast.
I currently am forced to try Avast 18.8. This is effort again.
And if too slow, and does not meet my expectation, this makes me further effort.
This is very forcing al in all.
And no fun at all.
"The one thing you can't do is hold Avast accountable for what some other site prints":
This I do not.
But I take Avast into the responsibility to not to support the vir-def list updates.
Or even to not update the Avast program with for XP.
This further is forcing to me to have to leave XP.
This I just cannot exept.
If it is OK this once saying here.
Thank You.
And thanks the labour trying to help.
-
"Outdated and unsupported = no actual reliable protection.":
That is the reason I do the effort I am doing here. To secure security.
Your effort would be better served in updating your outdated Operating System.
-
This is in progress, but with Linux, no more further with Win.
-
Virus definitions for Avast version 5-11 are indeed not created anymore (they are not compiled, not signed, not released - they simply do not exist).
The techspot.com page only makes it appear they are, most likely because they are showing the release date of the 18+ definitions (i.e. of a program version that is current and supported). But the definitions you actually download from there for Avast 5-11 are old, they won't update anything.