| Previous | Next |
| STATUS_IMAGE_NOT_AT_BASE | STATUS_SEGMENT_NOTIFICATION |
STATUS_RXACT_STATE_CREATED
Registry transaction state was initialized on demand
The RXACT runtime did not find an existing transaction state for the specified registry subtree and created one. This is informational: it describes setup of the transaction context rather than completion of the registry modifications that will later be committed or aborted.
A caller should retain the returned context and follow the expected RXACT lifecycle. Reinitializing the same subtree repeatedly can hide ownership bugs, while assuming that this status means the data is already durable can expose partially prepared configuration to later code.
What to inspect
- Log the subtree path and the component that initialized the transaction.
- Confirm that exactly one owner controls commit or abort for the context.
- Separate initialization success from the result of applying the queued actions.
- Inspect cleanup paths for abandoned contexts after exceptions or process shutdown.
References
- ReactOS RTL source: RXACT implementation
- ReactOS source: Configuration Manager
- Microsoft Open Specifications: NTSTATUS values
- Microsoft Windows SDK metadata: ntstatus.h
Looking for a different code? Search another status or error code.