| Previous | Next |
| STATUS_VHD_BITMAP_MISMATCH | STATUS_VHD_CHILD_PARENT_ID_MISMATCH |
STATUS_VHD_PARENT_VHD_NOT_FOUND
STATUS_VHD_PARENT_VHD_NOT_FOUND is a differencing-chain result. A child records only changed blocks and relies on a parent for the remaining virtual offsets; the provider cannot complete that chain because it cannot locate the expected parent object.
This is different from STATUS_VHD_PARENT_VHD_ACCESS_DENIED, where the parent can be located but the opening process lacks access. It is also different from STATUS_VHD_CHILD_PARENT_ID_MISMATCH, where a candidate parent was found but its identity does not match the child's recorded expectation.
Recover the chain, not a filename alone
- Inventory every VHD, VHDX and AVHDX file that belongs to the checkpoint or backup set before changing any parent path.
- Use read-only inspection to record the parent locator and the chain order; file names and extensions are not proof of identity.
- Do not merge or mount the child read-write until the intended parent has been verified and the complete chain is available.
References
Looking for a different code? Search another status or error code.