| Previous | Next |
| FWP_E_NO_TXN_IN_PROGRESS | FWP_E_TXN_ABORTED |
FWP_E_TXN_IN_PROGRESS
FWP_E_TXN_IN_PROGRESS means that the attempted WFP call is forbidden while an explicit transaction is active. This is distinct from a conflict or timeout: the API contract itself requires the caller to finish the current transaction before it can perform the requested operation.
Typical examples
Microsoft documents this behavior for actions such as net-event subscription and certain engine or security operations. These calls do not participate in the same policy change transaction as filter additions or deletions, so wrapping a large installer workflow in one oversized transaction can cause this error.
Correct sequencing
- Commit or abort the current transaction once its related policy changes are complete.
- Perform subscriptions, engine options, or other non-transactional operations outside that scope.
- Keep transaction scopes narrow enough that error handling has a clear rollback boundary.
Microsoft: WFP error codes · Microsoft: net-event subscription transaction restriction · Microsoft: WFP transaction semantics
Looking for a different code? Search another status or error code.