We found out that for eventid:[3, 11, 12, 13] on several deployments of Sysmon, we have processGUID set to 0 and as a coherent result,`image: unknown process`.
This is not always reproducible and looks to be linked with timing. We found some posts related to the same behavior but for ParentProcess, not the process itself, where parent was stopped and pid reassigned to another process. Could this be the same here?
Is this a known issue? We were able to reproduce it with short-lived processed performing network communication for example (but not in a stable manner either).
We have this behavior for several versions of Sysmon, including the latest available to download.
Best regards