Hi @박 내석 ,
I could not find any Microsoft documentation that guarantees an ordering between the classic kernel Process End timestamp and the instant the process object becomes signaled. Without that contract, there is no documented "no later than" or "strictly before" relationship for this event, and no documented set of OS builds or termination paths where either would apply. Everything below refers to documented behavior only; I am not offering an explanation of any particular implementation.
The pages you consulted describe each side separately but do not connect them. The ExitProcess remarks list the effects of exiting a process, ending with the termination status changing from STILL_ACTIVE and the process object becoming signaled, but the Process End event is not part of that list. That page also notes that returning from the main function results in a call to ExitProcess, without stating whether this covers the managed Main return path you exercised. The general Terminating a Process page has the same gap for other termination paths. On the event side, Process_TypeGroup1 defines the End event and its payload, and the parent Process class page declares EventVersion(3) with only Process_V0, Process_V1 and Process_V2 as older layouts, so the version 4 End event in your trace has no separate published definition.
On the equal versus strict distinction, a documented limit also applies at the measurement level. With ClientContext set to 1, WNODE_HEADER states that the time stamp stored in each event is equivalent to the value returned by QueryPerformanceCounter, so the event timestamp and your parent's readings share one clock. The QPC guidance you cited treats values taken on different threads that differ by ±1 tick as having an ambiguous ordering, which is 100 ns at your 10 MHz frequency. Since the event is logged by the kernel rather than by your wait thread, your readings cannot separate "equal" from "strictly before" within that window, regardless of any ordering contract.
As for missing metadata, the documentation defines no applicability criteria for this relationship, so no additional metadata would make a documented guarantee apply. If you pursue an implementation-specific answer, the items you already noted as not captured (the guest UBR, the full kernel patch version, the kernel file hash and a native termination call stack) would be needed to identify the exact build and termination path being described.
The relationship you observed on 10.0.26100 with managed Main return therefore remains indeterminate as a contract, and does not extend to ExitProcess, TerminateProcess or abnormal termination. If you need a formal statement from the Windows team, that would have to come through a Microsoft support channel, as this forum cannot provide one.
I hope this helps clarify what the available documentation establishes and where further confirmation is needed. If you find this explanation helpful, you’re welcome to follow this guidance so others with the same question find the relevant information.
Thank you.