Is that reproducible?
When the scan stops, does the avast! service process (AvastSvc.exe) use any CPU?
The file is small. Avast generally stuck towards the end of the scan (Between 90% to 98%), at a random file, and it stuck
permanently, so I have little options, but to stop it manually.
DavidR: The setting for this custom scan are: Scan Rootkits (Full scan), auto-start programs (All users) and all harddisks.
Scanning for PUPs is disabled, because of the frequent false positives, this option causes.
Archives are scanned, and the heuristic sensitiviy is on the default, and the option "Test whole files" is checked.
The scan is scheduled weekly every tuesday, at 14:00-15:00.
Is that reproducible?
When the scan stops, does the avast! service process (AvastSvc.exe) use any CPU?
AvastSvc.exe indeed seems to use much of the CPU during the scan anyway, because of the high level of scan priority I setted this scan, so I think that when Avast stuck toward the end of the scan, this process slows down my computer.