Avast Free Antivirus reports infection during RC1 installation


Posting rules: It shouldn't need saying, but... play nice. Please keep your discussions civil. You can disagree, just don't be disagreeable. And, of course, all of the usual stuff like no spamming. Tex adds: I'll be rigorously enforcing this as we go along. We're probably going to be a small community in a little lifeboat, so we can't have members at each others' throats. This is for the sake of the project as a whole. So when you post, pretend you're speaking in person with your very wealthy auntie who has always treated you wonderfully and currently lists you prominently in her will. I won't be tossing anyone out of the forums because we are all in this together (except spammers: immediate membership cancelation), but I'll delete suspect posts right away.


3 posts / 0 new
Last post
dke
Avast Free Antivirus reports infection during RC1 installation

Avast says object C:\Program Files\Lightzone\i4j3515029765524082554.tmp is infected with Win64:Evo-gen [Susp] and moves it into the container. LCTIFF.dll cannot be created.

Is there a problem or is it a false postive? My System is Windows 7 64 bit.

Regards, dke

Jacal
I have reported this to Avast

I have reported this to Avast already; if you do so too, it might speed things up. AV programs don't like "suspicious" unknown files, found in beta versions of open source programs. Just one day earlier, the same Avast on another computer didn't block the installation of RC1. I think the name of the "infection" is also suggesting this. Don't worry. You can disable Avast during installation and add LZ as an exclusion, like I did,  or wait for Avast to fix this.

 

Mart

 

Edit: Virustotal results:

https://www.virustotal.com/en-gb/file/be349b9d45557ec07700bb2aee12765376...

 

https://www.virustotal.com/en-gb/file/be349b9d45557ec07700bb2aee12765376...

 

It is the same file anyway. And it seems Avast has fixed this already.

 

dke
Thanks for your reply, Mart

I checked the file at Jottis malwarescanner in the meanwhile. It is OK.

I reported that to Avast.

Regards, dke