| Previous | Next |
| VDS_E_BAD_PNP_MESSAGE | VDS_E_NO_PNP_VOLUME_ARRIVE |
VDS_E_NO_PNP_DISK_ARRIVE
This status is about discovery sequencing. VDS models disk events with VDS_DISK_NOTIFICATION; disk arrival and departure are distinct event types associated with a VDS disk object ID. IVdsService::Reenumerate requests discovery of newly added or removed disks and returns after the bus rescan request is issued, so the PnP work may still be incomplete when that method returns.
Why this state matters
The absence of the expected arrival notification should therefore be investigated as an event/discovery problem, not as proof that media contents are corrupt. Compare the physical device state, PnP enumeration, provider events, and the VDS disk object list. A caller that immediately assumes synchronous arrival after Reenumerate can also create its own timing failure.
Diagnostic focus
- Record when the rescan or device-add action was issued and when the client expected the disk-arrival event.
- Enumerate current VDS disk objects after allowing the PnP transition to complete and compare object IDs.
- Inspect provider/PnP events for a device that arrived but failed later during provider registration.
- Do not substitute a volume-arrival event; disk and volume notifications are separate typed subjects.
Technical references
IVdsService::Reenumerate · VDS_DISK_NOTIFICATION · VDS_NOTIFICATION · IVdsAdviseSink::OnNotify · VDS common return codes
Looking for a different code? Search another status or error code.