| Previous | Next |
| STATUS_FWP_DUPLICATE_KEYMOD | STATUS_FWP_ACTION_INCOMPATIBLE_WITH_SUBLAYER |
STATUS_FWP_ACTION_INCOMPATIBLE_WITH_LAYER
The action is recognized, but the packet-processing point does not allow it
STATUS_FWP_ACTION_INCOMPATIBLE_WITH_LAYER differs from an invalid action type. The action is a known WFP action, but the selected layer does not support it. Layers represent distinct packet-processing stages and expose different fields and enforcement semantics, so moving a rule to a nearby layer is a policy change, not a neutral workaround.
Compare the layer GUID, action type, and callout requirements as one tuple. The correction may be a different layer selected by the policy design, or a different action that is valid at the current stage. Do not derive the choice only from similar layer names or IPv4 versus IPv6 suffixes.
What to inspect
- The exact layer GUID and its processing role.
- The
FWP_ACTION_TYPE, plus callout key or filter type where applicable. - Fields referenced by conditions and whether they exist at the replacement layer.
- The enforcement meaning before and after any proposed layer change.
References
- Microsoft: WFP error codes
- Microsoft: filtering layer identifiers
- Microsoft: FWPM_ACTION0
- Microsoft: FwpmFilterAdd0
Looking for a different code? Search another status or error code.