Numerous Trojan warnings since last update.

[Vlk]

Official statement here: http://forum.avast.com/index.php?topic=51647

[REDACTED]

Thank you for the official statement although, personally taking 5 hours to release the patch is too long. With 100 million users I would think there would be at least 1 person keeping an eye on things whilst you sleep. I mean seriously, you don't release an update of any kind without first testing it. Please never let this happen again. I have strongly considered changing anti virus programs because of this. I may still so have fun with that. You're very lucky it happened whilst the US was sleeping. If it had happened whilst they were awake you would have had mayhem. I mean the forums hardly loaded when the US was sleeping and there was a problem, let alone if they had been awake.

I hope these how to's come out quickly and that they will solve issues of where files were moved to the chest

[VikingBabe]

Not everyone sleeps at night in the USA.  My "day" is "Night" and came on just before Midnight MST to work online.  My automatic AVAST updated as normal without any alerts showing. 

Then  I visited a forum where a poster reported the trojan about 8 pm MST (Dec. 2).  I disabled my AVAST...just in case... and came here.  Apparently my update included the repair.  If I came online several hours earlier, I would have been "hit" as well. 

I have to give "kudos" to the AVAST team who made the repair within this five hours.  However inconveinent it may be waiting to long....better a thorough hunting down than a "quick, stopgap fix".   

[Yanto.Chiang]

Hi Sparky13,

I agreed with you too,

Your country is lucky not screw up with this problem, but in my country indonesia for user avast they are screw up with this problem.
And back to us to asked about this problem.  

Please in the future, before release a new signature update just make sure it internally.

[Lo Tek]

well, that sucked.

Boot scan "caught" more than a dozen instances of "Win32:Delf-MZG [Trj]," mostly from lightweight appz.  When it started flagging stuff like my soundcard drivers I  canceled the scan and decided to look here for more info . Glad that I did.

Luckily, I have only a few minor appz to reinstall.

glad to see that the problem's been fixed.

[shae_32]

Oh man...tell me about it. 

Luckily, I too only had to reinstall a few things. (Even reinstalled my sound card drivers straight from disc) I about freaked out.

I did uninstall Avast and reinstalled it, so fortunately, it updated to the correct defs. But boy oh boy, there for a while I was like "what the heck?"

Anyway, thanks Avast for fixing this monster ASAP.

[brian943]

hmmm - I've got the last update (091203-1) and STILL getting the warnings??

[kenf]

I also had problems with the update and followed Avast's recommendations and moved the files to the chest.
I them did the later update and restored each file in the chest.
The problem is that when I do an update now, Avast has to submit and download certain files in order to complete the update and it takes a really long time.  Very frustrating.
I don't know if Avast itself is now corrupted.
Any advice.  Should I uninstall Avast and then reinstall?
Think that would fix the problem?
Thanks for any help.
First problem since having Avast but a big hassle.
kenf

[Sesame]

hmmm - I've got the last update (091203-1) and STILL getting the warnings??

You may have real virus but please send it to the chest.

I also had problems with the update and followed Avast's recommendations and moved the files to the chest.
I them did the later update and restored each file in the chest.
The problem is that when I do an update now, Avast has to submit and download certain files in order to complete the update and it takes a really long time.  Very frustrating.
I don't know if Avast itself is now corrupted.
Any advice.  Should I uninstall Avast and then reinstall?
Think that would fix the problem?
Thanks for any help.
First problem since having Avast but a big hassle.
kenf

Avast! should be O.K.  Simply, Avast! is working as it is supposed to be:  Avast! tries to upload these files while updating.  At least, it won't harm your system.  However, in this circumstance, it must be tough to the servers.  And yet, Vlk recommended to keep them...

[brian943]

hmmm - I've got the last update (091203-1) and STILL getting the warnings??

You may have real virus but please send it to the chest.

I also had problems with the update and followed Avast's recommendations and moved the files to the chest.
I them did the later update and restored each file in the chest.
The problem is that when I do an update now, Avast has to submit and download certain files in order to complete the update and it takes a really long time.  Very frustrating.
I don't know if Avast itself is now corrupted.
Any advice.  Should I uninstall Avast and then reinstall?
Think that would fix the problem?
Thanks for any help.
First problem since having Avast but a big hassle.
kenf

Avast! should be O.K.  Simply, Avast! is working as it is supposed to be:  Avast! tries to upload these files while updating.  At least, it won't harm your system.  However, in this circumstance, it must be tough to the servers.  And yet, Vlk recommended to keep them...

You mean that Win32:Delf-MZG was a false positive before but now its real? AVG time

[vhunter]

Some problem still remain in new update, because still getting warnings about Win32:Zbot-MKK for a few files (for example opera.exe). I think problem that Avast using old VPS 091203-0 in some case, because when I received warnings, it have message that use VPS 091203-0. But I updated to 091203-1 already   

[VikingBabe]

I checked my update logs to see which virus database VPS and time it was automatically updated December 2.  This is what I found (Times are in Mountain Standard Time USA)

12/2/2009   2:14:58 AM   ......The virus database (VPS 091201-1) was automatically updated.
 
12/2/2009   11:40:59 PM .....The virus database (VPS 091203-1) was automatically updated.

So, I am assuming my AVAST is ok then. 

[Tarq57]

brian943
can you please advise the original file name  and path/s of the warnings you are currently getting?

I was thinking a few minutes ago that it would be an ideal time for malware makers to produce new variants of these particular ones and unleash them. I hope they haven't. But I'm not especially evil, and if I thought of it, bet your bottom dollar they have, too.

[Milos]

Hi,
maybe there is/was running some scan on background, so the VPS didn't updated.

Milos

[REDACTED]

Hi Sparky13,

I agreed with you too,

Your country is lucky not screw up with this problem, but in my country indonesia for user avast they are screw up with this problem.
And back to us to asked about this problem. 

Please in the future, before release a new signature update just make sure it internally.

Agreed, I don't see why they couldn't have just tested it on one simple computer 

Not everyone sleeps at night in the USA.  My "day" is "Night" and came on just before Midnight MST to work online.

I was more referring to the standard hours that Americans are asleep

I have to give "kudos" to the AVAST team who made the repair within this five hours.  However inconveinent it may be waiting to long....better a thorough hunting down than a "quick, stopgap fix".   

I just don't understand a 5 hour wait. I mean all they had to do was take us all back to the old virus definitions. That would have solved the problem. Then they can get onto the fix for the virus definitions they attempted to release. I just don't understand why it took 5 hours for the fix. I mean I understand that maybe it took them an hour to realise there actually was a problem but then they could have easily fixed the problem and if they couldn't they make an emergency call to the boss so it can be fixed ASAP.