For every process where Eset's AMSI .dll is being injected into, Windows Defender's amsi.dll is also being injected as shown in the below Process Explorer screen shot. This in spite of the fact that WD is disabled and its engine process isn't even loaded. Suspect this might also be related to the Authenticode issue.