| Previous | Next |
| STATUS_HOPLIMIT_EXCEEDED | STATUS_FASTPATH_REJECTED |
STATUS_PROTOCOL_NOT_SUPPORTED
The local machine does not have the requested protocol installed
These status values come from the Windows Filtering Platform path. For STATUS_PROTOCOL_NOT_SUPPORTED, wFP classifies traffic through layers, filters, provider contexts, sublayers, and callouts; IPsec policy is also configured through WFP at IKE/AuthIP-related layers.
This transport status means the requested protocol is unavailable on the local system. It is different from a remote protocol rejection or a blocked firewall rule.
For STATUS_PROTOCOL_NOT_SUPPORTED, 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
- Identify the protocol number or provider requested.
- Check installed network components and bindings.
- Separate missing local protocol support from network reachability.
References for STATUS_PROTOCOL_NOT_SUPPORTED
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Windows Filtering Platform
- Microsoft: TCP/IP settings and transport troubleshooting
Looking for a different code? Search another status or error code.