Conflict with avast antivirus, read first!

[AGGROxp]

I'm not affiliated with Safer-Networking nor Avast but am a customer of both. I believe Avast really screwed the pooch on this one... As of 12/03/09 CST, Avast Antivirus Database Update (VPS: 091203-0, 12/03/2009), is FUBAR. You would think Avast would have been a bit more proactive on rolling out updates.. It seems this update to the virus database for Avast Antivirus, is labeling everything related to Spybot, as a trojan (Win32:Delf-MZG). I've had 5 files labeled and the number is still growing... (VOL_TO~1.DLL, teatimer.exe, advcheck.dll, SDHELPER.DLL and SpybotSD.exe) I've also been seeing threads popping up on other forums, that it's also labeling system files as being infected as well. In turn some users are quarantining and deleting these files, which in turn are causing there systems to crash, hang and fail. For the meantime I would suggest not deleting any of the files that are legitimate resource files for Spybot or other programs you know to be safe, ESPECIALLY system files.. Safer Networking, you guys need to jump on board and start issuing statements before you start losing customers, as 95% of the alerts, are targeting spybot resource files and executables as trojans. I've also opened a ticket with Avast who is NOT being proactive in publicly adressing this...

[AGGROxp]

Avast has responded and issued a fix. Immediately update your iAVS from the previous version which has the issue: 091203-0, to the updated fix: 091203-1. Then update the program itself, from version: 4.8.1356, to the updated version: 4.8.1368. Restart your computer.

[AGGROxp]

Man, this could have gotten out of hand, real fast. Except for the 5% of users who were quarantining and deleting system files, which started to grow to 10%, 95% of the false positives were specifically targeting Spybot. What were they thinking?

[tashi]

Avast forum: Win32:Delf-MZG false positive issue statement.

http://forum.avast.com/index.php?topic=51647.msg436938

[AGGROxp]

Yeah I saw that. They issued that statement not too much longer after they acknowledged my ticket and released the patch. Noticed they didn't mention Spybot... Unless that falls under the "etc." category... At least our beloved "InspectorGadget" is still functioning properly!

[Mugrb]

For me, it not only took Spybot, but also screwed up Google Chrome, Ad-Aware 2008 (that I never used) and messed up my dial-up connection settings. My computer was so messed up I had to take it in to have it reconfigured as some of Windows DLL files were also corrupt.

[MarCn]

Originally Posted by Mugrb

For me, it not only took Spybot, but also screwed up Google Chrome, Ad-Aware 2008 (that I never used) and messed up my dial-up connection settings. My computer was so messed up I had to take it in to have it reconfigured as some of Windows DLL files were also corrupt.

I had the same problem, only worse. It not only messed up my dial-up connection settings, but all the interenet connection settings aswell. I had a lot of problem with my PC then.