| Previous | Next |
| ERROR_TRANSACTION_RECORD_TOO_LONG | ERROR_TRANSACTION_INTEGRITY_VIOLATED |
ERROR_IMPLICIT_TRANSACTION_NOT_SUPPORTED
The operation requires explicit transaction handling rather than implicit context
ERROR_IMPLICIT_TRANSACTION_NOT_SUPPORTED belongs to the Windows Kernel Transaction Manager transaction-processing model. KTM itself exposes explicit transaction objects and handles. Some Windows APIs can consult transaction context indirectly, but that behavior is component-specific. This error states that the target path does not support the implicit form requested by the caller; it does not mean that KTM is entirely unavailable or that explicit transactions cannot be created.
Identify how the application supplies transaction context. Look for wrappers that assume a current transaction is automatically consumed by every lower-level API. Compare the failing API contract with the explicit transacted variant, if one exists, and pass the transaction handle deliberately. In mixed libraries, also check whether a helper enters a transaction scope but invokes a subsystem that never implemented implicit enlistment. Retrying under the same ambient context does not add support.
What to inspect
- Find the exact API that rejected implicit transaction use.
- Use an explicit transaction handle or documented transacted API where supported.
- Audit framework transaction scopes that cross into native components with different context semantics.
References
- Microsoft: KTM programming model and transaction handles
- Microsoft: KTM transaction, TM, RM, and enlistment functions
- Microsoft: Kernel Transaction Manager overview
Looking for a different code? Search another status or error code.