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.

References

• Microsoft: System error codes 0–499