| Previous | Next |
| ERROR_IMAGE_NOT_AT_BASE | ERROR_SEGMENT_NOTIFICATION |
ERROR_RXACT_STATE_CREATED
What ERROR_RXACT_STATE_CREATED means
Windows created registry transaction state for a subtree because it did not previously exist. In practical terms, this status belongs to registry transaction bookkeeping: the registry transaction mechanism initializes state before applying or tracking an operation.
Typical causes
- The subtree is participating in a transaction for the first time
- Recovery code re-created transaction metadata after cleanup
- A registry operation entered an informational transaction path
How to investigate
- Correlate the status with the transaction identifier and registry path
- Verify whether the caller expects an informational result
- Check that the transaction is later committed or rolled back
Developer guidance
Do not report this informational state as data corruption. The important validation is whether the associated registry transaction reaches a defined final state.
Operational interpretation
When ERROR_RXACT_STATE_CREATED appears, first determine whether the operation actually failed, completed with an informational condition, or transferred work to another component. Record the API name, returned value, affected process or object, and the immediately preceding event. For this code, the most useful boundary is the registry transaction bookkeeping boundary; broad machine-wide remediation before that boundary is identified can hide the original evidence.
Example scenario
An incident begins when the subtree is participating in a transaction for the first time. A responder investigating this result should not begin with a generic reboot that destroys the original context. A better first step is to correlate the status with the transaction identifier and registry path. That evidence connects it to its producing operation and reveals whether this particular result is repeatable, expected, or merely secondary.
Logging and telemetry
Telemetry for this Win32 error should preserve its numeric value, component version, process and thread identifiers, operation name, affected object or endpoint, elapsed time, and the first earlier failure in the same activity. Keep the result correlation identifier stable across callbacks so the status can be joined to the request that initiated this exact operation.
Recovery and validation
Apply recovery only after the responsible state has demonstrably changed. After changing that state, repeat one controlled this result scenario and verify both the returned status and the resulting system state. Absence of another log line is not sufficient: confirm that the intended registry transaction bookkeeping action completed, that no resource remains pending, and that later cleanup does not produce a different secondary error.
References
Looking for a different code? Search another status or error code.