What components, other than the shields, did you allow when you installed avast.
Did you do the default or customized install ?
Which Windows version?
How much RAM in the PC?
Avast free with shields and only browser protection allowed.
All other options sandbox, ... where unchecked at custom installation time.
I use only the screensaver scan. Exceptionally I perform a manual scan on some folder (Downloads, ...)
My system is W7 64b home premium sp1 all updates and hot fixes; 6G memory (no it's not a virtual memory effect). I re-installed it 2 weeks ago but the issue is at least one year older. The avast issue, among other small problems, with ie11, WMP, ... in particular, was a reason why I decided to re-install everything from the factory state.
I have made a little more investigation to understand when the problem occurs. Several times a week but at random - apparently.
One reason why the unexpected scan is not always noticed is that the disk activity associated with it is not at a constant level. Sometimes it's very high (HDD led constantly lit) sometimes it's weak (a few led blinks per second).
There is another reason why I've not always noticed the issue after a screensaver period. Actually
- the scan does stop when the screensaver stops
- EXCEPT if the idle time has been long enough that the display has been switched off for power saving
- AND not long enough for the PC entering the sleep state.
In my case 5 mns for SS, 15 mns for display off, 1h for sleep. So for less than 15 mns of SS the scan stops when the SS stops, between 15 mns and 1h the scan continues even though the SS has stopped, after 1h the scan has stopped when the PC wakes up (be it because of the sleep state or because the scan is complete, I don't know yet). Such test is time consuming, I have repeated it twice (not statistically valid ...). I'll try with shorter delays..
Now I have set the display off delay to <never> so I should not need to stop the avast service manually, hopefully.