stapp 160 Posted June 20, 2017 Report Share Posted June 20, 2017 Windows 7 and Windows 10 using EAM. Why has this event id of a security audit failure mentioning a2hooks64.dll started showing under the Security section of the Event Viewer? I see there was a post about it in German section which Fabian answered but German is not my strongest subject Here are debug logs of the audit failure after boot on my Windows 10 64 bit machine just now, along with entry from event viewer. a2service_20170620144414(1336).zip Link to post Share on other sites
Frank H 109 Posted June 20, 2017 Report Share Posted June 20, 2017 Hi stapp, you promised me not to worry about such messages: cheers Link to post Share on other sites
stapp 160 Posted June 20, 2017 Author Report Share Posted June 20, 2017 But Frank I have slept hundreds of times since then Also this was after a Win 10 cold boot (fast boot disabled) with a day in-between when the machine had not been turned on. Link to post Share on other sites
Frank H 109 Posted June 20, 2017 Report Share Posted June 20, 2017 lol ! well, the message is the same and the cause too: Some processes Windows enforces specific digital signatures. One of them being everything related to DRM. like audiodg. When we try to load our DLL in there, we get this message. Link to post Share on other sites
stapp 160 Posted June 20, 2017 Author Report Share Posted June 20, 2017 Okay... I give in Link to post Share on other sites
JeremyNicoll 82 Posted June 20, 2017 Report Share Posted June 20, 2017 Frank, why does the event log message come and go? Is there a timing issue? - some aspect of the DLL being loaded that doesn't produce an event log record, that's changed so that now it does? Link to post Share on other sites
Frank H 109 Posted June 20, 2017 Report Share Posted June 20, 2017 hi, Like I said: it is an expected event , not related to timing and not an issue Quote Some processes Windows enforces specific digital signatures. One of them being everything related to DRM. like audiodg. When we try to load our DLL in there, we get this message. Link to post Share on other sites
JeremyNicoll 82 Posted June 20, 2017 Report Share Posted June 20, 2017 Maybe, but why does it sometimes not happen? Why has it started showing? Why has it not always shown? Link to post Share on other sites
Fabian Wosar 390 Posted June 22, 2017 Report Share Posted June 22, 2017 Different BB versions. The scope of which processes the BB monitors changes from release to release. Link to post Share on other sites
JeremyNicoll 82 Posted June 22, 2017 Report Share Posted June 22, 2017 Fabian, thank-you. Link to post Share on other sites
MTS 0 Posted June 27, 2017 Report Share Posted June 27, 2017 @stapp, Thank you for the link. I remember this happening quite a while ago and I made a post about it. It appears I should not be concerned. cheers! Link to post Share on other sites
Recommended Posts