According to the latest Build IceSword.exe seems to be a trojan. Is this a false/positive?
Win32:Stealth-H[Trj]
I sent the example of IceSword.exe to your labs (via VirusChest).
Greetings
Timo
According to the latest Build IceSword.exe seems to be a trojan. Is this a false/positive?
Win32:Stealth-H[Trj]
I sent the example of IceSword.exe to your labs (via VirusChest).
Greetings
Timo
You could also check the offending/suspect file at: VirusTotal - Multi engine on-line virus scanner I feel virustotal is the better option as it uses the windows version of avast (more packers supported) and there are currently 30 different scanners.
Or Jotti - Multi engine on-line virus scanner if any other scanners here detect them it is less likely to be a false positive. Whichever scanner you use, you can’t do this with the file in the chest, you will need to move it out.
If it is indeed a false positive, add it to the exclusions lists (Standard Shield, Customize, Advanced, Add and Program Settings, Exclusions) and Restore it to its original location, periodically check it (scan it in the chest), there should still be a copy in the chest even though you restored it to the original location. When it is no longer detected then you can also remove it from the Standard Shield and Program Settings, exclusions.
What version of Ice Sword are you using?
I have Ice Sword 1.22 English beta 3.
I right-click scanned every related folder and the program itself and it appears clean with Avast.
Also, are you using the last 000773-3 VPS file?
IceSword 1.20
VirusTotal showed only Avast which detected this “virus”. Panda marked it as “suspicious file”. All other suites (even Kaspersky or Antivir) didn’t show a virus.
I think I should upgrade this programm to 1.22
Greetings
Timo
Yes, it is just a FP.
Recommend that u switch to 1.22
Please, follow David’s advices and help avast to correct this detection.
Before doing anything, try to update the virus database and see if it still detected as being infected.
Updated to 1.22 and everything is fine now
The VPS Update from yesterday didn’t fix the problem with 1.20 though. I recommend you use IceSword 1.20 if you want to fix this f/p