Dear reader,

ever since I've installed version 0.90.1-3 of ClamAV on our mailsystem, I can't get clamDscan to work anymore. In the hope to solve the issue, I installed version 0.90.2-2 (downloaded from https://www.sosdg.org/clamav-win32), but this also doesn't help. Before I installed the first mentioned version, everything was o.k. The latest installed version that worked fine was 0.88.6-1, but I had to upgrade because Freshclam told me to do so.

The problem is that if I run clamDscan (while clamD is running of course), I get a message saying "lstat() failed. ERROR". The funny thing is that when I start clamD in DEBUG mode ("clamd --debug"), AND I run clamDscan.exe from the bin directory (current dir is c:\clamav-devel\bin), that it works perfectly then. But then when I run clamDscan from another directory (let's say c:\clamav-devel, by typing the command "bin\clamdscan.exe test\clam-error.rar", also while ClamD is running in debug mode) that I get the same error again. Again: if I run clamD in normal (non-debug) mode and run clamDscan from the bin directory, it doesn't work (while it works when running clamD in debug mode).

Does anyone have a clue what might be the problem? Maybe the problem is caused by OS updates instead of the new versions of ClamAV, I don't know.

System information:
- Microsoft Windows Server 2003, Standard Edition, Service Pack 1
- All recent OS updates installed
- ClamAV Win32 version: 0.90.2-2
- ClamAV directory: c:\clamav-devel

Thanks in advance for your suggestions!

Best regards,

Peter van der Meer
The Netherlands

ClamWin isn't associated with the SODG version of ClamAV for Windows. ClamWin also isn't involved with supporting ClamAV. You should vist the ClamAV Web site and the SODG page there for information about how to get support.

ClamWin has ported the "engine" that is in ClamAV over to Windows with its own GUI. The most current version of ClamWin is version 0.90.1.1. You can get support for it in these forums here.

Regards,