| Previous | Next |
| VDS_E_NO_VOLUME_PATHNAME | VDS_E_NO_IMPORT_TARGET |
VDS_E_PROVIDER_CACHE_OUTOFSYNC
VDS keeps provider-visible storage objects in a cache, while the underlying volume-management driver maintains its own state. This HRESULT marks disagreement between those two views. It is different from a corrupt cache: the structures can be readable but describe an older disk, pack, volume, or layout state than the driver currently reports.
Why this state matters
IVdsService::Refresh refreshes the service view of objects already known to VDS, whereas Reenumerate discovers newly added or removed disks. Choosing the wrong operation can leave the original mismatch unresolved. The most useful evidence is the object identity and layout before and after the external change that made the cache stale.
Diagnostic focus
- Log the provider ID, VDS object ID, and the operation that first observed the cache/driver mismatch.
- Use
Refreshfor changed state of known objects andReenumeratewhen the physical disk set changed. - Check for storage changes made by Disk Management, DiskPart, cluster software, or another VDS client between enumeration and the failing call.
- Reacquire object interfaces after synchronization instead of continuing with a reference that was already diagnosed as stale.
Technical references
IVdsService::Refresh · IVdsService::Reenumerate · VDS common return codes · MS-VDS error codes · IVdsDisk::GetProperties
Looking for a different code? Search another status or error code.
