| Previous | Next |
| STATUS_VOLMGR_VOLUME_NOT_MIRRORED | STATUS_VOLMGR_VOLUME_OFFLINE |
STATUS_VOLMGR_VOLUME_NOT_RETAINED
The operation expected retained-partition state that the volume does not have
STATUS_VOLMGR_VOLUME_NOT_RETAINED means the selected volume lacks the retain-partition association expected by the requested operation. The corresponding VDS error wording uses the same retained-association concept.
The public status tables identify the state mismatch but do not provide enough information to infer why the caller expected a retained partition. Do not invent a media-failure or redundancy explanation from the word “retain”; diagnose the exact management command and the volume properties it checked.
Compare this result with STATUS_VOLMGR_VOLUME_RETAINED, which is the opposite precondition failure. If software is toggling retained state, record the operation sequence and refresh the volume after each successful transition so a cached Boolean does not drive the next call.
What to inspect
- Identify the exact API or management command that requires a retained-partition association.
- Query current volume state instead of assuming a previous retain operation succeeded.
- If the workflow changes retained state, serialize those changes and consume their completion result before continuing.
References
- Microsoft VOLMGR definition of STATUS_VOLMGR_VOLUME_NOT_RETAINED.
- MS-VDS retained-partition association error wording.
- MS-DMRP asynchronous task and state-transition behavior.
Looking for a different code? Search another status or error code.