M
Menno Hershberger
I just did an exorcism on a computer that was really really bad.
Ordinarily I would just clone the drive, wipe it clean and start over.
However, preliminary attempts to clean it were working pretty well, so I
went ahead and cleaned it all up. It was SP1 so I went ahead and did the
SP2 update and got all the latest updates to that. MSAS, Spybot S&D, and
AdAware all come up clean in all four user accounts.
BUT... about every other time I log off and log back in as another
user (user switching is turned off), I get the red popup... "Warning -
SureSideKick Settings Modifier is trying to install". Down below...
"Microsoft Antispyware has detected SureSideKick trying to install a URL
Search Hook on your computer." Of course I then pick "remove", MSAS
removes it and asks if I want to do a full scan. I do and the scan always
comes up zero.
There isn't an ssk*.* file on the computer other than an ssk.log it
creates when it tries to install. All that Hijack This shows is "Unknown
Search Hook - (no file)"
Anyone have an idea how to get rid of this one last little glitch?
Ordinarily I would just clone the drive, wipe it clean and start over.
However, preliminary attempts to clean it were working pretty well, so I
went ahead and cleaned it all up. It was SP1 so I went ahead and did the
SP2 update and got all the latest updates to that. MSAS, Spybot S&D, and
AdAware all come up clean in all four user accounts.
BUT... about every other time I log off and log back in as another
user (user switching is turned off), I get the red popup... "Warning -
SureSideKick Settings Modifier is trying to install". Down below...
"Microsoft Antispyware has detected SureSideKick trying to install a URL
Search Hook on your computer." Of course I then pick "remove", MSAS
removes it and asks if I want to do a full scan. I do and the scan always
comes up zero.
There isn't an ssk*.* file on the computer other than an ssk.log it
creates when it tries to install. All that Hijack This shows is "Unknown
Search Hook - (no file)"
Anyone have an idea how to get rid of this one last little glitch?