| Previous | Next |
| STATUS_FLT_CONTEXT_ALREADY_LINKED | STATUS_FLT_REGISTRATION_BUSY |
STATUS_FLT_NO_WAITER_FOR_REPLY
STATUS_FLT_NO_WAITER_FOR_REPLY is a communication-port protocol result. A user-mode service attempted to send a reply, but no kernel-mode minifilter wait remained for that reply. The usual causes are a stale message identity, a timeout, cancellation, disconnect, or a race during filter unload.
Correlate every request and reply with the communication-port message identifier and define what the service should do when a reply is no longer wanted. A successful connection does not guarantee that a particular kernel wait remains alive; FltSendMessage has explicit timeout and disconnect outcomes.
Diagnostic data to retain
- Message ID, client-port generation, send time, reply time, and timeout configuration.
- Service restart and port-disconnect events.
- Whether the minifilter requested a reply buffer or only one-way delivery.
Communication between user mode and minifilters | FltSendMessage | NTSTATUS reference
Looking for a different code? Search another status or error code.