| Previous | Next |
| VDS_E_VOLUME_NOT_RETAINED | VDS_E_ALIGN_BEYOND_FIRST_CYLINDER |
VDS_E_VOLUME_RETAINED
This is the opposite retained-state precondition from VDS_E_VOLUME_NOT_RETAINED. VDS already maintains a volume-to-partition association, so repeating an operation that expects to create that association is rejected. The status is about idempotency and current provider state, not duplicate GPT partition entries.
Why this state matters
Requery the volume and disk layout before retrying. If a previous request timed out or the client lost its asynchronous result, the association may have been completed even though the caller did not observe success. Use current VDS object state as the source of truth and continue the higher-level workflow from the retained state rather than issuing the same transition again.
Diagnostic focus
- Check whether an earlier request completed after the client timed out or disconnected.
- Requery current volume/extent state instead of replaying the retain transition.
- Distinguish retained association from a duplicate partition GUID or duplicate volume object.
- Make the calling workflow idempotent by accepting the already-retained state where appropriate.
Technical references
IVdsAdvancedDisk · VDS Disk Object · IVdsDisk::QueryExtents · IVdsAdvancedDisk::QueryPartitions · MS-VDS error codes
Looking for a different code? Search another status or error code.