| Previous | Next |
| VDS_E_DMADMIN_METHOD_CALL_FAILED | VDS_E_PROVIDER_VOL_OPEN |
VDS_E_PROVIDER_VOL_DEVICE_NAME_NOT_FOUND
VDS distinguishes a volume object from the paths used to access the underlying volume. This HRESULT says the provider failed while retrieving the device form of the volume pathname. It is therefore narrower than “volume not found”: a cached VDS volume object may exist while the provider cannot map it to the current device namespace needed for a lower-level operation.
Why this state matters
The diagnostic priority is identity and lifetime. Volume GUID paths, mount points, drive letters, and device names are not interchangeable identifiers. Arrival/removal events and mount-point changes can occur while a client is holding older VDS object references. Refresh the VDS view and compare the volume object ID and current volume properties before assuming that a missing drive letter is the cause.
Diagnostic focus
- Capture the VDS volume object ID and all current access paths separately from the unavailable device-form pathname.
- Check for recent volume arrival, removal, or mount-point notifications before using a cached volume reference.
- Call
Refreshoutside a notification callback and requery the object properties. - Do not manufacture a kernel device path from a drive letter or volume display name; let the provider resolve its documented object.
Technical references
VDS_VOLUME_PROP · IVdsService::Refresh · VDS_VOLUME_NOTIFICATION · VDS_NOTIFICATION · IVdsAdviseSink::OnNotify
Looking for a different code? Search another status or error code.
