Try to duplicate the threat prevention policy from the McAfee default (read only) policy. Set all the exclusion once again, save the policy, and assign it to a single machine. If that solves your issue, it means previous policy was corrupted, if not open a ticket with support as I have not seen any behavior like this before.
I created new policy from default but it didin't help.
This is strange thing because a while ago I created service request about this issue but the technician said don't use this settings, its working like desined. He didin't hear anything I was trying to tell him that we have been using this setting for years in virusscan enterprise 8 version.
I've been just waiting new versions to come out to see if problem is fixed but it is not. We have newest EPO 5.3.2 build 156 and newest endpoint 10.5. Exclusions probably work even if the list is multiplied but if you need to change something its frustrating every time to clear the list.
Anyone else using same setting, to confirm it should work?
1 of 1 people found this helpful
Great question anderen yes effected all Out customers....
10.5.2 Patch Comming Soon.
This we asumed only happens if Client Side exceptions are Not overwritten by Server policys.
We often had that Like this because we Password Project the Client GUI. This effected VSE 8.8 migrated Policy to 10.x.
Now today after struggling with the Problem again in 10.5.1 hf2 we noticed today that should be fixes in Community Up Release 10.5.2. Bug fixes Said exceptions after reboot are twice (Double).
So 10.5.2 Patch hopfully Solves this. we have Seen since 10.2 now.
Greetings from switzerland
20 mcafee customers had that effected too. All with german w7 64bit.