1.5.2.20 very slow startup...
I'm experiencing something similar, alas it feels to me now like 1.5.2.20 is back to the ill-behaving startup procedure of the 1.5 early versions
I've experimented with 1.5.2.20 and 1.5.1.19 (I downgraded properly to it, by first uninstalling 1.5.1.20 and reboot). Under
Immunize, 1.5.1.19 has 66229 "items" now on my old
Win 2000 SP4 box. When I do
Check Again, it's fast. Every time I click
Immunize, the whole computer hangs for ~45 secs at the end of the progress bar (no HT or DualCore here

) I haven't seen this before, it might have to do with my switching to Firefox for good (from IE6 :bigthumb

? 1.5.2.20 hung for ~60 secs at the same spot.
1.5.2.20 seemed to have more "items" to Immunize, >80000, but I may be mistaken there and I have no idea what the difference is if it is indeed so. I have updated to the lastest def files a.s.o. in my current 1.5.1.19. I don't have the impression that 1.5.1.19 is now crippled in some what w.r.t. updates. Can anyone give some more exact info on this?
A full scan (115220 threats, I believe this is the current definitions) takes ~13 mins in 1.5.1.19 and this is on an old P4 2.66 GHz Windows 2000. 1.5.2.20 needs ~35 mins to do the same, it was clearly slower -- visibly so through the whole scan. I didn't change anything on the computer (except SpybotS&D itself) deliberately in between these runs. No Web-browser was running, but all Anti-virus stuff a.s.o. Nothing was contending for CPU cycles during any of the scans.
I'd say something changed to the worse performance-wise 1.5.1.19 -> 1.5.2.20 :sad:
Going through all the options I tried to toggle "
Immunize on program start if program has been updated" and this is what affects the startup time so much for me. As soon as I untick this option, startup is really fast again regardless of the status of any updates.
One would think that this option means that no new Immunization will take place
unless a newer definition file for it has been d/l:d and installed during the startup, but in 1.5.1.19 as well as 1.5.2.20, it behaves the same. Perhaps I don't suss the semantics of that option..? I don't know, but I don't like it much.
At this point, I'm inclined to stick with 1.5.1.19 for the time being rather than using 1.5.2.20. Hopefully these issues will be fixed in 1.5.2.2{1,2,3,4,5,6,...}
Comments?
Cheers,
/M