Virus Chest Destroys Files When Restored

No.
The Tenga detection has been there for years, untouched. The behavior you mention (infections on various exe files suddenly appearing) exactly matches Tenga, being a file infector. So no, this is not a false alarm - something is infecting the files on your computer or network.

The program updates also didn’t change anything about handling the files.

As for destroying the files… well, a file infector - such as Tenga - might certainly corrupt the files itself. It’s also possible that the detection is triggered “in the middle of the infection” (the file was already modified by the virus so that avast! detects it - but the infector hasn’t finished yet, so the file is in some kind of intermediate state) and the file was moved to Chest at that moment, in a corrupted state.

However, when dealing with file infectors (and I’d say avast! should be able to repair Tenga, even though I’m not 100% sure) - don’t expect that the file will be restored exactly, so that the hash matches the original - that’s just not possible. Some parts (e.g. a few EXE header fields) are irreversibly overwritten by the virus.

You have been though a lot and I can empathize with your frustration.

Question:

  1. Did you ever upload any of the files in the Chest to Avast for analysis? If yes, they would have analyzed them on the next virus definition update and if there was a false positive it would have been fixed and pushed out to users for the next update.

Since this is not a wide spread problem, I recommend the following:

  1. Run an OTS log so that we can see what is actually going on inside your machine and analyze better. Here is how to run OTS:

Check the information on the first post of this thread under Virus/Worms for you to check your machine for malware: http://forum.avast.com/index.php?topic=53253.0.

Follow the directions for obtaining the OTS logs (save them as ANSI and not Unicode). Post the OTS log as an attachment (Additional Options > Attach > Post).

Do not make any changes to your machine after you post the OTS log or you will have to repeat this all over again! We will analyze your OTS log and report back to you. Thank you.

Windows XP SP3 has a malware infection rate per 1,000 installations of more than six times that of Windows 7 x64. It amazes me that people stay on any release of XP.

Windows XP SP3 32-bit has an infection rate of 15.9 per thousand systems, while Windows Vista SP2 32-bit has half this infection rate, 7.5 per thousand. Windows 7 32-bit nearly halves this again to 3.8 per thousand, while Windows 7 64-bit managed to get the infection rate per thousand down to 2.5.
[url=http://www.zdnet.com/blog/hardware/windows-7-more-malware-resistant-than-xpvista/12786] http://www.zdnet.com/blog/hardware/windows-7-more-malware-resistant-than-xpvista/12786[/url]

I think it’s a matter of budget and hardware limitations only…

I have never used any Windows version other than the one that came pre-installed on the machine. When I get a new computer , it will have Windows 7, but I’m not switching from XP on this one. I used 98SE from 1999-2005 and I’ve been on XP ever since October of 2005 and am very satisfied. I’ve also never been infected by anything since I first started using a Windows computer.

We should get back on-topic and wait for the OP to respond to Post #21 as this will give us more information to work with to fix his problem. Thanks.

Do you have any hope that he come back?

I’m beginning to question that, but I’m giving him hoping he does by giving him another day or so. :-\

[b]Hi…

I’ve also had a similar problem like this before a long time.
But that has happened only once, what i was thinking is that the virus programs have infected those software’s because avast haven’t detected the same software’s as threats before and after that event.

Thank u[/b]

Malware (infections) are changing all the time. Yes, according to Post #20 by our senior Avast Team member, he explains the situation best.