ClamAV: clamscan seems to stall on scanning mounted Windows partition
 

While using Linux live-CD's to repair infected Windows system, clamscan seems to stall. At least, the LED's I would expect to be on during this operation, the 'hard drive activity' and 'CD activity', go off, both drives stop making noise. Checking "htop", clamscan is listed, but isn't...moving resource-wise. Also in "htop": Memory usage stays constant and low, but CPU usage is all the way at 100% and not moving. I can use other consoles and run other programs without issue, but clamscan just seems to start off well, then hit a point and stall.

I've heard that ClamAV is slow on scanning, but should it really be taking 2 hours on an .exe of 2MBs? And without showing sign of its effort in the process list?

I think at this time the verdict would be "inconclusive" due to lack of information. It really could be anything ranging from the inability to unpack or scan PXE-compressed PE executables to who knows what . (Different app but for instance a certain GNU/Linux version of Bitdefender stalled on sockets.) Best way forward IMHO would be to monitor the log and make clamscan run in verbose/debug mode to pick up any errors and at the same time monitor progress using 'lsof' on clamscan's PID: one of the file descriptors should show which file it's got open and stalls on. That should get you more info.