What does HRESULT 0x0004258B (VDS_S_PLEX_NOT_LOADED_TO_CACHE) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The plex exists in the driver but has not yet appeared in the VDS provider cache.

Previous	Next
VDS_S_FS_LOCK	VDS_S_WINPE_BOOTENTRY

VDS_S_PLEX_NOT_LOADED_TO_CACHE

This warning describes a temporary difference between the driver view and the provider cache. The published VDS error table explicitly says that the plex is present in the driver and that a volume-modified notification will be sent after the plex is loaded into the provider cache. A caller should therefore preserve the volume/plex operation result and wait for cache convergence rather than treating the plex as permanently missing.

Why this state matters

Plexes are topology objects beneath a volume, used for simple, spanned, striped, mirrored, and parity layouts. Reissuing a break, remove, or repair request while the newly changed plex is still absent from cache risks acting on stale topology. Track the affected volume ID and observe the later modification notification or requery after the service view has synchronized.

Diagnostic focus

Keep the volume and expected plex identifiers from the operation that changed topology.
Observe subsequent VDS_NF_VOLUME_MODIFY notifications before issuing another plex-changing operation.
Requery the volume plex enumeration after the provider cache converges.
Do not infer that the driver lost the plex merely because the provider cache has not loaded it yet.

Technical references

MS-VDS error codes · Volume Plex Object · VDS_VOLUME_NOTIFICATION · IVdsAdviseSink::OnNotify · IVdsService::Refresh

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