| Previous | Next |
| STATUS_VHD_BLOCK_ALLOCATION_FAILURE | STATUS_VHD_INVALID_BLOCK_SIZE |
STATUS_VHD_BLOCK_ALLOCATION_TABLE_CORRUPT
STATUS_VHD_BLOCK_ALLOCATION_TABLE_CORRUPT identifies a problem with the table that maps virtual blocks to locations in a legacy dynamic or differencing VHD file. Without a valid mapping, the provider cannot safely decide which backing block supplies a requested virtual offset.
It is more specific than a sparse-header failure: the header can be readable while the table it points to is damaged. It is also different from STATUS_VHD_BITMAP_MISMATCH, which concerns the sector-validity bitmap within an allocated block rather than the table of block locations.
Treat mapping damage as high risk
- Preserve the VHD and all parent disks before using a repair product that could rewrite BAT entries.
- Record the header table offset, expected entry count and image virtual size for comparison with the legacy format specification.
- Do not attach the disk read-write or merge a differencing chain until the block mapping has been independently validated.
References
Looking for a different code? Search another status or error code.