What does HRESULT 0x80042590 (VDS_E_ALIGN_IS_ZERO) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The VDS operation requires an explicit nonzero alignment, but the caller supplied zero.

Previous	Next
VDS_E_ALIGN_NOT_A_POWER_OF_TWO	VDS_E_SHRINK_IN_PROGRESS

VDS_E_ALIGN_IS_ZERO

This HRESULT must be interpreted at the method boundary because VDS APIs do not all treat zero alignment identically. IVdsPack2::CreateVolume2 describes zero as optional and allows the server to determine alignment, yet its documented return-code set also includes VDS_E_ALIGN_IS_ZERO for provider/operation validation. Other creation paths have their own rules for omitted offset and alignment.

Why this state matters

Preserve the exact interface and provider that returned the code. Do not apply a global rule that “zero always means default” across all VDS calls. Check whether the selected provider, volume type, or lower-level validation requires an explicit value, then derive alignment from documented geometry rather than inserting an arbitrary constant.

Diagnostic focus

Record the exact VDS interface/method, provider, and alignment argument.
Check that method documentation before treating zero as an automatic-default request.
If an explicit value is required, derive it from supported alignment policy and disk geometry.
Do not reuse assumptions from CreateVolume2 for partition-creation APIs with different contracts.

Technical references

IVdsPack2::CreateVolume2 · IVdsCreatePartitionEx::CreatePartitionEx · IVdsAdvancedDisk::CreatePartition · VDS_DISK_PROP · MS-VDS error codes

Looking for a different code? Search another status or error code.