I have a questions (and a problem about screen saver scan.
Question:
Is it normal that screen saver scan ring “Scan complete” sound when it finished first scan? If so, is there any way to prevent it (except for disabling all “Scan complete” sound)?
Problem:
Yesterday I noticed SS scan did not stop even if screen saver itself was stopped over 10 minutes before. It suddenly rang “Scan complete” sound (and I noticed this).
Does anyone know about these things? I installed avast from scratch just a fer days ago, and I started using SS scan…
P.S.
I’m sorry for not posting constructive things but only questions… :-[
I fixed the playing of the “Scan completed” sound in the screensaver, I doubt that was intentional (though I’d say it was there since the initial 5.0 release).
As for the scan running even after the real screensaver has finished… well, that certainly shouldn’t happen. The problem is… would you be able to reproduce the problem?
Thanks, waiting for the new release.
I used SS scan for the first time so I didn’t notice that.
As for the scan running even after the real screensaver has finished... well, that certainly shouldn't happen. The problem is... would you be able to reproduce the problem?
I successfully reproduced it... I heard scan complete sound just now :'(
It seems if screen saver scan continues over 10 minutes or so, scan goes mad. It works properly when scan continues only a few minutes.
Something odd indeed.
According to “Resource Monitor” tool, process “System” accesses many files which completely unrelated (some old installer, recovery volumes etc.) and “AvastSvc.exe” also scan them. However File System Shield does not scan them (avast icon not rotating, graph shows nothing).
After 40 minutes today, it rang scan complete sound and scan logs shows Screen saver scan was completed. But the finished time shows about 40 minutes ago, which is the exact time that Screen saver stopped. There was no entry about it before scan completion.
Unfortunately attached picture doesn’t contain AvastSvc.exe processes in lower column, it was difficult to get this because Resource monitor tool became nearly unresponsive due to high HDD accesses.