Hello Marzio,
I've actually run into the same issue using the EventLog consumer. As of right now I don't have a solution for it, as it would require a little investigative work into the Windows Event Log.
As a work-around, you could create a simple VBscript or PowerShell script and call them using the ActiveScriptEventConsumer or the CommandLineEventConsumer, respectively.
Hope this helps!
Cheers,
Trevor