I didn’t say that, I said it is totally unrelated to your other avast detections on unencrypted signatures found in memory. If it were, then I guess your system would have had this problem from 9 June.

Well the last file displayed in the UI isn’t necessarily the file that is actually being scanned, but the last file which has been scanned and the path written to the UI.

Whilst that may well be correct, explorer.lnk is hardly a rogue and again that has nothing to do with either comodo defence+, cmdagent.exe or avast ???

Guess what, there are hundreds of of applications, processes that run under explorer.exe.

Sorry but I’m not seeing a pattern at all, if you didn’t install the Comodo AV then there shouldn’t be any co-resident/conflict problems as it would be the defence+ element that is loading those signatures into memory.

If it truly were an issue of co-resident/conflict problems between comodo defence+ and avast then these forums would be alight as the comodo firewall with defence + must be one of the most commonly used firewalls.

Sorry but this is something else, as painful as this current issue is it’s unrelated to your previous issue 3 weeks ago.