Quote Originally Posted by PepiMK View Post
That sounds more like the Adobe Reader upgrade destroyed your proper .pdf extension handling than Spybot-S&D hijacking it.

What we've found so far:

  • If you click an unassociated file with Windows XP 64 or later, Windows will ask you what to do with it.
  • If you click an unassociated file with Windows XP 32 or earlier, unknown files will be opened with the first "all files" handler available.

By unassociating .pdf, we could reproduce this. But then, if .pdf is not asociated with any app, there's something wrong
Skip a few paragraphs now if you're not interested in the technical background.
I did read thru the tech stuff, but I'm not sure it's relevant.

Of this I'm certain. While the problem existed:

1.) The .pdf file assoc. was "Adobe <something>".
2.) When I right-clicked a .pdf, "Scan with Spybot" was bolded and first in the list. And that's what ran when I double-clicked the .pdf.

From that and the fact that the problem didn't exist when running older versions of Spybot I concluded that Spybot was the culprit.

I cannot now say that with certainty. But neither can I refute it.

The problem is near identical to that dealt with in:

http://forums.spybot.info/showthread...264#post236264

While you can't replicate it, obviously I did (unintentionally).

Y'all have got beau-coup VM's lying around and none are running W2k and are suitable for testing this?

Regardless of that, your efforts are appreciated.

Puddin