| Previous | Next |
| FWP_E_SESSION_ABORTED | FWP_E_TIMEOUT |
FWP_E_INCOMPATIBLE_TXN
FWP_E_INCOMPATIBLE_TXN means that the requested operation attempts to modify WFP policy while the session is in a read-only transaction. It is a mode mismatch, not a permissions diagnosis and not evidence that the filter engine rejected the filter definition itself.
Recognize the read-only scope
FwpmTransactionBegin0 can start a transaction with the FWPM_TXN_READ_ONLY flag. That scope is appropriate for a consistent inspection of policy but cannot add, delete, or update objects. Microsoft documents that adding filters fails with this status in a read-only transaction.
Fix the transaction design
- Keep read-only enumeration and validation separate from the write phase.
- Open a read/write transaction only when a configuration difference has been established and the caller has the required access rights.
- Commit or abort the old transaction before changing mode; do not try to nest a second transaction in the same session.
Microsoft: WFP error codes · Microsoft: transaction flags · Microsoft: FwpmFilterAdd0 read-only restriction
Looking for a different code? Search another status or error code.