| Previous | Next |
| VDS_E_NO_PNP_VOLUME_ARRIVE | VDS_E_NO_PNP_VOLUME_REMOVE |
VDS_E_NO_PNP_DISK_REMOVE
Disk removal in VDS is a distinct notification transition. The disk notification record carries a disk object ID and an event identifying arrival, departure, or modification. This HRESULT indicates that a workflow expected the departure side of that lifecycle but the corresponding PnP/VDS notification did not arrive.
Why this state matters
The useful question is whether the device is physically gone, still enumerated by PnP, or removed from one provider view while a stale VDS disk object remains cached. Reenumerate is the documented VDS request for discovering newly added and newly removed disks; because it only issues the rescan request before returning, clients must not equate method return with completion of the removal notification sequence.
Diagnostic focus
- Preserve the disk object ID that was expected to depart and compare it with the post-rescan enumeration.
- Check PnP/provider events to determine whether removal stalled before VDS notification delivery.
- Allow the reenumeration transition to finish before concluding that the departure event was lost.
- Invalidate client-side references to departed objects only when the current object view confirms the lifecycle change.
Technical references
VDS_DISK_NOTIFICATION · IVdsService::Reenumerate · VDS_NOTIFICATION · IVdsAdviseSink::OnNotify · IVdsService::Refresh
Looking for a different code? Search another status or error code.
