| Previous | Next |
| VDS_E_NO_PNP_VOLUME_REMOVE | VDS_E_EXTENT_EXCEEDS_DISK_FREE_SPACE |
VDS_E_PROVIDER_EXITING
VDS_E_PROVIDER_EXITING This HRESULT describes provider lifecycle, not disk media health. A provider that is exiting is no longer a stable endpoint for new VDS work, so a method may fail even though the disk, pack, or volume object was valid moments earlier. Retaining a COM interface pointer does not guarantee that the underlying provider remains operational.
What the VDS state means
The practical distinction is between an object-state failure and a provider teardown. Refreshing a stale object cannot make an exiting provider accept work. The caller should preserve the provider identity, stop issuing dependent operations, and allow service/provider recovery to establish a new object view before reacquiring objects.
Diagnostic focus
- Check whether the VDS service or a vendor provider is stopping, restarting, upgrading, or crashing at the time of the HRESULT.
- Cancel or drain application work that targets objects owned by the exiting provider; do not immediately fan out retries through cached interface pointers.
- After recovery, reenumerate providers and reacquire pack/disk/volume objects rather than assuming old object references describe the current provider instance.
- If provider exit is unexpected, save event logs and crash/service-control evidence before restarting the management stack.
Technical references
VDS common return codes · MS-VDS error codes · IVdsProvider · IVdsService::Refresh · VDS interfaces and structures
Looking for a different code? Search another status or error code.