| Previous | Next |
| ERROR_RM_METADATA_CORRUPT | ERROR_TRANSACTIONS_UNSUPPORTED_REMOTE |
ERROR_DIRECTORY_NOT_RM
The path does not contain the resource manager expected by the transactional operation
ERROR_DIRECTORY_NOT_RM belongs to the Windows Kernel Transaction Manager transaction-processing model. Transactional NTFS associates a transactional resource manager with filesystem state on an NTFS volume. Windows exposes `fsutil resource` commands that start and manage a transactional resource manager for a specified path. This status means the directory supplied to an RM-specific operation does not identify such a resource-manager location; it is not a general directory-not-found result.
Confirm the exact resolved path, volume, and mount point. A junction, volume remount, or configuration copied from another server can make a familiar directory resolve to a different filesystem. Query the resource manager through supported tools before modifying `$Txf` or other reserved NTFS state. If the application intended a custom KTM RM rather than TxF, this filesystem-oriented operation is probably being called against the wrong abstraction entirely.
What to inspect
- Resolve the directory to its actual NTFS volume and mount point.
- Use supported resource-manager queries before attempting start, repair, or log changes.
- Do not create or edit reserved TxF directories manually to make a path appear to be an RM.
References
- Microsoft: transactional resource manager and log management
- Microsoft: Transactional NTFS and KTM coordination
- Microsoft: Kernel Transaction Manager overview
Looking for a different code? Search another status or error code.