By logs my guess are that MCS has attempt to set and pack the malicious files in his Quarantine but avast! has block that operation. avast! has the routine to scan all new detected USB devices. Conflict may arises when AV (in this case avast!) wants to be the first in scanning, thereby not allowing access to the disk. MCShield attempts to access to disk as well to preform scanning and glitch occurs.
MCS detect and send malicious files in quarantine. After that Avast detect that "new" files in quarantine and delite it or send it to ist quarantine.
Avast dont block any MCS operation.
Also Avast
dont scan new detected USB devices, thats why is needed this 2nd layer protection for USB devices. So there is no conflict between Avast and MCS.
I would recommend as solution to disable that routine to allow MCShield that part of job if you will. That should be the solution for your problem. Or . . set the MCS's Quarantine folder %path% as an exception in avast!. Quarantine is located in programdata folder.
%ProgramData%\MCShield\Quarantine
As solution i add exclusion in Avast (File System Shield) MCS Quarantine folder:
C:\ProgramData\MCShield\Quarantine\
selected R and W not X so if any file from quarantine folder try to execute it will be scanned by Avast.
Anyway, I will preform some additional testing and report to dr_Bora.
I try test myself with this settings but MCS cant detect EICAR test file so i have no idea how to test it, and will it work.
Thank you for your feedback.
No problem, im always here to help