Cleaned up worm; now no "nstask32.exe" file

[Jenny]

I fixed the Blaster vulnerability and then removed
the "Win32sockdrv.dll" file that showed up as a virus on
my Norton Anti-virus scan, but now my computer says it
can't find "nstask32.exe" when it reboots. Is this file
necessary? Microsoft
(on "http://support.microsoft.com/default.aspx?
kbid=826955") says that I should look for
the "nstask32.exe" file and delete it if found (along
with "msblast.exe", "Teekids.exe", "Win32sockdrv.dll",
etc.). So, that makes "nstask32" sound like it is a
virus.

Does anyone know anything about "nstask32.exe"?

J

[Andy Allred [MS]]

Jenny,
Though you removed the virus, there were registry keys left behind that used
to start the virus when Windows started. Now that the virus is gone, you
still have these registry keys trying to start a non-existent file - this is
a harmless error but is obviously annoying, right?

Symantec has some information on how to manually remove these registry
entries, but use caution if you're not familiar with editing the registry,
see the following link:
http://securityresponse.symantec.com/avcenter/venc/data/w32.randex.e.html

After removing one or two registry entries, this benign error will go away.

Good luck!
--
Andy

This posting is provided "AS IS" with no warranties, and confers no
rights.
================================================== ===

"Jenny" > wrote in message
...
> I fixed the Blaster vulnerability and then removed
> the "Win32sockdrv.dll" file that showed up as a virus on
> my Norton Anti-virus scan, but now my computer says it
> can't find "nstask32.exe" when it reboots. Is this file
> necessary? Microsoft
> (on "http://support.microsoft.com/default.aspx?
> kbid=826955") says that I should look for
> the "nstask32.exe" file and delete it if found (along
> with "msblast.exe", "Teekids.exe", "Win32sockdrv.dll",
> etc.). So, that makes "nstask32" sound like it is a
> virus.
>
> Does anyone know anything about "nstask32.exe"?
>
> J
>