This issue occurs because the Volsnap.sys driver spends too much time marking available space on the volume when holding a spinlock. Resolution. This hotfix is also available at Microsoft Update Catalog. Hotfix information. A supported hotfix is available from Microsoft.

To resolve this problem, perform the System File Checker scan in safe mode, and make sure that the PendingDeletes and PendingRenames folders exist under %WinDir% \WinSxS\Temp. Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log %WinDir% \Logs\CBS\CBS.log.

On a computer that is running Windows Server 2008 or Windows Vista, you create a copy-on-write snapshot for a volume. On the volume that stores the copy-on-write snapshot, some other snapshots are deleted. In this scenario, the copy-on-write snapshot may become corrupted. A supported hotfix is available from Microsoft.

Fixes an issue in which the snapshot protection mode cannot be disabled on a Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2-based server.

On a computer that is running Windows Server 2008 R2 or Windows 7, you create two volumes on some dynamic disks. You configure one volume to store the shadow copy storage area (also known as "diff area") of the other volume. You enable the Snapshot Protection mode on both volumes. You create snapshots at set intervals.

You may also experience a problem in the Volsnap.sys driver that causes shadow copy deletion when there is a high level of input/output, especially when the disk write cache is disabled (for example, on a domain controller computer).

Discusses that you receive a "The last backup did not complete successfully" error message when you try to back up a Windows 8 system. Provides a resolution and a workaround.

Fixes an issue that occurs when you create some files and delete some older snapshots in parallel in Windows 8.1, Windows Server 2012 R2, Windows 8 or Windows Server 2012.

This issue occurs because the Volsnap.sys driver file cannot create the difference area on a volume that is larger than 16 terabytes (TB) during concurrent volume shadow copy operations. Resolution Hotfix information. A supported hotfix is available from Microsoft.

This issue occurs because of a race condition in the mounting of volumes after a failover. In this race condition, NTFS uses a target device object that is not a volsnap device object. Therefore, the Flush & Hold Writes operations are not sent to the Volsnap.sys driver. Resolution Hotfix information. A supported hotfix is available from Microsoft.