What does HRESULT 0xC0380032 (ERROR_VOLMGR_PACK_NAME_INVALID) mean?

ERROR_VOLMGR_PACK_NAME_INVALID

Why this is narrower than a generic disk error: volmgr pack name invalid

ERROR_VOLMGR_PACK_NAME_INVALID has unsigned value 0xC0380032. In the volmgr layer, the operation is rejected because the proposed dynamic-disk pack name violates the accepted naming or encoding contract. Diagnosis of this result should follow dynamic-disk pack identity, quorum and replicated configuration log through one controlled state transition.

Storage facts that change the diagnosis

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

A/B test

1. Associate it with one caller, one transaction and one target UniqueId.
2. Save the pre-call and post-call inventories, including pack GUID and name, online state, primary flag, disk inventory, configuration-log sequence numbers, quorum view and failing transaction ID.
3. Use this A/B case without touching unrelated storage: 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. Validate both the HRESULT and the on-disk or provider state after the relevant reopen, remount or attach cycle.

ERROR_VOLMGR_UNEXPECTED_DISK_LAYOUT_CHANGE describes a nearby but different storage condition; this result indicates that the proposed dynamic-disk pack name violates the accepted naming or encoding contract.

Mechanism-specific note

Validate the proposed name before beginning a metadata transaction. Record the original Unicode string, normalized form, length and any characters rejected by the management layer. A display label produced by a UI can include punctuation or truncation that is legal for presentation but not for the pack metadata field.

Corrective action and regression check

Repair the pack configuration through supported dynamic-disk management, preserving GUIDs and the newest valid log sequence; avoid sector-level edits to replicated metadata. The repair is incomplete until a fresh enumeration and new handle observe the corrected state.

• The original request now reaches success or a documented later status with the intended layout and access mode.
• A new enumeration reports internally consistent IDs, counts, geometry and ownership for the corrected object.
• The passing state survives the relevant lifecycle transition, such as reopen, remount, owner change or detach/attach.
• The application still distinguishes it from ERROR_VOLMGR_UNEXPECTED_DISK_LAYOUT_CHANGE and has no unbounded retry loop.

Technical references

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