Hi guys.
This might have been answered before but,
Are exclusions in settings applied when doing a boot time scan?
You see. I get a bunch of files that can not be accessed or are being used by other programs that populate my scan reports so I excluded them from scan, however it would be a good idea if they are scanned once in a while with the boot scan.
Thank you for your time.
You see. I get a bunch of files that can not be accessed or are being used by other programshttp://forum.avast.com/index.php?topic=61663.0
When you schedule a boot time scan you can specify what areas to scan. Also if I remember rightly the avastUI, Settings, Exclusions are still excluded.
First before doing anything else:
What are the file names and locations of the files that can’t be accessed ?
What reason is given for them not being able to be accessed ?
The reason there are many legitimate reasons why files can’t be accessed, but for me I wouldn’t be excluding them for that.
Pondus. Thank you for the link.
DavidR.
So whatever files I exclude from scanning in > avstUI > Settings > Exclusions, are also excluded during a boot time scanning? Sorry to ask again, I just want to make sure I understand correctly.
I have a few files from Spy Sweeper ( the same files since Avast 4.5 ). Docs & Sett, and Windows\sys32. All of them are not access by Avast because they are being used by another process.
I just want to know if it is OK to exclude them from “normal scanning”, but I would like to scan them when they are not being used by other process for example during a boot-time scan.
Thank you again.
As far as I can recall the exclusions are honoured in the boot-time scan.
As I said I certainly wouldn’t exclude them, if there is a legit reason, the scan concludes and lists those files in use, I want to know what is going on in my system, including files that can’t be scanned and why. It is easy to just ignore them in the results as there would be associated avast action as it isn’t an indication they are infected, just can’t be scanned and the reason.
I wouldn’t have expected .tmp or .log files to be scanned as I would have considered them a low risk or target of infection.
Why are there so many of these .tmp files in the wrstemp folder, are they signature updates things that have been quarantined, etc. ?
If they are truly temp files then you could clear the SpySweeper temp files before the scan.
If you are trying to exclude these files it is best not to exclude the complete folder as that would leave a hole in security, a better exclusion mask would be C:\Archivos de programa\Webroot\WebrootSecurity\wrstemp\SSMS*.tmp (the * is a wildcard so you are only excluding .tmp files beginning with SSMS.
David.
OK. They are honoured.
Yes, It is better not to exclude them so that I know what’s up with them when I do a boot-time scan.
Since quick and full scan parameters can not be changed (modified) but on schedule scan, I do not know if .tmp or log files should or not be scanned.
SS has always, since I can remember, had those .tmp files in the wrstemp folder. They are written on start up, and can not be modified unless SS is completely disable.
Thank you for the SSMS*.temp tip; However I will follow your first advice, It is better to check them out with a boot-time scan once in a while.
Thank you DavidR
You’re welcome.
Well in a boot-time scan in theory you shouldn’t get this issue anyway as nothing else should be using them (even if they are scanned), that really is the point of the boot-time scan.
It is normally only used when you encounter a malware problem, etc. that can’t be dealt with when windows is running, file in use, etc.