Why a new Avast 5 does not support automatic removal and other functions during the scan when you boot your computer? In version 4, they were very useful features. I beg for the return of these functions!
Does anyone know how to have the boot-scan automatically handle files without prompting the user in Avast 5? As it stands now, you have to wait for it to find a bad file and prompt you to press “Move all to chest,” but then you also have to wait for it to find a file inside the Windows directory and once again select “Move all to chest.” In Avast 4, you could instruct the program to automatically deal with these files so you could go to sleep while it scans through your entire collection of god-knows-what. This was a pretty useful feature in Avast 4.
The boot-time scan has never supported automatic removal by default (4.8) unless you pre-set these options when scheduling a boot-time scan (4.8 advanced options, see image).
So it looks like that option (advanced options) has been removed.
However, once you have one alert there are options displayed on the actions you want to take, and for each action option there is a Use this option for all detections (see image2 list, this is from 4.8 but basically the same). So that would give a sort of automated option.
Personally I rarely run a boot time scan and I’m loath to take automated multiple actions, certainly delete is nothing short of downright dangerous,‘first do no harm’ send to the chest.
Are you posting just for the sake of posting? You said there was no option except for the exact option in question, then plagiarized what I said about how Avast 5 prompts the user, and then supplied screen-shots to something we obviously know about as if it were news to us. And all the while, you don’t answer the posted question: “Why Boot Scan not support auto-remove functions?” Are you just post-happy?
Does anyone know if this option exists in Avast 5 or maybe why it has been removed?
I love forums. Bring on the flame… I know it’s coming.
You could read my post deeper too as there is a sodding big hint there too.
Since you don’t need the help I shan’t waste my time.
What help?
A Newbie arguing with an avast! Überevangelist should read his help more carefully.
Couldn’t agree more.
Please see here http://blog.avast.com/2010/02/04/v5-bts-auto-actions/
Vlk, thanks very much for that link to Avast’s blog which explains everything and answers my question. It’s good to know that the feature will be back in Avast 5.1.
I have just upgraded to Avast 5.1 and am fiddling around with it. As far as I can tell, the boot scan still does not support the auto-remove function like Avast 4.8 used to. Or… are the advanced boot scan features hidden somewhere?
No, that still isn’t in avast 5.1, no hidden settings.
Of course when you run the boot-time scan if something is found I believe the layout is still the same where you can answer the multiple response, Move to chest, do this for all detections option. So up to a point you can have semi-automated actions.
If the user can make any harm to his/her own computer IF automated actions are allowed, well, it’s a problem that avast team should face quickly and deep. I mean, only the first action is being asked… and the majority of the users will choose “do the same with all other detections”… Trusting in avast judgment.
White list, digital signatures, whatever… something must (or is already) need to be thought in order to release protection and safety in this case.
The user can’t be let by his/her own…
Now again…
So many users have been complaining about the removal of these options in v.5
The explanation is always the same: These options are dangerous.
I really don’t understand why the “ignore” option was dangerous, and had to be removed. ???
The “ignore” option did exactly what everyone asks for, it made babysitting the boot scan unnecessary.
Then afterward you just look in the log and decide what to do with the different positives.
The statement has been that the “ignore” option would be re-implemented in v5.1. It was not…
We are also told that the boot time scan only was thought as an emergency function.
I, and probably many other users actually used the v4.8 boot time scan for overnight scan of large hdd’s.
I guess noone uses the v5.0 or v5.1 boot scanner unless it is the last possibility…
If you want, you can use the sched.exe tool - it has always been there.
Igor.
Please explain about the the sched.exe tool. ???
Dangerous? And what will happen with a common user when use them? Lose data? Lose the capacity to boot?
What is dangerous here?
The ignore does nothing… The dangerousness is just letting the infection in your computer…
Exactly… We want all the actions back… and we want security also 
Tech
Please read the contribution before you answer it.
I did not write about the delete option, but about the ignore option.
I did not write about letting the infection stay in the Pc.
I will try to find out if the shed.exe tool is useful, as Igor writes.
Otherwise, here is a small boot time scan “workaround” that i succesfully have used with v.5. I guess it will not be official methode, but it works:
- Start the boot time scanner and notice where it starts the scan.
- Exit the scanner and start Windows.
- Turn off the Avast web scanner and download a virus to the area where the boot scanner starts the scan.
- Optimize the speed by renaming the virus file name to start with “a”
- Start the boot time scanner, and when it detects the virus, choose “ignore all”.
- When the scan is finished, read the scan log and take necessary action.
BINGO ;D Almost as in the good old v4.8 days…
No need to download a virus, just use the eicar test file, that cause avast to alert.
I’ve tried
I understand and agree. Just posted some different aspects.
Well… It could be a side effect of the ignore option…
Like David, I don’t think it’s a good method… not even a workaround.
Maybe I’m missing some technical difficulties as I’m not a programmer not an expert.
Maybe avast team could post a little more technical difficulties about it.
Can’t digital signatures be validated at boot time?
Can’t avast have a white list of necessary files to boot Windows?