HRESULT 0x80042534 (VDS_E_NO_EXTENTS_FOR

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

VDS has a plex object but cannot find disk extents that physically back that plex.

Previous	Next
VDS_E_PLEX_SIZE_INVALID	VDS_E_INVALID_PLEX_TYPE

VDS_E_NO_EXTENTS_FOR_PLEX

Plexes sit between a volume and disk extents in the VDS relationship model. IVdsVolume::QueryPlexes enumerates plex objects, and IVdsVolumePlex::QueryExtents returns the VDS_DISK_EXTENT records used by a specific plex. A plex with no extents is therefore a broken topology relationship, not an ordinary empty volume.

Why this state matters

The useful investigation is identity-based. Match the plex GUID from VDS_VOLUME_PLEX_PROP.id to the plexId field on disk extents and inspect provider/cache state. Do not format the volume or assign a drive letter in response; those operations happen above the missing physical mapping. First determine whether the plex was partially created, removed externally, or not yet loaded into the provider view.

Diagnostic focus

Enumerate the volume plexes and record the exact plex GUID that returned no extent mapping.
Query both the plex extents and relevant disk extent maps, comparing plexId fields.
Correlate the condition with recent create, remove-plex, migration, repair, or provider-cache events.
Preserve the topology snapshot before refresh so a later notification does not erase evidence of the missing relationship.

Technical references

MS-VDS IVdsVolume::QueryPlexes · IVdsVolumePlex::QueryExtents · VDS_DISK_EXTENT · MS-VDS storage object relationships · VDS_VOLUME_PLEX_PROP

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