| Previous | Next |
| STATUS_FWP_NO_TXN_IN_PROGRESS | STATUS_FWP_TXN_ABORTED |
STATUS_FWP_TXN_IN_PROGRESS
The call belongs outside the explicit policy transaction
STATUS_FWP_TXN_IN_PROGRESS is the inverse of STATUS_FWP_NO_TXN_IN_PROGRESS: the operation must not be executed while the session has an explicit transaction open. It does not mean that transactions are generally broken.
Identify the failing API before changing transaction scope. For example, FwpmEngineSetOption0 changes engine settings and is documented to reject calls inside a transaction. Complete or abort the policy transaction first, then make the engine-setting change as a separate, traceable operation.
Diagnostic sequence
- Log the API name, engine handle, transaction mode, and caller stack.
- Find the matching
FwpmTransactionBegin0and determine why it remains open. - Commit or abort only after evaluating the already queued policy changes.
- Run the prohibited operation outside the transaction, rather than silently moving unrelated filter updates.
References
- Microsoft: FwpmEngineSetOption0 transaction restrictions
- Microsoft: WFP transaction behavior
- Microsoft: WFP error codes
Looking for a different code? Search another status or error code.