I liken this argument to users who have disabled malware via msconfig.
A lot of volunteers will ask those users to remove those items and restore normal startup . . .. Why? Why do this?
Why allow malware that has previously been stopped from running to start and potentially "phone home" for reinforcements??
That, to me, is a dumb practice (and yes, I used to do that back before I really considered the consequences). I think in the past when we were all too dependent upon HJT, you needed to do this to get a good look at things.
But with DDS / RSIT et al, that is no longer necessary. We can see what has been stopped and deal accordingly.....
PP
Have done this myself, but stress to the user NOT to reboot, just apply the setting, scan with hijackthis, then disable again in msconfig.
Without the reboot, that malware should not start.
Moderator
Featured Poster
Reputation Points: 1142
Solved Threads: 982
Most Valuable Poster
Online 12,164 posts
since Feb 2004