| Previous | Next |
| STATUS_VHD_BLOCK_ALLOCATION_TABLE_CORRUPT | STATUS_VHD_BITMAP_MISMATCH |
STATUS_VHD_INVALID_BLOCK_SIZE
STATUS_VHD_INVALID_BLOCK_SIZE means a declared virtual-block granularity cannot be accepted for the image layout. Block size is not a cosmetic setting: it affects how many mapping entries are required, where data blocks are expected, and which offsets a provider can safely calculate.
This differs from STATUS_VHD_INVALID_SIZE, which concerns the logical capacity of the virtual disk, and from STATUS_VHD_INVALID_FILE_SIZE, which concerns the host-side container length. A valid logical size cannot compensate for an invalid block geometry.
Validate geometry as a set
- Record the logical size, block size, table entry count and relevant header offsets from a read-only copy.
- Check that the image was not truncated, converted incompletely, or produced by a tool that emitted an unsupported geometry.
- Avoid changing block-size fields in isolation because the associated table and payload layout depend on the same value.
References
- Microsoft: VHD image-format specification
- Microsoft: New-VHD examples and block size
- Microsoft: VHDX layout
Looking for a different code? Search another status or error code.