This issue will be fixed on the next DSA release. In the mean time, there are two workarounds to resolve this issue.
- Workaround 1: Behavior Monitoring protection exceptions use " * + lowercase "
- Ensure the full path of your target process is lower case. As an example, C:\adc\adc1.exe
- Navigate to Anti-Malware > Advanced > Behavior Monitoring Protection Exceptions, then add target path to list. As an example, *:\adc\adc1.exe
Because some characters of target path cannot be changed to lower case, use wildcard (*) to replace it. As an example, C:\adc\adc1.exe should be *:\adc\adc1.exe
Example 1: Original real target path: C:\adc\adc1.exe Correct target path pattern: *:\adc\adc1.exe Example 2: Original real target path: C:\adc\AdC\Adc1.exe Incorrect target path pattern: *:\adc\adc\adc1.exe Correct target path pattern: *:\adc\*d*\*dc1.exe Correct target path pattern: *:\adc\* \*dc1.exe Correct target path pattern: *:\adc\*
- Ensure the full path of your target process is lower case. As an example, C:\adc\adc1.exe
- Workaround 2: Process Exception
It is not case sensitive when process exception compares to path.- Navigate to Anti-Malware > General > Real-Time Scan then edit Malware Scan Configuration.
- Go to Exclusions > Scan Exclusions then enable Process Image File List. Click Edit.
- Go to General > Files then add the target path to the top of the list. E.g. C:\ADC\ADC1.exe
- Navigate to Anti-Malware > General > Real-Time Scan then edit Malware Scan Configuration.