CONTROLLED FOLDER ACCESS BLOCKS EVERYTHING!

In general there's no good reason to ever allow something CFA has blocked access, that is unless it's either causing an obvious problem with the operation of an app (e.g. error message or program failure) or more likely, the blocking action by CFA continues repeatedly and won't stop until the action is allowed.

The reason for this is that CFA entries are telling you about something that's already been blocked, so allowing won't do any good unless the operation is attempted again.

Looking at the CFA log entries you've listed, most likely occurred during either a Windows or application update process, which are the most common items CFA blocks and also why they often won't occur again, at least until the next update cycle tries the same action if the developer involved hasn't "fixed" their usually improper access to a protected folder.

CFA is badly understood, since it's really nothing more than a "dumb" blocker, stopping anything trying to write to critical folders that should never be written to under most circumstances. The reason for this is that most of these folders have ended up being abused by ransomware or other malware, since they are writable by default, but Microsoft has been trying to get developers to stop using them for years so they can simply block the ability for anything to write to them other than by the operating system itself.

I've never allowed any of the CFA warnings I've gotten and never had a true problem as a result.

Rob