| Previous | Next |
| ERROR_VOLUME_MOUNTED | ERROR_NOTIFY_CLEANUP |
ERROR_RXACT_COMMITTED
A registry transaction state already existed and was committed
ERROR_RXACT_COMMITTED corresponds to Win32 error value documented as: This success level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted. The commit has now been completed. The registry subtree already had RXACT state, and the operation committed that state rather than creating a wholly new transaction context. This is mostly encountered in low-level or legacy registry transaction handling.
Where the result appears in real systems
- Native registry initialization.
- Compatibility components.
- Recovery of a previously prepared registry transaction.
What to collect before making changes
Record the affected registry path, operation sequence, process identity, and whether recovery followed a crash; inspect surrounding configuration changes and verify the committed values.
Handling and recovery
Treat the subtree as committed and avoid replaying the same mutation blindly. Recovery code should verify resulting values before deciding whether another transaction is necessary.
What not to infer from this code
This result is not the same as an uncommitted transaction failure; it reports an already-existing state that reached commit.
References
Looking for a different code? Search another status or error code.