| Previous | Next |
| VDS_S_VSS_FLUSH_AND_HOLD_WRITES | VDS_S_FS_LOCK |
VDS_S_VSS_RELEASE_WRITES
This warning is the release-side counterpart to flush-and-hold failure. In the VSS provider sequence, VolSnap holds write IRPs while providers commit snapshots and then VSS releases the pending writes immediately after the last provider commit returns. Microsoft documents that the flush-and-hold window is tightly bounded because application and file-system write availability is affected.
Why this state matters
A release failure is therefore not equivalent to “snapshot provider returned an error” and should be treated as a write-resumption boundary. Preserve whether provider commit completed, whether the snapshot set was accepted or aborted, and which volumes were under the common hold. Do not declare the system recovered merely because subsequent application writes appear to work; verify the final VSS result and relevant VolSnap/VSS events.
Diagnostic focus
- Capture the final provider commit outcome and the VSS snapshot-set status before interpreting the warning.
- Collect VSS and VolSnap events around the exact release interval for all held volumes.
- Verify that write I/O resumed normally and that the requester did not accept an aborted or incomplete snapshot set.
- Distinguish release failure from the earlier inability to flush and hold writes; they occur at opposite sides of the critical window.
Technical references
Shadow Copy Creation for Providers · Volume Shadow Copy Service · MS-VDS error codes · VDS common return codes · IVdsService
Looking for a different code? Search another status or error code.