Today When I start clamwin I have started getting this error.
Bizzarely if I start clamwin as soon as I reboot and login then it will run without error and I can start a scan, but then after a minute or so once all the programs and services have finished loading I presume, the error occurs..

Hello,

Should be a problem related to a Runtime library. You may download the missing .dll from https://www.dll-files.com/dllindex/dll-files.shtml?msvcp60 (I already used this service for other .dlls that were missing when using an audio player, so I find it reliable). Then unzip it to System32 folder; this should fix the problem.

Hope this helps,
Antonio

The .dll isn't actually missing though, it is right there in c:/windows/system32 folder

Which should be the one that clamwin is using presumably as it is a 32bit application

what os?

I am usinf windows 2008 server

anyone else got any suggestions ? I can't find any other AV software that works on windows 2008 unles sI buy an expensive fileserver license.

"
clamscan.exe - Unable To Locate Component
This application has failed to start because MSVCP60.DLL was not found. Re-installing the application may fix this problem.
"

The DLL does exist on my system (C:\WINDOWS\system32\msvcp60.dll) and re-installing ClamWin has not helped.

I am running ClamWin 0.96.5 on Windows XP Pro 64-Bit (SP2). I think the error started appearing with ClamWin version 0.96.4, but it might have been a release or two before that.

Any ideas?

Did you try the site Antonio mentioned in a post above where you can download the dll?

Another option: see if you can boot up your Windows CD and repair instead of reinstalling Windows.

Regards,

The DLL provided by Antonio's link is an older version (6.00.8168.0) than what I already have (7.0.3790.1830). I suspect that this is not an issue with a missing or corrupt DLL, but rather an incompatibility between the latest versions/updates of ClamWin and WinXP Pro 64-bit (which I've heard is more like Windows Server 2003 than standard XP, if that matters).

I might try an OS repair at some point, but for now I'll live with the error as it doesn't seem to be 'fatal'.

Thanks!