Today, launching my ACDSee Pro 6 image viewer, Avast! Free moved the file “ACDSeePro6.exe” to quarantine and marked it as “MSIL:Crypt-NB [Trj]”
Anyone else having this?
This got to be a false positive?
Same thing happened to me with ACDSee pro4… It was fine yesterday!
I got the same issue trying to start acdsee 5 pro… argh
if you have the file in chest, right click the file and upload to avast lab as possible false positive
it will then be sendt at next avast auto/manual update
Same thing this morning on three files in Avanquest’s PowerDesk v9.0, which has been installed on this machine for a long time. Avast virus definitions file version 130507-0.
I have the same problem when trying to start Audiosurf through steam
Just want to mention that I started another thread saying that I am having the exact same problem today with another program - Serif Page Plus 5. I hope they fix what seems to be an Avast problem. I am unable to use the software, and from what I have read, it does no good to reinstall the program with the problem because Avast will just flag it again.
avast! just identified a 3rd party component (ChilkatDotNet4.dll) that a recently installed piece of software uses (that was working fine yesterday) as being a MSIL:Crypt-NB[Trj] Developer of software is contacting Chilkat to be sure but thinks that this is a false positive.
Check the file VirusTotal - Multi engine on-line virus scanner Maximum file size: 64 MB
https://www.virustotal.com/en/
and communicate the results here in this topic.
You can send the file via email to avast lab
virus@avast.com zipper and password, please.
put “False positive” to email subject
Same problem with Ready Pro eBay listing software
All chilkat components are identified as infected
You can send the file
Submitting files from the Virus Chest to avast! virus Lab
Done!
Thanks
If it’s a false positive you can do this:
- Avast → File System Shield → Stop
- Reinstall ACDSee
- Avast → File System Shield → Settings → Exclusions
- Add “\ACDSeePro6.”
- Press OK to confirm
- Avast → File System Shield → Start
That’s it.
was fixed in update 130507-2