| Previous | Next |
| STATUS_FWP_INVALID_PARAMETER | STATUS_FWP_CALLOUT_NOTIFICATION_FAILED |
STATUS_FWP_TOO_MANY_SUBLAYERS
The filtering engine cannot allocate another sublayer
These status values come from the Windows Filtering Platform path. For STATUS_FWP_TOO_MANY_SUBLAYERS, wFP classifies traffic through layers, filters, provider contexts, sublayers, and callouts; IPsec policy is also configured through WFP at IKE/AuthIP-related layers.
Sublayers group filters and define relative ordering. This status points to policy-object exhaustion or a leaking policy manager that creates sublayers instead of reusing stable ones.
For STATUS_FWP_TOO_MANY_SUBLAYERS, 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
- Enumerate sublayers by provider.
- Delete stale policy objects left by old versions of the product.
- Reuse a fixed provider and sublayer design instead of creating per-connection sublayers.
References for STATUS_FWP_TOO_MANY_SUBLAYERS
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Windows Filtering Platform
- Microsoft: WFP error codes
Looking for a different code? Search another status or error code.