HRESULT 0x8004250C (VDS_E_DUP_EMPTY_PACK

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

VDS already has an empty pack with the GUID needed for another empty pack creation.

Previous	Next
VDS_E_CORRUPT_EXTENT_INFO	VDS_E_DRIVER_NO_PACK_NAME

VDS_E_DUP_EMPTY_PACK_GUID

VDS_E_DUP_EMPTY_PACK_GUID This HRESULT is about pack object identity, not duplicate volume or disk GUIDs. A pack has its own object GUID in VDS_PACK_PROP, and the software-provider model allows creating a pack object. The error is raised when an empty pack already exists and another empty pack would duplicate the pack GUID context.

What the VDS state means

Microsoft’s published text specifically says to release the existing empty pack before creating another. That wording matters: the problem is not solved by changing a disk signature or GPT disk GUID. Those are disk-level identifiers exposed by VDS_DISK_PROP, whereas this status concerns the pack container maintained by the VDS software provider.

Diagnostic focus

Enumerate current packs and inspect their object IDs and status before issuing CreatePack or a migration workflow that expects an empty target pack.
Release application references to the existing empty pack when it is no longer needed, then reacquire provider state before creating another.
Do not modify MBR signatures, GPT disk GUIDs, or volume GUID paths to “fix” this HRESULT; those identifiers belong to different VDS objects.
If the empty pack persists unexpectedly across provider refresh/restart, inspect provider cache and Logical Disk Manager events for stale pack state.

Technical references

VDS common return codes · MS-VDS error codes · IVdsSwProvider · VDS_PACK_PROP · VDS_DISK_PROP

Looking for a different code? Search another status or error code.