In your FAQ you say:



What is the status of the "on-access scanning component" and do you need any help with it?

it's in private alpha-testing. We do need help with programming in C++, what could you offer?

I've done a moderate amount of C++ work on windows in tha past. A good mix of services, ActiveX/COM controls, and GUI. Currently, most of my "work" is in C#. What do you need done?

looks like it's been 7 years since the last post in this topic... any news on when ClamWin will be recognized by Windows 7? How about Windows 8 now?

Thanks for keeping this alive!

Antivirus integration with the Windows security center is costly and probably beyond the ability/budget of free AV programs--excluding the free versions of commercial AV programs. I don't remember what all is required for integration, but I do recall that the AV needs to have a resident scanner, which ClamWin does not have. The AV also needs to be certified by one of the recognized testing companies, which have minimum standards for detection, useability, cleaning/restoring, and false positives. I'm really kind of surprised that Immunet (the commercial AV now owned by Clam AV's Sourcefire parent) is integrated. However, it uses some scanning code licensed from Bit Defender, which I guess lets it meet the testing requirements. Malwarebytes' Antimalware program is not yet integrated, so you can have a good AV that is not.

Regards,

OK good to know. Thanks for the reply!
I also found Clam Sentinel. It also doesn't integrate with Windows, but it does provide realtime protection.
I also started using Kaspersky. I got it for free when I bought my Windows 8 laptop. It doesn't work with Windows 8 *big surprise), but it works very well with Windows 7. It also came with 2 years of virus updates. It already found some issues on my computer that ClamWin didn't. And ClamWin constantly finds false positives, but seems to miss the real issues.

Are those false detections from ClamWin or from Clam Sentinel? ClamWin's signatures detect "infected files," and Clam Sentinel's heuristics detects "suspicious files."

ClamWin uses the scan engine and virus database provided by the Clam AV project. Clam now prepares most of their signatures automatically. The way they do it seems to result in more false positives on Windows system files. ClamWin protects against this by not allowing the quarantine of files that are digitally signed by Microsoft. You should report all false detections to the Clam AV people, however.

Virus writers often do not follow good programming practices or properly document their files to the Windows operating system. Clam Sentinel detects these files as "suspicious." Always verify files that are quarantined as "suspicious" with another AV or with Jotti/Virus Total online. If they are false detections, whitelist them in Clam Sentinel.

To prevent conflicts and save system resources, if you use another AV with ClamWin/Clam Sentinel, exclude the ClamWin data folder (which has the signatures and quarantine files) from the other AV scans. Also exclude the other AV program folder and signature/quarantine folders from Clam Sentinel scans. ClamWin isn't real-time by itself, so you probably don't have to exclude anything from it.

Regards,