The latest version of avast 2015 10.0.2208 isn’t compatible with OSes prior to XP (SP2 or later), it would be pointless to test on an old avast version as it doesn’t have the same functionality. So the same condition probably wouldn’t exist.
Prova, is your XP fully updated, I mean, even after SP3?
Do you use any other security program that could interfere? Antivirus, antimalware, firewall, etc.
Which should be the same as under avast 2014, weird.
Not being a SUMo user - but I’m not sure if that is the case. The reason I think this is that in avast 2015 there are new avast functionality that isn’t used in XP - so essentially it should be reacting in the same way as the previous avast 2014 version.
I’m at a bit of a loss as to why this would be seen in SUMo, XP, system combinations - its activity of pulling in software updates would certainly generate avast scanning activity, but that would have been the same in avast 2014.
A possibility being the DeepScreen and Hardened Mode features, which would have been updated - I know that Hardened Mode isn’t enabled by default, but the DeepScreen may be enabled by default. This may well generate more avast activity on the file system shield - you could try disabling these two if you have them enabled and see if that makes a difference and then turn them back one one at a time.
Another thought older XP systems may suffer more than later OSes, in that they haven’t got the same resources available in newer systems.
As far as I know, SUMo does not “pull software updates”. It checks versions during the scan and reports installed and available version#. That should not cause these enormous delays.
Deep Screen job might be it under the one hand doesn’t know what the other is doing theory.
I’d be curious if someone on 32-bit XP with the current Avast could do a careful, repeatable, multiple, timing comparison of just opening Properties on any .exe file - with and without active Avast shield. I suspect it’ll be rough to time, being short, but perhaps it will shed some light on the reported slow scans.
Another thing to look at during SUMo scan might be Avast logs - are the files SUMo checks listed in any Avast log? If ‘scan on execution’ is to blame, there might be something in the logs.
I had Hardened Mode mode disabled. I tried disabling DeepScreen, but the problem persists.
Not sure if you mean software or hardware resources. It’s not a hardware problem because in the same physical PC I have Win XP and Win 10, and on XP I have this problem but I don’t on Win 10.
I meant hardware resources mainly RAM and CPU - I found that 1GB of RAM or less (and many of that era did have less) on XP systems had XP swapping out to the pagefile.sys - I found 2GB really made a difference in performance and with RAM so inexpensive I moved to 4GB.
Thanx folks for the intense discussion of my problem. I think its clear now that the reason is the combination of XP and avast 10.x.
For me the waiting time for a fix (or even a reaction of the avast developers) was too long, so I changed - not the antivirus, but the OS to Win7.
And voila: SUMo runs smooth again.