Thank you for your quick response. The removal/clean/re-install seems to have it working now. Sorry, I didn't know about the FAQs, this the first time I've had any cause to use the Forum. May I suggest that a try{ ... } catch( ... } block with some watchdog counter might be a better way to deal with such a file information error? Spamming syslog is one of those bugs that can seriously impact a system's performance and can very time-consuming for a field tech to track down. Anyway, so far so good. Again, thanks for your response and thanks to all of you for a wonderful piece of antimalware. Guy