I am running Windows XP SP3 with the latest updates. I have been using Avast for about 3 years. I also have Zone Alarm with only firewall turned on. I have Avast Home edition version 4.8.1296 running. The VPS is up to date with a version of 081226-0. After the latest software update a few weeks back, the On Demand scan runs till about 15% and then stops. Around the same time as the software download I also made changes to the HDD config. Till recently the Harddisk had 3 partitions but only C was active and the rest were unpartitioned. So a month back I enabled the rest of the partitions so I now have C, D, E. This should not have any bearing on it because it stops on C itself which has always been there. The option I pick for On Demand scan are - thorough scan, scan archive files, local drives only, highest sensitivity. When I run the scan it runs till about 15% and stops. There is no specific folder where it always stops. It first starts scanning C drive and after 15% it stops. It’s very consistent with that percentage. I have left it running all night and even after 12 hours it does not budge. I have rebooted and tried and left it running all night but with same result. But that 15% seems to be precise. So I once started and watched and sure enough it stopped at 15%. The folder where it stops is random but the percentage is consistent. I looked at all log files but I have not been able to see anything untoward.
Anyone else having this issue? Thanks in advance for your help. Appreciate it.
Thanks to Avast for providing a fully working free version. Nice of you to do that.
I have found a workaround. I can scan individual drives and folders.
I wonder if the Free Home Edition has a limit on the number of files/folders it scans. I can not think of any other reason.
For sure not.
How exactly does it freeze? Does it happen always approximately at the same place/folder of the scan?
Do you see a hard disk activity (when it freezes)? Is only the program frozen, or the whole computer (possibly with mouse cursor)?
Additionally, you can go to the program settings and turn on the creation of the report file (with “OK files” to be included as well in the report). This way, you can find out where the scan really stopped (it’s going to be close to the end of the report).
After avast! disappears, check the end of the report file - the “troublesome” file is likely to be close to the end (close in the sense that this particular file will probably not be written in the report, but the previous one will be the last line, so it shouldn’t be hard to guess). We would certainly like to have this file - if it really causes problems to avast! - so that we could fix the problem.
The report file created (if you turned it on in program settings) will be (default location) at \Data\Report\Simple User Interface.txt