Error message after scan...

[bomberb17]

I get this error message after scanning. (see screenshot) My windows XP is greek version, SP2, and the error message means "Cannot open file"". The system cant find the specified disk path". Then the spyware appear to have been cleaned but if i scan again they are detected again... Any ideas?

[spybotsandra]

Hello,

Which version of Spybot do you run?

Best regards
Sandra
Team Spybot

[bomberb17]

Spybot S&D 1.4

[bomberb17]

Any ideas?

[md usa spybot fan]

All of the Spybot detections that you listed are tracking cookies. Tracking cookies are third-party cookies and track users cross domain (site to site) profiling the user's surfing habits. If any transaction occurs where the user gives any personal info, then the tracking becomes personally identifiable. While tracking cookies may not be as insidious as some other malware, they are definitely spies.

If you are using Internet Explorer, you can block the same tracking cookies as Spybot detects by activating Spybot's Resident SD helper Browser Helper Object (BHO). To do this:

• Go into Spybot > Immunize
  • Check (if unchecked) the following:
    "Enable permanent blocking of bad addresses in Internet Explorer"
  
  Note: There are three modes of operation for this option:
  • Block all pages silently
  • Display dialog when blocking
  • Ask for blocking confirmation
    
    Most people prefer: "Block all pages silently".

There is also another alternative if you use another browser (or even Internet Explorer). You can block tracking cookies in your browser as follows:

• Why do other anti-spyware applications detect so many more tracking cookies?
  http://www.safer-networking.org/en/faq/37.html

******************

As far as the "Cannot open file" error message that you are getting. Can you locate and access that file using Windows Explorer and what is the file?

[bomberb17]

This message doesn't refer to a specific file... There is no file named inside the ""... That's what makes it so strange...

[bomberb17]

Still have the same problem, even after the latest updates...