We have not had any program changes to avast recently that would have changed how ashServ.exe works so it can't of its own volition start scanning files for no reason. So what else has changed to cause the increased activity?
I was probably one of the first to bring this up and as a result of extensive testing totally disabled my firewall on boot as it made 450-500 file accesses, now they weren't all to the same files, yes log and ini files will have multiple accesses, but that doesn't make up the entire file access load.
Yes I think that Alwil should improve the boot up scan and as far as I'm aware it shouldn't scan multiple accesses to the same file as is the case in standard shield. However, because this is so early in the boot it may not be able to store and access the information in the avast files I just don't know and it was something that I don't feel was very well answered by the Alwil Team I the thread I created.
Perhaps there should be different levels of scanning at boot that could be included in the settings, low (just those files that are loaded, normal (Loaded and important system files) and paranoid (
) which would increase the number of files scanned.
There are files in my Program Files folders (I have two) that are scanned on boot that aren't used from one week to the next, so only files that are actually opened to run or for modification should be scanned by default.
