| Previous | Next |
| STATUS_PROTOCOL_NOT_SUPPORTED | STATUS_LOST_WRITEBEHIND_DATA_NETWORK_DISCONNECTED |
STATUS_FASTPATH_REJECTED
The optimized network path declined the operation or packet
Windows networking can use fast paths that bypass slower general processing when state and policy allow it. This status means the requested data or operation did not qualify for that optimized path. The public NTSTATUS contract does not identify which fast-path implementation rejected it.
A caller should preserve the layer, direction, offload state, compartment, and packet metadata. Some implementations can fall back safely to the normal path; others surface the rejection because the caller requested fast-path-only behavior. Do not assume packet corruption without evidence from the owning component.
What to inspect
- Identify the API, driver, or protocol layer that requested the fast path.
- Record offload, interface, compartment, and policy metadata.
- Check whether a documented slow-path fallback is required and supported.
References
- Microsoft: FWPS_INCOMING_METADATA_VALUES0
- Microsoft: FwpsInjectForwardAsync0
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.