What does NTSTATUS 0xC03A000F (STATUS_VHD_CHILD_PARENT_TIMESTAMP_MISMATCH) mean?

STATUS_VHD_CHILD_PARENT_TIMESTAMP_MISMATCH

STATUS_VHD_CHILD_PARENT_TIMESTAMP_MISMATCH means a differencing child's recorded parent timestamp does not agree with the parent the provider opened. The comparison is a chain-consistency safeguard, not a complaint about the host clock or the time shown to the guest OS.

Unlike STATUS_VHD_CHILD_PARENT_ID_MISMATCH, the parent identity can still match. Unlike STATUS_VHD_PARENT_VHD_ACCESS_DENIED, the provider reached the parent well enough to inspect its metadata. The mismatch can indicate that the parent was modified after the child was created or that the wrong revision was selected.

Determine whether the parent changed

• Compare the parent image against the backup or checkpoint inventory that produced the child.
• Record whether any resize, conversion, restore or direct edit occurred on the candidate parent after the child was created.
• Avoid bypassing the check unless the exact chain history has been independently established and preserved.

References

• Microsoft: VHD image-format specification
• Microsoft: VHDX parent locator
• Microsoft: Get-VHD

Looking for a different code? Search another status or error code.