| Previous | Next |
| VDS_S_SYSTEM_PARTITION | VDS_S_DEFAULT_PLEX_MEMBER_IDS |
VDS_S_NO_NOTIFICATION
This warning is narrower than the four PnP-specific missing-notification errors. The common VDS return-code documentation states that no volume-arrival notification was received and suggests IVdsService::Refresh. VDS normally updates its cache automatically as notifications arrive, but a missing event can leave the caller waiting for an object view that never synchronizes through the normal notification path.
Why this state matters
Microsoft also warns that Refresh itself can trigger additional notifications and must not be called from inside IVdsAdviseSink::OnNotify, or the application can create a notification loop. The safe pattern is to finish the callback, mark the object view as suspect, and refresh from an independent control path before re-resolving the volume.
Diagnostic focus
- Record the operation and volume identity for which an arrival notification was expected.
- Exit the VDS notification callback before scheduling an explicit
Refresh. - After refresh, enumerate volumes and compare object IDs instead of testing only for a drive letter.
- If the warning repeats, inspect the provider notification pipeline rather than refreshing continuously.
Technical references
VDS common return codes · IVdsService::Refresh · IVdsAdviseSink::OnNotify · VDS_VOLUME_NOTIFICATION · IVdsService::Advise
Looking for a different code? Search another status or error code.