| Previous | Next |
| STATUS_VHD_COULD_NOT_COMPUTE_MINIMUM_VIRTUAL_SIZE | STATUS_RKF_KEY_NOT_FOUND |
STATUS_VHD_ALREADY_AT_OR_BELOW_MINIMUM_VIRTUAL_SIZE
STATUS_VHD_ALREADY_AT_OR_BELOW_MINIMUM_VIRTUAL_SIZE means a virtual disk has reached, or is already below, the safe minimum capacity calculated by the provider. It is a boundary result from a shrink workflow, not a claim that the host file cannot be compacted further.
Compare it with STATUS_VHD_COULD_NOT_COMPUTE_MINIMUM_VIRTUAL_SIZE: that status means no safe threshold is available, whereas this one means the threshold was determined and cannot be crossed. It also differs from STATUS_VHD_RESIZE_WOULD_TRUNCATE_DATA, which applies when a specific proposed target would cut into data.
Separate capacity shrink from file compaction
- Query the virtual disk's minimum size and current virtual size before requesting another shrink.
- Use guest-aware cleanup and partition management if a smaller virtual capacity is actually required, then recompute the safe minimum.
- Use Optimize-VHD or another supported compaction path only for backing-file space reclamation; it does not lower virtual capacity by itself.
References
Looking for a different code? Search another status or error code.