| Previous | Next |
| VDS_E_DISK_IN_USE_BY_VOLUME | VDS_E_VOLUME_NOT_MOUNTED |
VDS_E_ASYNC_OBJECT_FAILURE
This HRESULT occurs at the async-object boundary rather than reporting failure of the storage work itself. VDS uses IVdsAsync to represent long-running create, format, attach, login, shrink, and related operations. When initialization of that helper fails, the caller has no valid progress/result object with which to wait for or query the operation.
Why this state matters
Do not interpret the status as “the disk operation ran and failed.” The more immediate question is whether the underlying operation was ever successfully represented as an asynchronous task. Preserve the initiating method, provider identity, and any service/provider event log evidence. Retrying blindly can be dangerous if the caller cannot prove whether an operation with side effects was actually started.
Diagnostic focus
- Check whether the initiating call returned a non-null
IVdsAsyncinterface and do not dereference a missing helper object. - Preserve the initiating VDS method and target object ID so provider or service events can be correlated.
- Before retrying a topology-changing request, refresh the object state and verify whether any side effect occurred.
- Distinguish async-object initialization failure from the final HRESULT normally delivered through
WaitorQueryStatus.
Technical references
IVdsAsync · IVdsAsync::Wait · IVdsAsync::QueryStatus · IVdsService · MS-VDS error codes
Looking for a different code? Search another status or error code.