Once in a blue moon my HitMan scans take over 20 minutes, which is absurd. At that point, I know it is time to activate a RESTORE POINT. That seems to be the only way to correct an extremely slow boot time which coincides with an extremely slow HitMan Pro scan.
It is something to do with TCP/IP and max number of connections, or some such nonsense. Wireless + XP = SO DAMN BUGGY.
Think this is the culprit (via Event Viewer "system"):
"TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts"
When HitMan Pro begins to act as if I have a very slow wireless connection and takes 20+ minutes to scan (usually done in 2 minutes), I force it shut and then I reboot. When I see the little red light, by the power switch, on my tower, flickering away in a constant, yet dim lit fashion, I know it is time for a RESTORE POINT. It is peculiar to say the least.
Usually, ANY restore point works to remedy this condition, so it seems it is unrelated to new software or relative updates, but is due to some glitch that is remedied by system restore actions in themselves, not what is restored (if that can make sense).
The last time this happened, the only thing I had done was to update HitMan Pro, run a GMER scan (nothing found or removed) and updated Mozilla (The latter could be the culprit). After I did a system restore this time, which gave me my 20 second boot time back and fixed the slow HitMan Pro scan, Mozilla update would not function properly, so I could not get version 20. I then restored to a point a few days after the recent restore point that remedied the slow boot an slow HMan Pro scan. After the second restore point, Mozilla Firefox updated completely, and for some reason the new update package was around twice as large as the initial try, even though the restore points I used were no more than 5 days old.