| Previous | Next |
| VDS_E_VD_ALREADY_COMPACTING | VDS_E_VD_ALREADY_ATTACHED |
VDS_E_VD_ALREADY_MERGING
This HRESULT rejects a second merge request because the selected virtual disk is already in the MERGING state. VDS merge operates on a child and a specified number of parents in a differencing chain. Running two merge requests against the same chain would make parent/child state and block movement ambiguous, so the provider serializes the operation.
Why this state matters
The first merge can continue asynchronously after the initiating method returns. The management application must retain the corresponding operation result and should not infer completion from the absence of immediate errors in another process. After merge, child disks invalidated by the operation are not automatically deleted, so chain inspection is still required.
Diagnostic focus
- Match the active merge to the child virtual disk and record merge depth and parent path information.
- Wait for the first merge operation to finish; do not submit another merge as a timeout-recovery mechanism.
- Prevent other orchestration components from independently mutating the same differencing chain.
- Re-enumerate chain properties after the final result before deleting child backing files or starting a new merge.
Technical references
IVdsOpenVDisk::Merge · VDS_VDISK_STATE · VDS_VDISK_PROPERTIES · MS-VDS virtual disk state transitions · IVdsOpenVDisk
Looking for a different code? Search another status or error code.