I just finished installing the new IrfanView 4.50, which I downloaded from Major Geeks. I don’t believe I even got around to actually bringing it up. I think I was barely closing the last IrfanView window after the install was finished when avast throws up a Threat blocked window. I have included an attachment image of it.
Anyone else experience this?
I was going to send the alleged threat file to VirusTotal, but the file is not at the location indicated by the path. I guess that’s because it was blocked.
Downloaded and installed the 64 bit version from http://www.majorgeeks.com/
without any problems. No notification from Avast.
Even checked the file before installing - No warning.
I must admit that there IS a difference in my environment and y’all’s. I have avast 12.3.2280 and this version certainly doesn’t seem to like something about IrfanView 4.50. b[/b]
I installed it again … and again, right after closing the last IrfanView window, avast threw up a Threat blocked message.
Then I conducted an experiment. I scanned the setup files for both IrfanView 4.44 and IrfanView 4.50 with avast, SAS and MB3 around 4 times each. IrfanView 4.44 would always pass all 3 scans with flying colors. IrfanView 4.50 on the other hand, every time that MB3 was scanning, avast would flag MB3 with a Threat blocked message like the 2nd one that I have attached.
Yeah, I know what y’all are gonna say — “You need to update to the latest avast 17!!!”
Well, right now I cannot do that. A couple of weeks ago, my sister’s laptop, the one on which I would periodically download my apps updates finally went kaput. So, now I no longer have that High Speed Internet source to use for large footprint apps.
Up to now I have had no problems with my avast 12.3.2280. This IrfanView issue is the 1st time.
Thanks for reporting it as a false positive, Pondus.
I vaguely recalled talk around here that avast and MBAM / MB3 no longer get along very well. But, that said, though, I found it odd that why did avast allow MB3 to scan the IrfanView 4.44 setup file successfully all 4 times … while the scan of the IrfanView 4.50 failed ALL 4 times?