| Previous | Next |
| VDS_E_DISK_CONFIGURATION_NOT_IN_SYNC | VDS_E_DISK_DYNAMIC |
VDS_E_DISK_CONFIGURATION_UPDATE_FAILED
This HRESULT occurs after a configuration change has reached the persistence boundary. The published VDS message is deliberately plural: one or more disks failed to receive the new configuration. In a multi-disk dynamic layout, that is different from validation failure before any write was attempted and can leave the provider reconciling members with different metadata generations.
Why this state matters
Treat the result as a potentially partial topology update. Record every disk in the affected pack and determine which members are online, writable, and returning I/O errors. Query the pack layout again before repeating the request. Blind retry can obscure which disk failed first and may produce additional metadata churn without addressing the underlying device or path failure.
Diagnostic focus
- Capture the complete disk set for the pack or volume operation, not only the disk that surfaced the HRESULT.
- Check disk status, read-only state, and I/O events for each member involved in the configuration write.
- Requery extents and pack membership after the failure to identify partial state changes.
- Preserve the original operation and provider events before retrying the configuration update.
Technical references
IVdsDisk · VDS_DISK_PROP · IVdsDisk::QueryExtents · Basic and Dynamic Disks · MS-VDS error codes
Looking for a different code? Search another status or error code.