This page is a repository of information to help troubleshoot issues related to Volume Shadow Copy Service. The information is collected from various sites on the Internet, with references (if available). Some of the information may suggest system related changes and/or registry changes. Please use at your own risk.
Symptoms of a Volume Shadow Copy Malfunction
- Very long (or seemingly indefinite) VSS snapshot generation time with intensive hard drive activity.
- VSS errors reported in the Event Viewer (click start and search Event Viewer in search box to open)
- VSS errors reported by Microsoft’s Volume Shadow Copy tool vssadmin
- VSS fails to create snapshots.
- Errors such as “The writer vetoed the shadow copy creation process”
VSS Repair Strategy #1 [1]
Reboot. For some reason, servers that haven’t been rebooted in a while cause VSS to malfunction. This resolves the issue many times.
VSS Repair Strategy #2 [1]
Open vssadmin from the command line (run cmd as administrator).
Enter vssadmin delete shadows /all to clean up any dead VSS snapshots. Some defect systems accumulate hundreds of VSS snapshots that persist in the system and cause Windows to become unresponsive.
Enter vssadmin list writers and check for errors. If you receive any errors for one VSS writer, you may need to fix that particular VSS writer. It is common to receive writer errors caused by Microsoft’s Virtual Server 2005 VSS writer.
If you see a VSS writer error, try the following:
- Restart the services: COM+ System Application Service, Distributed Transaction Coordinator Service, and Volume Shadow Copy Service and also restart the affected VSS writer service, for example Virtual Server 2005 VSS writer or Hyper-V VSS writer.
- Check the Event Viewer for any additional error information logged by that VSS writer. Run again
vssadmin list writersto check if the above resolved the problem.
VSS Repair Strategy #3 [1]
Check if the Volume Shadow Copy service is started, try restarting the service:
- Click ‘Start’, and then click ‘Control Panel’. Click ‘Administrative Tools’, and then double-click the ‘Services’ snap-in.
- Check for ‘Volume Shadow Copy’.
Also, restart the following services on the affected machine:
- COM+ Event System Service
- COM+ System Application Service
- Remote Procedure Call (PRC) Service
- MS Software Shadow Copy Provider Service
VSS Repair Strategy #4 [1]
Uninstall all backup software on your computer, including Windows Backup if it’s installed. After all other backup tools have been uninstalled, open the Registry Editor (regedit) as administrator and check the following branch: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Providers
Underneath that key you should only find Microsoft Software Shadow Copy Provider 1.0 and no other VSS writer. If you do find another, it may be a residue registry entry of a previous backup software installation. You can save the entry by exporting the entire registry to a file (right click and select Export) and then it’s safe to delete the entire branch entry underneath: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Provider. Then reboot and try again running vssadmin list writers to confirm the problem has been resolved.
VSS Repair Strategy #5 [1]
On some systems, the command vssadmin delete shadows isn’t available. You need to delete old shadows using:
vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=300MB
300MB is usually the smallest amount you can specify and will effectively delete any existing VSS snapshots on your system. If you don’t get any VSS writer errors when using vssadmin list writers but the system isn’t able to create a new VSS snapshot (and you have deleted all existing snapshots), then you may have to actually increase the max shadow storage size on your system. Use the previous command with a greater number, such as 10GB:
vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=10GB
Note that it is also possible to allocate shadow copy storage space on a different drive, as along as it’s local:
vssadmin Resize ShadowStorage /For=C: /On=X: /MaxSize=200GB
VSS Repair Strategy #6 [1]
You can try to re-register all VSS and COM+ components by running the following commands from the command prompt as administrator. These instructions for 32-bit systems:
cd /d %windir%\system32 Net stop vss Net stop swprv regsvr32 ole32.dll regsvr32 vss_ps.dll Vssvc /Register regsvr32 /i swprv.dll regsvr32 /i eventcls.dll regsvr32 es.dll regsvr32 stdprov.dll regsvr32 vssui.dll regsvr32 msxml.dll regsvr32 msxml3.dll regsvr32 msxml4.dll regsvr32 Vssapi.dll regsvr32 Vssui.dll net start vss net start swprv
Execute these instructions for 64-bit systems:
Net stop vss Net stop swprv regsvr32.exe /i %windir%\system32\eventcls.dll regsvr32.exe /i %windir%\system32\swprv.dll regsvr32.exe %windir%\system32\vssui.dll regsvr32.exe %windir%\SysWOW64\vss_ps.dll regsvr32.exe %windir%\SysWOW64\msxml.dll regsvr32.exe %windir%\SysWOW64\msxml2.dll regsvr32.exe %windir%\SysWOW64\msxml3.dll regsvr32.exe %windir%\SysWOW64\msxml4.dll regsvr32.exe %windir%\SysWOW64\ole32.dll regsvr32.exe %windir%\SysWOW64\oleaut32.dll regsvr32.exe %windir%\SysWOW64\es.dll regsvr32.exe %windir%\SysWOW64\comsvcs.dll vssvc /register net start swprv net start vss
VSS Repair Strategy #7 [1]
If the PC or server you are using is a virtual machine host, you need to install the latest VMware Tools (for VMware), Virtual Machine Additions (Virtual Server), or Hyper-V Integration Services (for Hyper-V and Windows Server 2008) on each virtual machine. Try updating them if you have them installed already. Outdated integration services can cause various VSS errors.
VSS Repair Strategy #8 [1]
Your computer may have a corrupt COM+ subscription information. Open the registry editor (regedit) and navigate to:
HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}
Then delete the Subscriptions key and reboot the machine. A subsequent call in the command prompt should show no more errors: vssadmin list writers This VSS repair strategy appears to work well when the System Writer is reporting an error. The Event Viewer may be reporting this or a similar error:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {34162f4c-59ff-468e-848d-cb4b3d8dd7dc}
VSS Repair Strategy #9 (VSS Error Code 0x800423f3) [1]
If the VSS error code 0x800423f3 is reported, the reason is a corrupt state of WMI (wmiutils.dll). This may happen if a registry cleaner was used or a third-party application was uninstalled incorrectly. What you need to do is re-register wmiutils.dll and then restart the WMI service.
In the command prompt, execute the following three lines (note that stopping the WMI service does NOT stop VMs, it only stops the management service):
net stop winmgmt regsvr32 wmiutils.dll net start winmgmt
After that you should start up the Hyper-V Management Service again if needed.
Another cause for this error: You may need to update your Hyper-V virtual machine integration services inside of each VM when you come across this error. See http://technet.microsoft.com/en-us/library/dd582376(v=WS.10).aspx. Check the vmguest.iso date / time you have in your system folder. You may have different versions of the Hyper-V Integration Services CD on your system. There have been bug reports indicating that Hyper-V uses the wrong ISO file when the VM Action menu is used to install the Integration Services. Try attaching the ISO manually and use the latest vmguest.iso in your system folder.
On Windows Server 2008 (not R2), also check this hotfix: http://support.microsoft.com/kb/971394
VSS Writers
| VSS Writer | Service Name | Service Display Name |
| ASR Writer | VSS | Volume Shadow Copy |
| BITS Writer | BITS | Background Intelligent Transfer Service |
| COM+ REGDB Writer | VSS | Volume Shadow Copy |
| DFS Replication service writer | DFSR | DFS Replication |
| DHCP Jet Writer | DHCPServer | DHCP Server |
| FRS Writer | NtFrs | File Replication |
| FSRM writer | srmsvc | File Server Resource Manager |
| IIS Config Writer | AppHostSvc | Application Host Helper Service |
| IIS Metabase Writer | IISADMIN | IIS Admin Service |
| Microsoft Exchange Writer | MSExchangeIS | Microsoft Exchange Information Store |
| Microsoft Hyper-V VSS Writer | vmms | Hyper-V Virtual Machine Management |
| NTDS | NTDS | Active Directory Domain Services |
| OSearch VSS Writer | OSearch | Office SharePoint Server Search |
| OSearch14 VSS Writer | OSearch14 | SharePoint Server Search 14 |
| Registry Writer | VSS | Volume Shadow Copy |
| Shadow Copy Optimization Writer | VSS | Volume Shadow Copy |
| SPSearch VSS Writer | SPSearch | Windows SharePoint Services Search |
| SPSearch4 VSS Writer | SPSearch4 | SharePoint Foundation Search V4 |
| SqlServerWriter | SQLWriter | SQL Server VSS Writer |
| System Writer | CryptSvc | Cryptographic Services |
| TermServLicensing | TermServLicensing | Remote Desktop Licensing |
| WINS Jet Writer | WINS | Windows Internet Name Service |
| WMI Writer | Winmgmt | Windows Management Instrumentation |
Footnotes
1. “Volume Shadow Copy Service (VSS) Troubleshooting”, http://www.tomahawkbackup.com/faq/index.php?action=artikel&cat=8&id=117&artlang=en