-----Original Message-----
This stuff can be cleaned manually, although it is quite difficult.
The posts with the most information generically on such cleaning procedures
in this group are those from Jim Byrd. He is posting in response to
specific bugs, but the general procedures and tools in his links are more
generally useful I believe.
I don't have a lot of direct experience with cleaning these resistant bugs.
In the cases I have worked on, working at a safe mode command prompt level
using the attrib command to remove everything except index.dat from the
Temporary Internet Files folder was a primary part of the fix--but each bug
is different. Use all the tools you can find that show where things start
from and disable those you can't find and verify through copyright or other
information the source of. If you can't find a given item in a startup
entry that's a good clue--keep looking! The Silent Runners.vbs script is
an excellent tool, as is MSCONFIG, and lots of others.
And, if you can, by all means submit a Tools, suspected spyware report from
the machine--this'll give Microsoft more data points on your particular bug.
.