When I try to do a scan, it gives an error saying "Malformed directory", and doesn't scan. How do I fix it?

Which message do you get--malformed directory or malformed database. It's hard to tell because your message says one, and your subject says another. At any rate, if it's malformed database, you should delete the daily and main database in the ClamWin database directory. If you don't know where it is, check the File Locations tab in the ClamWin preferences. It's also possible you may have a 'home-made" signature database for some reason (maybe you make some of your own signatures). If so, it will probably be something like a filename.db file. Delete that also.

If you actually have a malformed directory, that's not ClamWin's fault. You will need to do something about that yourself.

Regards,

Just thought I'd post that I've also been getting this with a fresh install of 0.94.1. I've included a sample of the exact log report below.

Personally, I have tried deleting the database files and re-downloading/rebuilding as well as completely removing and reinstalling ClamWin. Everything appears to download and work fine until a scan is attempted. At which point, this error occurs. I'm beginning to think that there's (as of yet, unknown) malware on the system interfering with ClamWin.

So, you have a malformed database! You can tell the location of the database by right clicking on the ClamWin icon in your system tray. Select Configure ClamWin and then select the File Locations tab. The Virus Database folder will tell you the location of the signature database on your machine. In Windows XP it's usually under All Users in the Documents and Settings directory. Here is the location on my XP machine: C:\Documents and Settings\All Users\.clamwin\db . If you go there, you should have a main.cvd file (the main database), a daily cvd. file (the daily database that hasn't yet been integrated into main), and a mirrors.dat file.

To make a long story short, however, you should proabably just delete both cvd files and manually re-download the databases to get new/good ones. Some users also prepare a few of their own "unofficial" signatures. If you do this, you will also have other database files (such as somename.db or .mdb or .ndb or .hdb), and these could be corrupted. If this is the case with you, rather than attempting to correct them, (and before manually re-downloading), just delete the unofficial signatures. Your detection will probably not suffer very much.

Regards,

An update to my post... On a whim, I decided to uninstall SpyBot S&D and the TeaTimer resident. It may be a fluke, but ClamWin appears to be functioning correctly for the moment. Perhaps there is a conflict with SpyBot [shrugs]

If you re-read my post, you'll see that I did indeed do what you suggested. And I did it numerous times with variations of uninstalling ClamWin partially/completely.

This was a fresh install (first time ClamWin was on the box) and I just ran the installer and let it download the database when it was done.

I also just posted a follow up indicating that uninstalling SpyBot S&D seems to have resolved the issue, indicating that there's potentially a conflict of some kind that's occurring between these two applications under certain circumstances.

And, in case it wasn't obvious, please note that I am not the original author of the thread, but another person who was experiencing the same issue

If Spybot S&D still uses that TeaTimer real-time module, that was probably doing something to the ClamWin updates.

Regards,