| Previous | Next |
| STATUS_RXACT_INVALID_STATE | STATUS_MAPPED_FILE_SIZE_ZERO |
STATUS_RXACT_COMMIT_FAILURE
The registry-subtree commit did not reach a known final state
This failure is more serious than a rejected operation: the RXACT database remains in the COMMITTING state, so the caller cannot assume either that all actions were applied or that none were applied. A second unqualified commit can compound the uncertainty.
Preserve the original transaction data and inspect the target subtree before recovery. The correct response is application-specific, but it should reconcile expected and actual values and then rebuild from a known state. Registry cleaners or broad deletion are not substitutes for transaction-aware recovery.
What to inspect
- Capture the first I/O or access failure that preceded the commit error.
- Read back every value controlled by the transaction and classify partial changes.
- Avoid destroying the only transaction log or backup before analysis.
- Restart the configuration operation only from an explicit consistent baseline.
References
- ReactOS RTL source: RXACT implementation
- Microsoft Learn: Registry Files
- ReactOS source: Configuration Manager
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.