| Previous | Next |
| VDS_E_NO_EXTENTS_FOR_VOLUME | VDS_E_INTERNAL_ERROR |
VDS_E_DISK_NOT_LOADED_TO_CACHE
This HRESULT is tied to migration and cache population. The disk operation has advanced far enough that VDS expects the migrated disk to be represented in the provider cache, but the corresponding cached disk object is unavailable. That is different from a disk that was never selected for import or a disk that does not belong to the source pack.
Why this state matters
Because VDS object references can become stale, preserve the migration result and then examine the current provider view. Refresh refreshes cached object information and sends arrival/modification/removal notifications needed to synchronize callers, while Reenumerate is for newly added or removed physical disks. Use the operation that matches the suspected boundary instead of repeatedly migrating the same disk.
Diagnostic focus
- Capture the migrated disk ID, source/target pack IDs, and final migration HRESULT.
- Query the provider cache after the migration and verify whether a disk object with the expected identity appears.
- Use
Refreshfor stale cached object state; reserveReenumeratefor physical discovery changes. - Do not submit the same migration again until current pack membership and disk identity are known.
Technical references
VDS common return codes · IVdsService::Refresh · IVdsService::Reenumerate · IVdsAdviseSink::OnNotify · IVdsService
Looking for a different code? Search another status or error code.