Is it possible to exclude the contents of a folder from real-time scanning, but not scheduled scans?

[plarue 0]

Is it possible to exclude the contents of a folder from real-time scanning, but not scheduled scans? I see that this can be accomplished with individual files, using Process Exclusions. Is there a way to do the same thing for a specific directory?

[itman 1,755]

Yes, by path exclusion; e.g. C:\Some directory name\*.*

[plarue 0]

Thanks for the quick response. When I try to add an exclusion path like the example you gave it indicates an invalid path.  I'm doing this in "Process Exclusions". The documentation suggests that this is really designed for backup processes and that a specific process has to be chosen. Where you referring to the Performance or Detection exclusions? I know a folder's contents can be excluded there, but I thought both of them would also exclude from the scheduled scans.

[Marcos 5,288]

You can set up the scheduled scan to ignore exclusions.

[plarue 0]

21 minutes ago, Marcos said:

You can set up the scheduled scan to ignore exclusions.

My scheduled scan is currently not set to "Ignore exclusions". However, If I select this box, it's an all or nothing option. I have a lot of other exclusions that I'm good with not scanning and would probably create issues if they were scanned. I just need to ignore this new one.

Perhaps the answer is to create a new scan, checkmark the "ignore exclusions" box, turn off "Scan all targets" and give this new scan a target of the specific folder that I have in mind?

[itman 1,755]

2 hours ago, plarue said:

When I try to add an exclusion path like the example you gave it indicates an invalid path.  I'm doing this in "Process Exclusions".

Works fine on EIS. For Detection exclusions, mouse click on the gear symbol next to Real-time file system protection. Then select "Edit Exclusions."

Edited September 20, 2021 by itman

[conorc 1]

sorry to hijack the topic but I assume it is not possible exclude folders within user directory pathways?

for example, we want to exclude Onedrive but each users Onedrive is in a different pathway based on their username e.g.  /Users/jim/OneDrive

 

[Marcos 5,288]

Wildcards are supported only at the end of the path in performance exclusions. You can exclude /Users/*/OneDrive but we do not guarantee that it will always work.

By contrast, detection exclusions support wildcards anywhere in the path.