What does Windows error code 128 (ERROR_WAIT_NO_CHILDREN) mean?

ERROR_WAIT_NO_CHILDREN

What ERROR_WAIT_NO_CHILDREN means

A wait-for-child operation was issued when the caller has no child processes eligible for that wait. The result means the wait request has no valid target. The child may never have been created, may already have been reaped, or may not belong to the calling process under the relevant compatibility rules.

Common causes

• The parent waits twice for the same child
• Process creation failed but the code still enters the wait path
• Another thread already consumed the child termination event
• The supplied relationship or process group is incorrect

How to investigate

1. Record child creation success and the returned process identifier
2. Track which thread owns the wait and reap operation
3. Ensure only one component consumes termination status
4. Inspect races between timeout, cancellation, and normal completion

Developer guidance

Model child ownership explicitly. Transfer the process handle or identifier to exactly one reaper and invalidate it after the termination result is consumed.

Administrator and support guidance

The code usually indicates application bookkeeping rather than a missing operating-system service. Gather the parent/child event timeline.

How this code differs from related results

ERROR_CHILD_NOT_COMPLETE means an eligible child exists but has not finished; this code means there is no eligible child to wait for.

Evidence worth collecting

For ERROR_WAIT_NO_CHILDREN, begin the trace at the operation where the parent waits twice for the same child. For ERROR_WAIT_NO_CHILDREN, preserve the exact API boundary, numeric result, process and thread identifiers, relevant object state, and the component version. The first verification point should be to record child creation success and the returned process identifier. This evidence distinguishes the specific ERROR_WAIT_NO_CHILDREN contract from a later secondary failure.

Recovery and verification

Recovery for ERROR_WAIT_NO_CHILDREN should address the observed condition rather than merely retrying the same call. After the change, reproduce the scenario in which the parent waits twice for the same child, then confirm that the intended operation completes and that cleanup returns all associated resources. For ERROR_WAIT_NO_CHILDREN, also verify that the next repeated operation follows the same successful path without increasing the resource class implicated by this result.

When to escalate

Escalate ERROR_WAIT_NO_CHILDREN with a minimal reproduction focused on the failing process-control boundary. Include the operating-system build, binary architecture, runtime or compatibility-layer version, the exact input values, and a timestamped trace showing the parent waits twice for the same child. For the ERROR_WAIT_NO_CHILDREN escalation record, note whether changing concurrency, object lifetime, target process, module set, or endpoint location alters the result.

References

• Microsoft: System error codes 0–499

Looking for a different code? Search another status or error code.