This problem is starting to get to me, made a clean install on my system to see if that helped, but it didn’t. If i make a shared folder on my computer, and even if it aint connected to other computers/internet, it still see *.exe files as infected by Tenga. Is there a way to bypass that error, and the reason i call it an error is that only avast see it as a virus. (even if it’s program files made by myself)
Since Tenga is a file infector, I’m not convinced that it’s a false alarm.
If you take one of the reported files and upload it to www.virustotal.com - what results do you get?
It found nothing. it’s not like im a newbie, im an network admin. When doing a clean install on a system containing only new components, not connecting it to any network, creating a shared folder, and copying *.exe files to that folder mainly from root\windows\ not installed other than avast and it tells me after reboot that everything is infected by tenga, that makes one wonder if there aint a problem with avast and network shares. So far my only option seems like installing another antivirus program, coz im getting pretty feed up with loosing my *exe files
It’s not like false alarm can be produced without any reason on clean files (without even updating in the middle). Either they’d be already detected during copy operations or something is infecting you somehow different.
I too am a little puzzled.
I have just performed avast scans on two systems (both Win XP SP 2 US English implementations). One system is running the current beta version of avast (with latest VPS) the other is running current production avast (with latest VPS). I have also performed cross system scans of network shares. No errors are reported on either system.
Were this a generic avast problem I think it would be more reproducible.
Can you pack a few of those “infected” files, detected by avast!, into a password-protected ZIP or RAR and send it to virus@avast.com ?
Thanks.