new avast reporting Win32:Delf-MZG

Viruses and worms
1

I just updated to the new avast program build:sep2009(4.8.1368) And as soon as it loaded it started reporting the malware Win32:Delf-MZG trojan as being in all sorts of programs. pspad, skype-pm, wordweb, mobo hardware audio programs, registry, temp files, etc etc etc etc…
I looked on the site and saw that I should run
MBAM http://filehippo.com/download_malwarebytes_anti_malware/

and

SAS http://filehippo.com/download_superantispyware/

they didn’t find anything. So my question is … are you getting reports of false readings for win32:delf-mzg ? Which is kind of hard to believe since it is such an old trojan and I would have thought the replaced program would have caught this.
This is a brand new machine less than 2 weeks old running xp sp3.
If not then any suggestions?

2

It’s doing it for many of my programs. I couldn’t even let it do a memory scan on reboot as everything comes up the same virus and it won’t let me ignore all or send all to chest.

It’s 10 PM EDT and I hope it’s fixed soon.

3

This same problem with me

http://i182.photobucket.com/albums/x229/christarzan/Untitled-1.jpg

Please fix this problem soon

:-X :-X :-X :-X

4

I have Avast on two computers. Both started reporting Win32:Delf-MZG on multiple programs - even including my Logitech Mouse and Keyboard software. It killed at least one application that I’ve had to reinstall each time I have rebooted. Is there any way to roll back to the previous version until they get this fixed?

5

I’m now getting a ton of false positive Win32:Delf-MZG Trojan warnings from programs I know are safe, like my intel desktop monitor and a-squared anti-malware.

Please fix this ASAP guys.

I can’t run a program I use often because it’s being mistakenly identified as having the trojan.

I have about 12 programs that are triggering false prositives from the latest Avast update.

6

Fixed in VPS - 091203-1.

Milos

7

Okay…it was fixed with the new VPS download version 091203-1, but that file wouldn’t migrate to the scanner. Here’s what happened and how I fixed it.

After I downloaded the “fixed” VPS, I was still getting the same Trojan messages. 164 on my laptop alone. I opened Avast, and during start up and memory test, the alarms were sounding. Same issue. I hit “continue scan” since I knew these weren’t real threats , and let it finish the start up and memory test.

Now, when the scanner opened up, the VPS version on the scanner STILL read 091203-0…the bad VPS. I hit the update “bolt” and tried to download the 091203-1 version. It tried, but proceeded to tell me that I already was running the latest version. I opened up the scanner again and it STILL had the “bad” VPS 091293-0 as the current VPS file.

I went to my control panel and clicked on “add/remove programs” and selected Avast and hit “change/remove”. A screen pops up with 4 options, the one on the very bottom being “repair”. I clicked on “repair” and Avast proceeded to install the updated “fixed” VPS and everything was fine after that.

I repeated this process for all three of my PCs, and I’m happy to say the issue has been resolved. I ran full scans on all and not a single alarm.

Good luck!

8

Yes…I think it’s normally a good idea to try the repair option before re-installation.

9

I agree…I didn’t even know there was a repair option until I stumbled upon it. I’ve never had an issue with the program before today’s fiasco.

One thing to add…when it first ran amok, I moved all those files to the chest…many of them. Instead of opening up the chest and moving the files, I just did a system restore to 15 hours earlier and that took care of all the flagged/moved files in one shot. That may be a better option for some users…especially those who deleted the files.