This hotfix makes some classes of writer (SQL, Active Directory, and others) less likely to experience time-out errors. In part, this hotfix is designed to improve the performance of the default shadow copy driver (Volsnap.sys) when there are high input/output levels.

This issue occurs because of a race condition in the Volume Shadow Copy Service driver (Volsnap.sys). When the volume size is being changed in the snapshot creation process, the race condition might be encountered. Resolution Hotfix information. A supported hotfix is available from Microsoft.

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

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.

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.

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.

When you use a backup application that uses VSS to back up files, you might notice an unexpected increase in disk space usage. This may occur in a corner case. When you examine the disk, you find that it is filled with undeleted snapshot files.

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.

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.

Assume that you have a computer that is running Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2. You use a backup application that uses the Windows Volume Shadow Copy feature to create snapshots and read files from the snapshots. In this situation, one or more corrupted files are found in the snapshots.