HRESULT 0x80042513 (VDS_E_NO_PNP_VOLUME

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

VDS expected a volume-departure event, but no matching PnP volume-removal notification arrived.

Previous	Next
VDS_E_NO_PNP_DISK_REMOVE	VDS_E_PROVIDER_EXITING

VDS_E_NO_PNP_VOLUME_REMOVE

This status is the volume-side counterpart to missing disk removal. VDS treats volumes as independent notification subjects, so a disk can remain present while one volume disappears because of layout, plex, import, or provider changes. The expected evidence is a VDS_NF_VOLUME_DEPART event for the affected volume object, not a generic device-change message.

Why this state matters

Before forcing cleanup, compare the current VDS volume enumeration and access paths with the object ID that was supposed to depart. Mount-point changes are also reported through their own notification type. Removing drive letters or mounted folders does not prove that a volume object has departed, and stale object references should be resolved through the current VDS service view.

Diagnostic focus

Log the expected volume object ID and the operation that should have removed it.
Compare volume departure notifications with current volume enumeration after the provider state settles.
Distinguish removal of access paths from removal of the VDS volume object itself.
Use a later refresh outside OnNotify if the cache appears stale; do not refresh recursively inside the callback.

Technical references

VDS_VOLUME_NOTIFICATION · VDS_NOTIFICATION · IVdsAdviseSink::OnNotify · IVdsService::Refresh · IVdsService

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