The whole point of having an Anti-Virus program on ones computer in the first place is to prevent malicious code from tampering with ones computer. In this case ClamWin poses no threat to ones computer, in fact it is the opposite, and exists for the same purpose as does Avast, therefore, it is NOT a threat and hence my determination of a False Positive.
Granted, Clamwin should encrypt their database, but then Avast would/should detect ClamWin when it decrypts it’s database, causing yet another False Positive.
A simple solution exists, (and yes you are correct in that Wildcards should not be used), and in this case I see no reason why it should not be implemented by default.
For the Standard Shield provider (on-access scanning):
Left click the ‘a’ blue icon, click on the provider icon at left and then Customize.
Go to Advanced tab and click on Add button…
For the other providers (on-demand scanning such as the screen-saver or the Simple User Interface):
Right click the ‘a’ blue icon, click Program Settings.
Go to Exclusions tab and click on Add button…
You can use wildcards like * and ?.
But be careful, you should ‘exclude’ that many files that let your system in danger.
Thanks for the information for users having ClamWinPortable installed on their USB flashdrives. I also have that setup. However, for my home PC, I have installed the static ClamWin on my hard drive [Windows Vista Home Premium 32-bit]. What would be the exclusion string for it? Thanks in advance. ???
The exclusion string example is independent of OS presuming you installed it in the OS.s program files folder, if the vista program files are stored in a different location you need to change ‘program files’ to that folder name. I don’t use vista.
THAT IS A MESSAGE EVERY TIME I LOG INTO MY COMPUTER… EVERY TIME I RUN SPYWARE TERMINATOR AND AVAST… IS IT A TROGAN HORSE OR VIRUS… I HAVE NO CLUE WHAT TO DO?? IT HAS BEEN GOING ON FOR ALMOST A MONTH. ;(
IF ANYONE CAN HELP I WOULD GREATLY APPRECAITE ANY AND ALL HELP
BOBBIE
I’m for sure no expert for this, but I would suggest to contact someone from ClamAV that they solve this as it is their mistake I think…
It seems as they don’t encrypt their files strong enough…
Or uninstall ClamAV.
The detected file can be deleted in my opinion, as it seems to be a temporary file…
1. Clamav is not compatible with avast (i.e., both installed and running).
ClamAV isn't resident. I've used it for a long time as a second opinion when avast! detects something.
Using the exclusion outlined by DavidR in the earlier part of this post has worked without any problems. :)
