Whole MikTeX 2.9 distribution is marked as false positive. The false positive upload form is not sufficient enough to upload 366 files.
How to upload these files? Even when so, I have uploaded several samples.

Feel free to look at here: https://www.virustotal.com/#/file/1e3c13d46a2c06c6cd242f66d86c40e3e4bed3926b6c2320cdb241dcb1009cd7/detection

You do not need to report all files that are falsely detected if they detect the same virus. Just report one of them, note that there are others falsely detected as well, and insert a link to one of the false positives on Virus Total.

Virus Total will/should report false positives to the antivirus company involved, but Clam AV may not notice it (no one works on Clam AV detections full time), so submit your own false positive with a link to Virus Total to make it more noticeable to Clam AV.

Thanks for using ClamWin!

Regards,

Thank you for your effort but there is still too much false positives remained.

All I see are 2 versions of falsely detected malware found in several different files. As I said, just send one file of each false positive to Clam AV. To speed things up at Clam AV, you might upload each file to Virus Total and include a link in the information you give to Clam Av. I have also learned to send a FP file to Virus Total a couple of times to make it look like it is a serious problem to help speed up Clam AV's signature correction.

You do know that you can exclude a file from scanning by ClamWin? Read the Help manual (I think it will tell you how to exclude).

Regards,

I have already done actions you recommend.


Good idea thanks.

Yes I can ignore problem but I still hope that there is interest to fix ClamWin for everybody. I will do it if you refuse to fix false positive.


Anyway I have installed another antivirus - McAfee endpoint security - at work, that even cannot be configured and erases files without user agreement. It works worse than malware or virus because user is even not allowed to change behavior. The file simple disappears. Clamwin is much more better because it silently do not erase files. McAfee is proud that it solved me 6500 problems, but it caused me many days of useless work or at least erase all .clamtmp files on temp directory.

ClamWin can not fix most false positives. ClamWin uses the free, open source engine from Clam AV (owned by Cisco). Clam AV is responsible for the scanning code and the virus signatures and needs to fix any false positives detected by its signatures.

Clam Av is the only one who can fix most false positives. Until Clam AV fixes a FP, ClamWin users can only exclude the file from scanning with ClamWin via using menu item: Tools, Preferences, Filters, Exclude Matching File Names.

If ClamWin detects a file, and it is not detected on Virus Total by Clam AV as infected, that is a ClamWin problem--let us know about that. I am seeing a few FPs like that lately--which means that ClamWin needs to update to the latest Clam AV source code version to fix it. I have told the developers about these ClamWin only FPs.

Thanks for using ClamWin!

Regards,

Yes, I remember this situation several times. But I am pretty sure that this file has been posted to http://www.clamav.net/reports/fp
I am looking to clamav.net just before posting.
I did not know that you want to emphasize such event.

I have been finding lately some that some files are being detected by ClamWin with a false positive message to submit the file to Clam Av for signature correction. The problem is that Clam Av does not detect the file on Virus Total. The detection is probably due to ClamWin not being able to process a signature correctly because it does not have the latest Clam AV scan code that properly handles the signature. Here's hoping the ClamWin developers can/will give us a current version Windows port of ClamAV.

Thanks for using ClamWin!

Regards,

Thank you very much, MikTeX is clean: