| Previous | Next |
| VDS_E_DISK_CONFIGURATION_CORRUPTED | VDS_E_DISK_CONFIGURATION_UPDATE_FAILED |
VDS_E_DISK_CONFIGURATION_NOT_IN_SYNC
This status identifies divergence between two configuration views. VDS and its software provider keep an object/cache representation of disks and volume topology while the storage stack maintains the actual layout and metadata. A mismatch means the requested update cannot safely proceed using the current in-memory model.
Why this state matters
The correct first action is reconciliation, not another topology change. Query partitions and extents again and correlate any external layout modification that occurred outside the current VDS workflow. A disk-modify notification can be generated when disk properties or extents change, but a client holding old object state can still make decisions from stale data. Preserve object IDs and offsets rather than comparing only drive letters.
Diagnostic focus
- Requery partition and extent information from the current VDS service view.
- Identify external disk-management, imaging, firmware, or provider operations that changed the layout.
- Compare disk object IDs and exact offsets instead of relying on access paths or partition ordinal numbers.
- Retry only after the cached/in-memory topology matches the layout reported by the storage stack.
Technical references
IVdsAdvancedDisk::QueryPartitions · IVdsDisk::QueryExtents · VDS_PARTITION_PROP · VDS Disk Object · MS-VDS error codes
Looking for a different code? Search another status or error code.