Windows Defender fails to remove 4 stubborn spyware

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have had this problem with Spybot S&D as well. There are 4 that come up
regularly after a full scan, but nothing after a quick scan.

When I direct the Defender to Remove these items, the failed message comes
up. How do I get them off my computer?
 
Start, run, eventvwr.msc <enter>

Click on the System event log

Go to View, choose Filter, and choose "windefend" in the source control.

Look for yellow triangle entries that give the precise path and location of
what was detected.

Report a possible spyware problem to Microsoft
http://www.microsoft.com/athome/security/spyware/software/support/reportspyware.mspx
AND
(e-mail address removed)
Full details on how to submit here:
http://www.microsoft.com/athome/security/spyware/software/support/reportspyware.mspx

Have you tried the cleanning operations running in safe mºde? (Spybot,
Ad-Aware, etc. etc.)

You can run in safe mode with networking.
http://www.ewido.net/en
http://safety.live.com/site/en-US/default.htm
http://support.microsoft.com/kb/890830

Еиçеl
 
Since you don't say what the error message number is, I'm guessing, but I
would imagine the detections are either in an archive file (zip type
compressed file) which Defender doesn't remove, since such files could
contain other wanted/needed information, or they are in a restore folder
which also isn't touched by Defender, or they are in a quarantine folder.
All occurrences are harmless in that state but could cause a problem if
uncompressed or restored.

You should see what files are involved by examining the system event log:
Do a start, run, eventvwr.msc, **click OK**, then click on

**System**, then View, then Filter, and scroll down the " event source"

control to reach Windefend, that will give you a view of just Windows

Defender-related events.

Look for events with yellow triangles

Then make a decision as to either deleting/ignoring/manually cleaning them
or in the other case emptying your restore folder and creating a new
restore point as described in these forums.

If the four don't match this description, let us know what the error number
is and what files are involved from the event log.
 
Back
Top