Printable View
right, thanks..
Here's the DSLreports page discussing the issue for anyone that wants more info...
http://www.dslreports.com/forum/rema...flat~days=9999
EDIT-
hmm.. what it says is..
"If it states that it finds DLLs in directories like Windows\$NtUniinstallKB or Windows\WinSxS, you can safely ignore them"
not actually the sxs.dll file itself.
This whole thing is really confusing.
Duane: Sorry it didn't go well. :(
Isn't this a bunch of hooey, that we all have to go through stuff like this? What is it going to take for MS to really give us all some good help?
I'm responsible for around 20 PCs at work and due to software related issues, I can't move all of the XP machines to SP2. And to top this off, some spokes guy from f-prot says yesterday or so that they can't guarantee protection. Apparently these jpg/jpeg files can masquerade as other file types and may get missed by AV scanners. So even my hope that AVs could save us is tenuous at best...
DuaneB--Ouch!! ButEDIT--I understand you renamed the old one, so it was disabled. That should have prevented problems.Quote:
Well, I did it and now have two gdiplus.dll files in my System32 folder - gdiplus(old).dll (1,667KB) and gdiplus.dll (1,607KB).
After you did a system restore, what gdiplus.dll was operative? Did you have any further problems?
Anyone else have success in substituting the old gdiplus.dll with the new?
I used the sxs.dll in my system32 folder to replace the servicepack/i386 version (which I think was dormant anyway) and now I get a clean, no red, scan. Hopefully that's the end of it.
There are so many conflicting and confusing articles and comments about this issue out there it's hard to know what's accurate and what isn't.
For anyone that's interested I d/l'd and tested my a/v programs on a copy of the jpeg virus that was found on usenet... Trend Micro's PCCillin found it right off both in zipped and jpg format but I had to unzip it for Kaspersky and Ewido to detect it which both did successfully after it was extracted to a temp folder.