| Previous | Next |
| VDS_S_UPDATE_BOOTFILE_FAILED | VDS_S_VOLUME_COMPRESS_FAILED |
VDS_S_BOOT_PARTITION_NUMBER_CHANGE
This warning identifies a topology change with boot consequences. Partition numbers are ordinal positions in a disk layout and can change when migration or layout operations insert, remove, or reorder partition entries. Boot configuration is stored separately from the VDS object model, so a successful storage change can still require the boot environment to be reconciled with the new layout.
Why this state matters
Do not treat the warning as a failed migration. Capture the partition table before and after the operation and determine which partition contains the Windows installation and which partition is the system partition. Then verify the BCD store and boot files. The useful evidence is disk identity, partition style, offsets, and boot entries; a remembered drive letter is insufficient because access paths are assigned at a different layer.
Diagnostic focus
- Record the original and resulting partition order, offsets, and disk identity.
- Confirm which partition is the Windows boot volume and which is the system partition.
- Inspect BCD entries after the storage operation if automatic boot-file update reports a warning.
- Do not recreate partitions merely to restore the old ordinal number without checking boot configuration.
Technical references
MS-VDS error codes · IVdsPack::MigrateDisks · BCDEdit command-line options · BCDBoot command-line options · Set up dynamic boot partition mirroring on GPT disks
Looking for a different code? Search another status or error code.