Resolve VSS Writer Errors Without Rebooting

How to Resolve VSS Writer Errors Without Rebooting

Scenarios

• Scenario 1: Failed VSS Writers

  Backups fail due to VSS writers in a failed state, and rebooting the server immediately is not feasible.

• Scenario 2: VSS Writers Not Started

  A writer is not running and needs to be started. Running vssadmin list writers will show only currently started writers.

• Scenario 3: Using VShadow for Windows Server 2003 or XP

  VSS is available in the Volume Shadow Copy Service 7.2 SDK, which can be downloaded from the Windows Download Center.

Troubleshooting Steps

Scenario 1: Failed VSS Writers

Step 1: Open Command Prompt as Administrator:

Start > Command Prompt > Right click > Run as Administrator

Step 2: Run the command to list VSS writers:

vssadmin list writers

If the command hangs or does not return output, the Volume Shadow Copy service or its dependencies may be in a bad state. Restart the service, or reboot the machine if it fails to restart.

Step 3: Take a screenshot or make a list of failed VSS writers.

Step 4: Find and restart the associated service for each failed VSS writer:

Use the table of associated services and their Display Names.

Step 5: Stop all VSS related services in services.msc.

Step 6: Rerun the command to confirm the status:

vssadmin list writers

The status should now read “Stable with No Error.”

Step 7: Attempt the backup again.

If the VSS writers fail again, a reboot of the machine may be required.