| Previous | Next |
| STATUS_FWP_PROVIDER_CONTEXT_NOT_FOUND | STATUS_FWP_NOT_FOUND |
STATUS_FWP_SUBLAYER_NOT_FOUND
The policy-ordering container is missing
STATUS_FWP_SUBLAYER_NOT_FOUND means that the requested WFP sublayer does not exist. A sublayer is an ordering and policy container within a WFP layer; it is not itself the layer where packets are classified, and it is not equivalent to a filter rule.
This matters because filters are installed into sublayers and their effective precedence depends on that structure. A missing sublayer can therefore prevent policy installation even if the target layer is valid. Check the sublayer GUID, provider ownership, weight, and installation order rather than moving filters into a default sublayer without reviewing conflict and precedence behavior.
What to verify
- Confirm the target layer and the intended sublayer GUID separately.
- Check whether the sublayer is built in, persistent, or dynamically created by a service.
- Review provider ownership and effective sublayer/filter weights.
- Avoid using a default sublayer as a blind replacement for a missing custom one.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Windows Filtering Platform object model
- Microsoft: WFP sublayer identifiers
- Microsoft: FWPM_FILTER0 structure
Looking for a different code? Search another status or error code.