What does HRESULT 0xC0380034 (ERROR_VOLMGR_PACK_HAS_QUORUM) mean?

ERROR_VOLMGR_PACK_HAS_QUORUM

Identify the owner before touching the layout: volmgr pack has quorum

ERROR_VOLMGR_PACK_HAS_QUORUM (0xC0380034) is emitted by the volmgr path when the disk group already has enough healthy configuration copies, so quorum recovery is not applicable. The deciding object is dynamic-disk pack identity, quorum and replicated configuration log, so the first investigation belongs there rather than in a generic “disk failure” bucket.

Keep the first result attached to its request parameters and object instance. Cleanup failures or a later drive-letter change are secondary evidence, not replacements for the original failure.

Minimum diagnostic set

Keep this HRESULT as the primary result if rollback or cleanup reports another code; those later values describe recovery, not the first rejected invariant.

Reproduce without destructive cleanup

1. Capture the API parameters and object map that led to this result; do not begin with cleanup.
2. Build a passing control with the same disks or image copy and preserve pack GUID and name, online state, primary flag, disk inventory, configuration-log sequence numbers, quorum view and failing transaction ID.
3. Run the narrow transition described here: serialize the exact VM_VOLUME_LAYOUT buffer, validate every count and Size field, and compare it with a layout produced by a known-good management API.
4. Compare resulting IDs, counts, health and ownership to prove the caller crossed the result invariant rather than suppressing it.

Use ERROR_VOLMGR_NO_VALID_LOG_COPIES as the nearest comparison. This result is specific to the disk group already has enough healthy configuration copies, so quorum recovery is not applicable; the neighboring result belongs to another validation or lifecycle branch. Keeping both names prevents a generic storage label from hiding the actual owner.

Mechanism-specific note

Quorum recovery is intended for a pack that lacks enough mutually consistent configuration copies. If quorum already exists, the safer action is normal reconciliation or repair of the outlier disk. Record which copies agree on the highest sequence so a “healthy quorum” result is not confused with every disk being healthy.

Restore the contract

Repair the pack configuration through supported dynamic-disk management, preserving GUIDs and the newest valid log sequence; avoid sector-level edits to replicated metadata. After correcting it, reopen the pack, volume, tier, snapshot or virtual disk so no cached generation participates in the validation run.

• the first retry uses newly enumerated identifiers rather than cached handles.
• The durable metadata or provider state agrees with the success returned after it.
• A second run after close/reopen does not recreate the rejected condition.
• the nearby ERROR_VOLMGR_NO_VALID_LOG_COPIES path remains separately testable and separately logged.

Technical references

• Microsoft: COM error codes for VOLMGR, VHD and SDIAG — defines the volmgr objects used to interpret it.
• Microsoft: Virtual Disk Service object model — primary API or object-model reference.
• Microsoft: Pack object — use this source to verify volmgr state and parameters.
• Microsoft: Virtual Disk Service common return codes — documents the supported management path relevant to this HRESULT.