I regret to have to report that still, in March '18, Controlled Folder Access is behaving badly.
I've just tried to update MBAM from 333 to 344 and I received a CFA warning that some program in a tmp [sic] folder had been 'prevented from making changes'.
As soon as you touch the warning in the Action Centre, it disappears, bringing up the CFA 'Allow an app through..' dialog box with no further information. The AC warning is so abbreviated that you have to infer what's being meant, but that's not always easy.
I therefore don't know if all of the MBAM update has been installed, or how successful it was; it appears to be, but I can't tell.
I do like to have both CFA's and MBAM's oversight, in this context. CFA is more obvious: its fences are quite visible; I know what it's doing. MBAM... it's silent, but probably doing the right thing... speaking softly, but carrying a big stick, I suppose.
Turning off CFA every time you update a program is highly impractical. Is there anything MBAM can do not to raise CFA's ire during an update?
