| Previous | Next |
| VDS_E_NO_PNP_DISK_ARRIVE | VDS_E_NO_PNP_DISK_REMOVE |
VDS_E_NO_PNP_VOLUME_ARRIVE
This HRESULT is specifically about volume arrival, not disk arrival. A physical disk can already be present while creation, import, mount, or layout processing is expected to expose a VDS volume object. VDS has a separate VDS_VOLUME_NOTIFICATION subject with arrival, departure, and modification events, so receiving a disk event does not satisfy the volume-arrival transition.
Why this state matters
The correct investigation follows the object graph from disk layout to volume enumeration. Capture the operation that was supposed to create or reveal the volume, wait for its async result if applicable, and then compare the current VDS volume list with the notification stream. A missing drive letter is not equivalent to a missing volume: access-path assignment is a separate layer.
Diagnostic focus
- Record the operation that should have caused the volume to appear and its final asynchronous HRESULT.
- Compare current volume object IDs with received
VDS_NF_VOLUME_ARRIVEnotifications. - Inspect the disk layout and provider cache before blaming Mount Manager or drive-letter assignment.
- Do not treat a disk-arrival event as proof that the expected volume object was created.
Technical references
VDS_VOLUME_NOTIFICATION · VDS_NOTIFICATION · IVdsAsync::Wait · IVdsService::Refresh · VDS common return codes
Looking for a different code? Search another status or error code.