If you see a VSS error, try the following:
It is quite common to receive multiple errors from several related services, such as “VolSnap” and “Disk”. If you receive errors for one writer, you may need to fix that particular service. Some defect systems accumulate hundreds of VSS snapshots that persist in the system and cause Windows to become unresponsive.Įnter “vssadmin list writers” and check for errors. Open “vssadmin from the command line (run cmd as administrator).Įnter “vssadmin delete shadows /all” to clean up any dead / orphaned shadows. Rebooting will eliminate VSS problems caused by transient VSS errors. As all Microsoft veterans know, you need to reboot regularly as a preventive and cleanup For some reason, servers that haven’t been rebooted in a while cause VSS to malfunction. Once you know the exact cause, the fix is usually trivial.
If you haven’t done this before, it’s a great opportunity to approach it now since the Event Viewer system is where Windows logs almost everything. This is the most crucial step in fixing the problem: dig through the Event Viewer logs. In addition, download our VssDiag tool which helps you find VSS error entries. Step #1: The First Thing To Do Before Attempting FixesĬheck Windows Event Viewer logs and several sub-logs this will save you hours if not days of work! Run VSS doctor, if this doesn't help try to following.
0 kommentar(er)
