| Previous | Next |
| STATUS_FWP_IKEEXT_NOT_RUNNING | STATUS_FWP_INJECT_HANDLE_CLOSING |
STATUS_FWP_TCPIP_NOT_READY
WFP cannot complete the request before TCP/IP is initialized
These status values come from the Windows Filtering Platform path. For STATUS_FWP_TCPIP_NOT_READY, wFP classifies traffic through layers, filters, provider contexts, sublayers, and callouts; IPsec policy is also configured through WFP at IKE/AuthIP-related layers.
Some WFP operations depend on the TCP/IP stack. This status is usually timing-related during boot, resume, adapter arrival, or early service startup.
For STATUS_FWP_TCPIP_NOT_READY, for diagnostics, keep the failing API call, layer or sublayer key, provider context type, filter condition set, callout id, engine state, and whether the Base Filtering Engine, IKEEXT, TCP/IP stack, or L2 path was ready.
What to inspect
- Retry after TCP/IP initialization and adapter binding.
- Avoid installing filters against transport layers too early in boot.
- Correlate with network stack initialization and interface arrival events.
References for STATUS_FWP_TCPIP_NOT_READY
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: WFP error codes
- Microsoft: Windows Filtering Platform
- Microsoft: TCP/IP settings and transport troubleshooting
Looking for a different code? Search another status or error code.