To diagnose the Volume Shadow Copy service writer problem, run the vssadmin command immediately after the backup failure: Click Start, and then click. Run. Type vssadmin list writers. This command lists the Volume Shadow Copy service writers and the current state of each writer.

You perform a backup or run the vssadmin list writers command on one of the cluster nodes. Note For more information about this command, see vssadmin list writers. In this scenario, the backup or list writer operation may log the following error in the Application log on all cluster nodes other than the node that you ran the command on: Source: VSS

Symptoms. When you run the vssadmin list writers command in Windows Server 2008 R2, no VSS writers are listed. Additionally, the following events are logged in the Application log: Log Name: Application. Source: VSS.

Note You can use the vssadmin list shadows command to determine whether the problem is caused by undeleted snapshot files. Cause. This issue occurs because VSS encounters a race condition that prevents the snapshot deletion feature from deleting all snapshots. Resolution Hotfix information

Change the allocation by using the Vssadmin command, syntax: vssadmin resize shadowstorage /On=C: /For=C: /Maxsize=1G (where Maxsize=the amount of disk space you've allocated to System Restore points, you should increase it larger) Then reboot your computer. Restore point deletion can also be caused by the following:

You run the Vssadmin list writers command to view the writers that are subscribed to the Volume Shadow Copy Service (VSS). You use Windows Server Backup to try to back up the system. In this scenario, System Writer is missing, and the backup fails. Resolution. Hotfix information. A supported hotfix is available from Microsoft Support.

Cause. This issue occurs because a worker thread incorrectly maintains a slim reader/writer (SRW) lock when the worker thread is in sleep state. Therefore, the listener thread cannot obtain the lock to push the work item into the queue. Resolution. To resolve this issue in Windows Server 2012 R2, install update rollup 2887595.

Fixes an issue in which the trigger of a shadow copy task is not set as expected in the task scheduler on a cluster that is running Windows Server 2012 R2 or Windows Server 2012. This issue occurs when the shadow copy storage is set on another share disk.

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool. (C) Copyright 2001 Microsoft Corp. Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {0df8b3f5-59ee-4185-983c-f35f16488e17} State: [9] Failed. Last error: No error. Writer name: 'COM+ REGDB Writer'

Run the System File Checker tool (SFC.exe) To do this, follow these steps: Open an elevated command prompt. To do this, do the following as your appropriate: If you are running Windows 10, Windows 8.1 or Windows 8, first run the inbox Deployment Image Servicing and Management (DISM) tool prior to running the System File Checker.