| Previous | Next |
| VDS_E_EXTENT_SIZE_LESS_THAN_MIN | VDS_E_NO_FREE_SPACE |
VDS_E_BOOT_PARTITION_NUMBER_CHANGE
This is the failing counterpart to the informational partition-number warning. During disk migration, VDS evaluates whether moving the selected disks would change the ordinal number of the boot partition. In this code path the change is a blocking precondition, so the migration does not simply proceed with a warning. The problem belongs to boot-sensitive layout migration, not to free space or file-system health.
Why this state matters
Preserve the source and target pack layouts and inspect the exact partition order on the boot disk. Review the intended migration set: omitting or adding a disk can change how the target layout is reconstructed. Do not work around the error by editing BCD first; the storage transition was rejected before a new boot layout could be considered authoritative.
Diagnostic focus
- Record the boot disk partition order and offsets before retrying migration.
- Verify the complete disk set supplied to the pack migration operation.
- Compare source and target pack topology and identify the partition whose ordinal would change.
- Change the migration plan first; repair boot configuration only after a supported storage layout exists.
Technical references
MS-VDS error codes · IVdsPack::MigrateDisks · VDS Pack Object · BCDEdit command-line options · BCDBoot command-line options
Looking for a different code? Search another status or error code.