A little puzzled with the request, could you elaborate on the initial issue?
I would assume your are referring to DriveHookExclusions?

In my last 10+ environments and have had no need for exclusions for msedgewebviewruntime so could be related to something else, conflicts of 3rd party security software, miss match of token integrity issues policy etc.

I would raise a ticket with BT.

Hi ​@Jens Hansen Thank you for your reply. Yes it is driver hook exclusion. We have seen few Windows executable (ai.exe and msedgewebviewruntime) showing Windows  pop-ups that mention pghook.dll could not be verified. To resolve the issue immediately Support suggested to add the driver hook exclusions. Managed Hook exclusions didn’t resolve it. Tried different EPM W agents too. In crash dumps it shows pghook.dll as faulting module.  I see on other security vendor blogs (not in our environment) have faced the same issue for msedgewebview2 and suggested exclusions in respective tools.

Later we have seen it for msedge.exe as well. No pop-up but app crash.
Also zoom.exe started crashing too and the dumps indicate pghook.dll is causing it. After adding the driver hook exclusion in EPM the issue is gone.


My other posts for more details 

could you provide more details on “miss match of token integrity issues policy” . As you suggested, I will recreate issue/test by removing other security tools just in case to see if it is interaction issue. We do have exclusions for security tools in EPM as well as in those tools for EPM. (One of the tools has folder paths that change every update )

Thank you for your time