Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Charyb-0 on October 14, 2010, 04:08:57 PM
-
Would it be a good idea for Avast to include a pre-scan before installation proceeds?
Seems like many of Avasts problems occur because of remnants of old antivirus programs, failure to remove existing AV, running more than one antivirus, and/or malware already on computer before installation. Scanning for all of these issues would more than likely help to decrease the number of failed installs. This is not my idea and is already being used by other AV's to prevent such problems.
-
Great idea, but I think it's not easy to realize it... ;)
-
It's a good idea but virtually impossible to implement
A new AV would need detect every other AntiMalware + all variants
-
Then why are other AV developers scanning before installing? What areas are they scanning? Aren't they checking for existing AV programs, system files and checking for infected/corrupted files before they allow the install to proceed? It doesn't seem to be a full scan because it only takes a minute or two. They wouldn't do this for no reason. And if others can achieve this why would it be difficult for Avast to do the same thing?
-
Some verifications are already done.
I know that Comodo prescans in order to assure that the machine is clean and refund the user in case of infection.
-
Some verifications are already done.
I know that Comodo prescans in order to assure that the machine is clean and refund the user in case of infection.
This is somewhat vague. Does this mean that you are in favor of a pre-scan? And do you know what these verifications are?
-
... A new AV would need detect every other AntiMalware + all variants
Hi DavidCo,
this is exactly what I meant. Difficult to realize, isn't it?
-
This is somewhat vague.
Why do we need to be precise all the time? ;D
Does this mean that you are in favor of a pre-scan?
No, I'm not. I think the process of installing takes too long.
The user could do a scanning after installing/booting.
And do you know what these verifications are?
If services/drivers are active and running, for instance.
But I'm not sure. And also not sure about which ones are detected indeed (if any).
-
Some verifications are already done.
I know that Comodo prescans in order to assure that the machine is clean and refund the user in case of infection.
This is somewhat vague.
Why do we need to be precise all the time? ;D
Because it in no way answered the question. You did mention Comodo though (are you promoting Comodo on an Avast forum?). Is that the (your) solution?
I would rather have the installer take a few extra minutes to get it right than to have to spend a great deal of time trying to figure out what the problem is. For a paid version I want it right the first time. I don't want to feel like I have purchased a beta program. Which I'm starting to question more and more each day. I can't count how many times people have been told to download the uninstall tool and reinstall. If it prevented most of these problems wouldn't you be for it? How many of these bad installs are there? How many don't get reported on the the board? With millions of users I think it would be quite high.
-
How many of these bad installs are there? How many don't get reported on the the board? With millions of users I think it would be quite high.
What you see on the board [forum] are the problems. Users who don't have problems do not report a problem and few come here to give a compliment although we do get them from time to time. So given the millions of users of Avast, there is a low percentage of people with "bad installs."
Many times, these "bad installs" can be contributed to conflicting security software that the user has on their system, remnants of previous security software that they [the user] are responsible for removing (not the company who they are going to install new software), existing malware preventing an AV from being installed, hardware problems, and firewall issues (connectivity for updates).
The user is ultimately responsible for their machine, including reading and understanding the EULA of all software. Do you read all your software EULA's? Most people do not. Most people when installing software do not read what they are clicking and just click "next" or "OK" without reading. Can you list how many AV's, FW, and other security software you had on your machine since you have owned it? You should as a responsible owner of that machine since you also should have uninstalled it by the vendor's uninstaller tool and not some other way which may cause problems down the road with another security software. Do not blame Avast for a "beta program," which it is not...the problem is that people need to be responsible for their machines. We are here to help them when they need assistance because we know that not everyone does what I have outlined above.
-
How many of these bad installs are there? How many don't get reported on the the board? With millions of users I think it would be quite high.
What you see on the board [forum] are the problems. Users who don't have problems do not report a problem and few come here to give a compliment although we do get them from time to time. So given the millions of users of Avast, there is a low percentage of people with "bad installs."
Many times, these "bad installs" can be contributed to conflicting security software that the user has on their system, remnants of previous security software that they [the user] are responsible for removing (not the company who they are going to install new software), existing malware preventing an AV from being installed, hardware problems, and firewall issues (connectivity for updates).
The user is ultimately responsible for their machine, including reading and understanding the EULA of all software. Do you read all your software EULA's? Most people do not. Most people when installing software do not read what they are clicking and just click "next" or "OK" without reading. Can you list how many AV's, FW, and other security software you had on your machine since you have owned it? You should as a responsible owner of that machine since you also should have uninstalled it by the vendor's uninstaller tool and not some other way which may cause problems down the road with another security software. Do not blame Avast for a "beta program," which it is not...the problem is that people need to be responsible for their machines. We are here to help them when they need assistance because we know that not everyone does what I have outlined above.
You can't convince me that what is seen on the board are the only problems. No way for you to prove that. What about the ticket system? How about the people that just give up on it? What about all the people that have fixed the problems on their own? Or the people who just went with another product?
And yes, I can list what antivirus/firewall/security suite has been installed on this machine. There has only been one and the vendors uninstall tool was used to remove the program. My computer is fairly new and has never had malware.
For everything you just mentioned is good enough reason to perform the scan. To me, you just made a good argument for it. Whether someone reads the EULA or not is not going to cure the problem. That is why I suggested to perform a pre-scan to help prevent these problems. Seems that me calling it a beta version really struck a nerve. "I don't want to feel like I have purchased a beta program" is what I typed previously. Anytime there is a problem the helpers on this forum direct users to Malwarebyte, Spyware Doctor, Trend Micros Hijack This, Kasperskys Rootkit removal tool, etc. The repairs and remedies are being farmed out to other vendors. How promising is that? Can't Avast handle its own affairs in detecting, blocking and removing malware? How about using Avast tools to troubleshoot and remove things like this. Until then "beta".
-
Because it in no way answered the question.
Sorry. Maybe somebody else then...
You did mention Comodo though (are you promoting Comodo on an Avast forum?). Is that the (your) solution?
Exactly. This is precisely what I'm doing from the last 8 years in these forums and also translating avast software. Also dedicating a lot of hours to help avast users. Give me a break...
[/sarcasm]
-
Because it in no way answered the question.
Sorry. Maybe somebody else then...
You did mention Comodo though (are you promoting Comodo on an Avast forum?). Is that the (your) solution?
Exactly. This is precisely what I'm doing from the last 8 years in these forums and also translating avast software. Also dedicating a lot of hours to help avast users. Give me a break...
[/sarcasm]
The way you worded it seemed like you were promoting it. How am I to know if it is sarcasm or not? Sounded like a recommendation to me.
-
Pre-scan before installing Avast?
« on: Yesterday at 02:08:57 PM » Quote Modify
--------------------------------------------------------------------------------
Would it be a good idea for Avast to include a pre-scan before installation proceeds?
Seems like many of Avasts problems occur because of remnants of old antivirus programs, failure to remove existing AV, running more than one antivirus, and/or malware already on computer before installation. Scanning for all of these issues would more than likely help to decrease the number of failed installs. This is not my idea and is already being used by other AV's to prevent such problems.
« Last Edit: Yesterday at 02:29:24 PM by Charybdis01 »
Feel free to close this.
-
For those of us who use layered security software that are compatible with each other, I would not want another security software to remove it. It is my opinion that the user of their machine be responsible for removing remnants on their machine that may be causing issues, which you seem to be repeating as the issue for "bad installs." BTW, I am an Avast user just like the rest of you, that also volunteers my time in helping others.
Feel free to close this.
Only you can do that:
- Please go back to the first open post in this topic, click the modify button in that Post and change the title/subject, add [Resolved] to the beginning of the title so this thread can be closed. Thank you.
-
I have gone through what I have typed and have really found nothing that I have "kept repeating" and remnants of old software is not the only thing I cited.
Difference is, I paid for my version which supports those who use the free version. In a free version I would expect some problems. In a paid version nope.