itman 1,799 Posted December 15, 2017 Posted December 15, 2017 (edited) WD Exploit Guard is preventing an Eset .dll from loading. Appears they have the Code Integrity Guard set on internally in Edge. I haven't "played" yet with creating a rule for Edge and then disable CGI which really isn't advisable. Appears Eset will have to perhaps MS code sign their .dlls? Quote Log Name: Microsoft-Windows-Security-Mitigations/KernelMode Source: Microsoft-Windows-Security-Mitigations Date: 12/14/2017 3:19:21 PM Event ID: 12 Task Category: (6) Level: Warning Keywords: User: Computer: Description: Process '\Device\HarddiskVolume3\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe' (PID 4916) was blocked from loading the non-Microsoft-signed binary '\Program Files\ESET\ESET Security\eplgEdge.dll'. Edited December 15, 2017 by itman
ESET Moderators Peter Randziak 1,181 Posted December 18, 2017 ESET Moderators Posted December 18, 2017 Hello @itman , thank you for sharing, I will have that checked even I assume that the guys responsible are already aware of it. Regards, P.R. Tracking note: ESSW-3502
Recommended Posts