In doing a manual full system scan today, I noticed Avastsvc.exe is only utilizing core 0 of the four cores I have on my i5-2500, with no way around due to the native defenses of Avast in regards to permission access. Is this feature intended to try and maintain performance levels for the rest of the system? I don't mind if it is just an oversight in coding with the intent being for scheduled system scans running when the system is idle or in the background...
Is it possible to implement the usage of more than one core in a program update in the future? The utilization of only one core seriously slows down the process a full system scan would take though when one is manually scanning for system up-keep/setting a base-line.
