| Previous | Next |
| ERROR_RECEIVE_PARTIAL_EXPEDITED | ERROR_EVENT_PENDING |
ERROR_EVENT_DONE
What ERROR_EVENT_DONE means
A Transport Driver Interface event indication completed synchronously. In practical terms, this status belongs to legacy TDI event completion: the event callback finished without entering a pending asynchronous state.
Typical causes
- The client handled the indication immediately
- No additional completion callback is required
- A legacy network component returned a synchronous completion status
How to investigate
- Verify that resources are released exactly once
- Do not schedule a second completion path for a synchronous result
- Compare code paths for done versus pending indications
Developer guidance
This is a completion-state value used by legacy networking code. The main implementation risk is double completion when synchronous and asynchronous paths are not separated.
Operational interpretation
When ERROR_EVENT_DONE appears, first determine whether the operation actually failed, completed with an informational condition, or transferred work to another component. Record the API name, returned value, affected process or object, and the immediately preceding event. For this code, the most useful boundary is the legacy TDI event completion boundary; broad machine-wide remediation before that boundary is identified can hide the original evidence.
Example scenario
An incident begins when the client handled the indication immediately. A responder investigating this result should not begin with a generic reboot that destroys the original context. A better first step is to verify that resources are released exactly once. That evidence connects it to its producing operation and reveals whether this particular result is repeatable, expected, or merely secondary.
Logging and telemetry
Telemetry for this Win32 error should preserve its numeric value, component version, process and thread identifiers, operation name, affected object or endpoint, elapsed time, and the first earlier failure in the same activity. Keep the result correlation identifier stable across callbacks so the status can be joined to the request that initiated this exact operation.
Recovery and validation
Apply recovery only after the responsible state has demonstrably changed. After changing that state, repeat one controlled this result scenario and verify both the returned status and the resulting system state. Absence of another log line is not sufficient: confirm that the intended legacy TDI event completion action completed, that no resource remains pending, and that later cleanup does not produce a different secondary error.
Escalation notes
Escalate this result with a minimal reproduction, the exact binary architecture, operating-system build, and a timestamped trace covering initialization through cleanup. Include whether the result changes after the affected object is recreated. These details allow the owner of the legacy TDI event completion component to distinguish a contract violation from environmental state.
References
Looking for a different code? Search another status or error code.