| Previous | Next |
| STATUS_PIPE_DISCONNECTED | STATUS_PIPE_CONNECTED |
STATUS_PIPE_CLOSING
The pipe handle is already in closing state
These statuses belong to the Windows named-pipe path. For STATUS_PIPE_CLOSING, A named pipe can have multiple instances with the same name, but each instance has its own state, buffer, handles, type mode, read mode, and wait mode.
This status means the instance has started teardown. Later reads, writes, connects, or mode changes should not be treated as new protocol failures because the handle lifetime is ending.
For STATUS_PIPE_CLOSING, for diagnostics, record the pipe name, server/client end, instance count, blocking versus nonblocking mode, byte versus message mode, overlapped operation state, and whether the handle is connected, listening, closing, or disconnected.
What to inspect
- Check for concurrent CloseHandle, DisconnectNamedPipe, or cancellation.
- Stop scheduling new I/O after closing begins.
- Treat repeated failures as cleanup fallout if teardown is already in progress.
References for STATUS_PIPE_CLOSING
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Named Pipes
- Microsoft: Named Pipe Type, Read, and Wait Modes
- Microsoft: Named Pipe Operations
Looking for a different code? Search another status or error code.