| Previous | Next |
| VDS_S_RESYNC_NOTIFICATION_TASK_FAILED | VDS_S_VSS_RELEASE_WRITES |
VDS_S_VSS_FLUSH_AND_HOLD_WRITES
This warning belongs to the VSS point-in-time write-quiescing mechanism. Microsoft documents that VSS issues IOCTL_VOLSNAP_FLUSH_AND_HOLD_WRITES to the volumes in a snapshot set, flushes supported file systems, and causes VolSnap to hold write IRPs while providers commit the shadow copy. The hold window is deliberately time-critical.
Why this state matters
The status should not be diagnosed as a generic “disk flush failed.” Preserve the VSS snapshot-set/provider context and determine whether the failure occurred while quiescing one source volume. During the hold phase, delays can affect all involved volumes, and VSS cancels the hold if the release does not arrive within its documented time window. Writer state, provider commit latency, and storage errors belong in the same timeline.
Diagnostic focus
- Identify the VSS snapshot set, source volumes, and provider participating when the flush/hold phase failed.
- Collect VSS, VolSnap, and storage events from the same commit window.
- Check for provider work that ran too long inside the time-critical CommitSnapshots phase.
- Do not treat this as confirmation that the snapshot exists; verify the final VSS/requester result and release state.
Technical references
Shadow Copy Creation for Providers · Volume Shadow Copy Service · MS-VDS error codes · VDS_NOTIFICATION · VDS common return codes
Looking for a different code? Search another status or error code.