| Previous | Next |
| ERROR_RM_NOT_ACTIVE | ERROR_DIRECTORY_NOT_RM |
ERROR_RM_METADATA_CORRUPT
Resource-manager metadata cannot be trusted for transactional recovery
ERROR_RM_METADATA_CORRUPT belongs to the Windows Kernel Transaction Manager transaction-processing model. A durable RM needs persistent state to connect its own resource changes with KTM enlistments and recovery outcomes. Microsoft describes RM logging and recovery information as the mechanism used after failure to reconstruct outstanding transactional work. Corrupt RM metadata therefore affects the resource manager control state itself, not merely one application record inside a transaction.
Identify the RM owner and preserve its metadata and log before attempting reset. Correlate the failure with CLFS, NTFS, storage, and abrupt-restoration events. Use the owning component recovery procedure or `fsutil resource` diagnostics for TxF resource managers where applicable. Deleting metadata to make the RM start can discard knowledge of in-doubt transactions and leave resource data inconsistent with KTM. A repair decision must account for whether the RM protects durable application state.
What to inspect
- Preserve the RM metadata and transaction log as a matched recovery set.
- Check storage and CLFS errors at the time corruption was first detected.
- Use the RM owner supported repair or recreation workflow rather than deleting metadata files manually.
References
- Microsoft: KTM resource-manager log streams and recovery
- Microsoft: KTM recovery processing and presumed abort
- Microsoft: transactional resource manager and log management
Looking for a different code? Search another status or error code.