After the windows 10 creator update, MacAffe was messing with my system. Hence I uninstalled MacAffe and installed Avast. Tried to do a full scan. I faced two issues with Avast. Initially for approx 2-3 hrs the GUI was showing 0%, I was wondering if it is scanning at all. I googled and came to know about this issue. Hence I kept it running and finally after5.5 Hrs Avast was able to scan 470 GB of data. MacAffe hardly took 2 hrs for a complete scan. Am I the only one facing this issue?? Any suggestions to avoid this issue??
Did you use the McAcrap removal tool ?
U mean the MacAffe removal tool??? If yes, then I used that to remove MacAffe from my system.
What settings did you have for the full scan ?
The default settings.
Noticing that there was a reported ‘Virus Found’ in your first image, even on default settings if a virus is found then it goes into a higher degree of sensitivity (paranoid) mode. This is most likely for the increased duration of the scan.
Also in the first few scans avast would also be building up its Persistent cache data, this should also improve overall scan speed once it has been built up. Open the Full Scan Settings > Performance and ensure all options related to the Persistent Cache are enabled. You may also check the other scan settings and also the file system shield settings to build the persistent cache, ‘Store data about scanned files in the persistent cache.’
Please see the attached screenshot. Even though there was no virus detected, it took Avast approx 1.5 Hr to scan 165 GB of data. Also after changing the persistent scan setting the scan is still stuck at 0% from last 10 min.
As I said, “in the first few scans avast would also be building up its Persistent cache data” so initially you wouldn’t see any improvement, in fact because of the additional load, building up its Persistent cache database it could be slower initially.
However, what you are reporting doesn’t appear to be related to the above, but some people in the forums are reporting the scan sitting on 0% for some time. Personally I haven’t experienced it, but I rarely do on-demand scans other than in beta testing and in response to forum questions.
This is why I rarely do them - with a resident (on-access) scanner the need for on-demand scans is much depreciated. For the most part dormant/inert files are being scanned, the other active files are going to be scanned by the resident shields when they are activated.
As has been told in many threads already, the scan isn’t stuck at 0% it only looks that way.
Up to a point Eddy, for those scanning a very large amount of data, working out how long the scan is likely to take could take some time. During that calculation the progress would show 0%.
For those scanning less data, it would appear pretty quickly.