| Previous | Next |
| STATUS_FWP_FILTER_NOT_FOUND | STATUS_FWP_PROVIDER_NOT_FOUND |
STATUS_FWP_LAYER_NOT_FOUND
The requested packet-processing point is not available
STATUS_FWP_LAYER_NOT_FOUND means the requested WFP filtering layer does not exist in the filter engine. A layer represents a defined point in network processing at which filtering can occur. It is not a generic network-interface name, and it is not a sublayer that orders rules within one layer.
A layer lookup commonly fails because a GUID is wrong, a version-specific layer was assumed, or code requested a layer that is not available on the target platform. The correction is to verify the documented layer identifier and the intended processing stage. Moving a rule to a nearby layer changes what fields are available and can change its security meaning.
What to verify
- Confirm the exact layer GUID and whether it is IPv4, IPv6, user-mode, or kernel-mode.
- Verify OS support and SDK/WDK version assumptions.
- Check that the chosen layer exposes the fields used by the filter conditions.
- Do not replace a missing layer with an arbitrary layer without reviewing policy semantics.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Windows Filtering Platform object model
- Microsoft: WFP filtering layer identifiers
- Microsoft: WFP operation
Looking for a different code? Search another status or error code.