OK. This is starting to make some sense.

Avast’s 6 quick scan doesn’t include the memory scan. Neither does the default full system scan. Both of these I have run previously with no Comodo issues.

I didn’t like the default system scan since it was scanning all three of my HDDs. One contains XP and the other just backup image files. I am running Avast 6 on my WIN 7 x64 OS. So I created my own custom system scan. It scans for rootkits, system drive, and memory. I think this was the first time it ran.

So is the solution here just to exclude cmdagent.exe from being scanned in my custom scan that does memory scanning? So far this appears to be the only conflict I have encountered with Comodo files or processes.

What is interesting though is cmdagent.exe did not block avast from scanning it like it does everything else. That tells me Avast has some very heavy methods to scan for memory threats. Impressive!