| Previous | Next |
| VDS_E_VOLUME_DISK_COUNT_MAX_EXCEEDED | VDS_E_INVALID_PLEX_GUID |
VDS_E_CORRUPT_NOTIFICATION_INFO
This status locates the failure at driver notification metadata. VDS notifications use an object-type discriminant and event-specific structures carrying object IDs and other fields. Corrupt notification information means the driver/provider change record cannot safely be used to update the VDS cache or tell clients which storage object changed.
Why this state matters
The status is not a reason to infer on-disk corruption from the word “corrupt.” Preserve the event log and the VDS object state surrounding the notification. Since VDS normally updates its cache automatically when a valid change notification occurs, malformed notification data can leave clients with an incomplete or stale view until the provider/service state is recovered and refreshed.
Diagnostic focus
- Capture the provider, affected operation, and driver/VDS event log entries from the first occurrence.
- Compare disk and volume object enumerations before and after a service-level refresh performed outside callbacks.
- Do not guess the notification target type or object ID from partially valid bytes.
- If the condition repeats after reenumeration, treat it as a driver/provider defect boundary rather than repeatedly changing disk layout.
Technical references
VDS_NOTIFICATION · VDS_NOTIFICATION_TARGET_TYPE · IVdsAdviseSink::OnNotify · IVdsService::Refresh · MS-VDS error codes
Looking for a different code? Search another status or error code.