| Previous | Next |
| STATUS_VHD_INVALID_BLOCK_SIZE | STATUS_VHD_PARENT_VHD_NOT_FOUND |
STATUS_VHD_BITMAP_MISMATCH
STATUS_VHD_BITMAP_MISMATCH concerns the bitmap associated with a virtual-disk data block. The bitmap participates in deciding whether data for a virtual sector is present in the current file or must be obtained through another part of the layout, which is especially important for differencing disks.
Unlike STATUS_VHD_BLOCK_ALLOCATION_TABLE_CORRUPT, the provider has reached an allocated block but the block-level validity information does not agree with what it finds. Unlike STATUS_VHD_PARENT_VHD_NOT_FOUND, this is an inconsistency in data mapping, not merely an unavailable parent path.
Do not guess which sector wins
- Preserve the child and every parent before any attach or merge attempt, because the correct source for a sector can depend on the chain.
- Record the virtual offset, block index and whether the image is dynamic or differencing when the status is reported.
- Use a format-aware validator or restore path; copying a block over its bitmap can silently select the wrong version of data.
References
- Microsoft: VHD image-format specification
- Microsoft: VHDX differencing-disk overview
- Microsoft: Merge-VHD
Looking for a different code? Search another status or error code.