| Previous | Next |
| STATUS_CTLOG_INVALID_TRACKING_STATE | STATUS_VHD_METADATA_FULL |
STATUS_CTLOG_INCONSISTENT_TRACKING_FILE
The tracking metadata no longer describes a coherent history
The .rct and related metadata are not guest data; they are host-side records used to reconstruct changed regions. This status means the tracking file cannot be interpreted as a consistent sequence for the associated virtual disk. Possible causes include interrupted metadata updates, storage faults, mismatched files restored from backup, or manual movement of only part of a VHDX set.
Using the file despite the error risks producing an incomplete incremental backup. Recovery procedures therefore focus on preserving the VHDX, retiring the damaged tracking metadata, and generating a new trusted baseline through the supported Hyper-V or backup-product workflow.
What to inspect
- Preserve copies of the VHDX, .rct, and .mrt files plus VMMS and storage event logs for analysis.
- Verify that all files came from the same VM state and were not restored or copied independently.
- Check the underlying volume for I/O, filesystem, and cluster ownership errors.
- Use the vendor-supported RCT reset procedure and schedule a new full backup.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: antivirus exclusions for Hyper-V hosts
- Microsoft: Hyper-V backup approaches
- Microsoft: GET_VIRTUAL_DISK_INFO change-tracking state
Looking for a different code? Search another status or error code.