| Previous | Next |
| STATUS_VHD_DRIVE_FOOTER_MISSING | STATUS_VHD_DRIVE_FOOTER_CORRUPT |
STATUS_VHD_DRIVE_FOOTER_CHECKSUM_MISMATCH
STATUS_VHD_DRIVE_FOOTER_CHECKSUM_MISMATCH means that a legacy VHD footer was located, but its checksum did not agree with the bytes the VHD provider read. The footer is a container-level record, not guest NTFS, ReFS or application data.
This differs from STATUS_VHD_DRIVE_FOOTER_CORRUPT, where footer fields can be structurally or semantically invalid even if the failure is not reported specifically as a checksum problem. A checksum mismatch is evidence that the footer bytes changed, were torn, or were read inconsistently; it is not proof of which event caused that change.
What is useful to compare
- Compare the footer from a preserved copy with the specification-defined checksum calculation instead of editing the checksum field in place.
- For a dynamic or differencing legacy VHD, compare the beginning and ending footer copies while keeping the original file unchanged.
- Check host-storage, transfer and backup logs for a partial copy or write interruption before deciding whether the image should be recovered or restored.
References
Looking for a different code? Search another status or error code.