Avast blocks new2007 version

Add the entire directory of PowerTools to the "Exclusions list" in avast! settings screen for the time being. I've just sent them an e-mail, and I suppose it's a matter of hours 'til they update the iAVS to reflect the positive.

EDIT: Don't add it, it just doesn't work :

This problem should be fixed by Macecroft and not Avast. Release 403 worked perfectly fine with Avast. The difference in code lies with JV16 Powertools.

I feel that it's not that easier...

GTX66 wrote

... For me this latest release was the only one that Avast Reported. All Prior releases were not problematic with Avast

The only one for me too. What do you make of posts from other members that other AV products are failing to detect the trojan seen by Avast! ?

I've just sent the file to ALWIL Software for them to analyze, instead of a simple e-mail complaining about the positive. I've also uploaded the file both to Jotti's VirusScan and to Hispasec's VirusTotal. avast! and eSafe both detect the file as infected with a Trojan, so I assume both developers will have to fix their way.

Did the people that got this "false detection" have the "Check for Updates" thing checked when they installed jv16PT by any chance? Just a thought.

ALSO, It's strange that the times when people got the false "You have Pirated Software!!" warning after installing a new version of JV16PT, were also the times when people complained about "False Trojan Detections". Hmmmm . . . .

GTX66 wrote

This problem should be fixed by Macecroft and not Avast. Release 403 worked perfectly fine with Avast. The difference in code lies with JV16 Powertools.

The problem is in the Avast product, in ours. Even in theory, how would it even be possible for us to fix the problem? I mean we don't know what causes the Avast to think our product contains a virus, therefore we can't possibly fix it either.

I've been using avast! for a couple of years without any problem with PowerTools. For this experience, I also know that, although it sounds quite incredible, that avast! scanner flags as 'infected' executables with bugs. Yes, that's not made up, it happened to me a couple of times with another software (XMPlay) that had some tiny bugs, and after those were fixed, avast! didn't detect the software as 'Trojaned' anymore, although in this case, it used heuristics to detect that possible Trojan instead of the iAVS like in this case.

Lashiec wrote

I've been using avast! for a couple of years without any problem with PowerTools. For this experience, I also know that, although it sounds quite incredible, that avast! scanner flags as 'infected' executables with bugs. Yes, that's not made up, it happened to me a couple of times with another software (XMPlay) that had some tiny bugs, and after those were fixed, avast! didn't detect the software as 'Trojaned' anymore, ...

This is just coincidence, there is no way the presence of bugs could cause an antivirus program to mark a program as a virus.

After all, it's pretty much impossible to detect bugs from compiled programs (i.e. exe files) automatically, if it could be done software developers would naturally use that to find bugs, not beta testing.

My Avast Program has updated the IAVS twice since this problem began. I my now to assume that it is fixed????

Yes, I have received the response for ALWIL virus labs that the problem was fixed in the latest iAVS update (761-2). We can go crazy on PowerTools again! :

But Jouni, you'll agree that it's a pretty impressive coincidence. A virus software acting like a debugger!

Yes, thank you. I have the "Standard Shield" back on and get no Avast! warning pop-up.