Why is the (smart) exclusion not working?

[CP-Shark]

Hey guys,

we recently upgraded several servers to E89.25 and have noticed that certain Smart Exclusions are no longer working as expected.

While reviewing the TE.log collected via CPInfo, I found indications that the exclusions are not being applied correctly.

The screenshot below shows how the exclusion was configured. Based on the information provided in sk181679 - Smart Exclusions - Syntax and Supported Capabilities for Exclusion Types, this exclusion should also be valid for Forensics and therefore should prevent the related processing.

Has anyone seen similar behavior after upgrading to E89.25, or does anyone have an idea what might be causing this?
And please not again the answer that this is a case for a TAC ... 

Cheers,
Oliver

[lluner]

@CP-Shark 

From what I can see in the images, Blade Forensics is showing an alert. Could you check what is happening?

[CP-Shark]

@lluner thanks for the reply. This is just a hint we find in every exclusion:

[lluner]

@CP-Shark 

Put it in this field.

Process name 

manager.exe

Process path

**\manager.exe

Keep only the forensics blade. I believe each blade has a different configuration and support.

[CP-Shark]

I guess this could be an idea, but not the solution. And you mean EFR-M and not EFR-AR?
In an older version we had no issues and we cannot separate all exclusions.
We´ve opened a ticket via our SP.