@ Libra
OK, that scan All files option is I believe overkill as you are going to be scanning files that aren't at risk of infection, etc. The default settings are going scan any file considered at risk, plus it also depends on the term opening, it is possible to open some files without running/executing them. That is covered by default in the Scan when executing tab, if a file is to be executed it will first be scanned and why there is no such scan all files option.
To me the same is true of scan when writing as these would mostly be data files capable of being written to. Executable files if they were written to it is most likely as a result of a true virus infection/injection and these files would be scanned under the when files are created or modified the FSS.
I have left these scan all files at the default as I don't believe avast would have that as the default setting if it were dangerous to do so.
The web shield default is to scan all files, so that it can attempt to detect malware and abort the connection, stopping it from being saved on the system.
I don't know why MBAM detected this as other than the log data there is no way to analyse the file, it could well be that it wasn't detected by avast as no AV will give 100% protection. That is true of MBAM also but it compliments avast and I run a weekly update and scan though it has never found anything (though I don't really expect it to) other than a couple of FPs, which is true of all security applications, none are FP free or will give 100% detection.
