Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Paul1149 on May 04, 2010, 10:39:55 PM
-
Hi,
I just tried to run a boot time scan on my desktop. I set it and went away for hours. When I came back I found Avast stuck on a dubious PUP. All that time was wasted. Is there some reason Avast doesn't by default simply make note of the possible offender and keep on scanning? I see that this option is obtainable for the other scans, but I don't see it for BTS.
Secondly, is there any way to set exclusions for the BTS, or do program exclusions automatically kick in? There are a bunch of folders I'd like to exclude in order to save time.
Thanks,
p.
-
It was asked before, i.e., the automated actions of the boot time scanning.
I agree with you that they should be returned back (as they were on avast 4.8).
-
Yes please. And please note that this really is a showstopper if you rely on a remote desktop connection/VPN or whatever similar to get access to your box. Please put the feature back.
-
It's just common sense. Why would anyone want to stop a scan merely because it found something? Raise a flag? Yes. Stop the scan, emphatically not. This is completely counterintuitive, and very frustrating.
-
The automatic actions for the Boot-time scanner will be back in v5.1.
For v5.0, please see here: http://blog.avast.com/2010/02/04/v5-bts-auto-actions/
Thanks
Vlk
-
The automatic actions for the Boot-time scanner will be back in v5.1.
Yay! Thanks. 8)
-
Vic, to be clear about this, I am not necessarily arguing for BTS automatic actions, but rather for the completion of the scan before any actions are required. If at the end of the BTS the user would have to manually deal with the results before the machine went on to boot up, that would be fine with me. My problem is coming back to a machine hours later to find the scan stalled at 3%, waiting for my input - and facing the possibility of that happening repeatedly as Avast found other possible viruses.
The other thing I would like to see are exclusions for the BTS. I have a large storage folder whose exclusion would save a lot of time from the scan. And the windows update files, of the pattern C:\windows\$* are also vast and, I think, can be safely excluded.
bw,
p.
-
Global exclusions should work even for the boot-time scanner.
-
Ok, thanks. I'll check that out.
p.
-
Thanks Vlk, I have forgotten that blog thread.
-
Global exclusions don't seem to be working for the BTS. For instance, I set *mirc.exe and c:\vault\* for exclusion, yet mirc.exe was hit for the mirc-Z virus and I saw C:\vault... being processed. Booted up, I just checked my settings again, and made sure that my exclusions had indeed taken, and they had.
-
Strange... we're talking about the Settings / Exclusions window, right? (and not e.g. about File System Shield exclusions)
-
Correct, the globals. There are no exclusions for the BTS.
-
OK, I can see the problem... I'll fix it somehow.
-
we can make avast to finish the entire BTS and finally it shows a log with location of detected items..the user can select his options whether to delete or ignore here..thus BTS is neither automatically deletes files nor stops the scan and asks user..! ;)
-
The problem with global exclusions should be fixed in the next virus database update.
-
Thanks, Igor.
-
Igor, exclusions working well here now. Thanks.
p.