DavidR
13
No excluding cmdagent.exe won’t make a blind bit of difference as it isn’t cmdagent.exe that is being detected as infected. It is the unencrypted signatures cmdagent.exe loads into memory and you are asking avast to scan that memory.
So you aren’t excluding its actions, just stopping avast scan that file.
By all means create a custom scan but don’t scan the memory or choose one of the lessor levels of memory scan, in the Memory section of the options, see image.