| Previous | Next |
| STATUS_FWP_WRONG_SESSION | STATUS_FWP_TXN_IN_PROGRESS |
STATUS_FWP_NO_TXN_IN_PROGRESS
The API requires a caller-controlled transaction boundary
STATUS_FWP_NO_TXN_IN_PROGRESS means the operation requires an explicit transaction instead of WFP’s normal implicit transaction behavior. The failure is about the state of the current engine session, not about a malformed filter or a failed packet classification.
Open a read/write transaction only around the related policy changes, then make the required calls and commit or abort based on their results. Record the begin, the individual WFP calls, and the decision to commit; otherwise, a retry can accidentally run in a different transaction context.
What to check
- The API’s documented transaction requirement and the engine handle passed to it.
- Whether
FwpmTransactionBegin0succeeded before the operation. - Whether a wrapper opened and closed a separate session or committed early.
- The rollback plan if one of several related policy changes fails.
References
- Microsoft: WFP error codes
- Microsoft: WFP sessions, transactions, and object lifetimes
- Microsoft: WFP object model
Looking for a different code? Search another status or error code.