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. The hotfix also includes a larger initial size for the shadow copy storage area: 300 MB instead of 100 MB.

Xbox Support ... Xbox Support

This issue occurs because of a race condition in the Volume Shadow Copy driver (Volsnap.sys). This race condition may occur when the volume size changes during the snapshot creation process.

This issue occurs because the Volume Shadow Copy driver (Volsnap.sys) calculates the boundary of the free disk space that has copy-on-write protection incorrectly.

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.

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.

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.

Assume that you install a large hard disk on a computer that is running Windows 7 or Windows Server 2008 R2. For example, the size of the hard disk is larger than 2 terabytes. In this situation, there is a short delay before Windows starts. This issue occurs because the Microsoft Software Shadow Copy provider is being initialized.

Fixes an issue in which the cluster service takes longer than expected to bring a CSV volume online in Windows Server 2012 R2. This issue occurs when logs of VSS snapshots are accumulated by the Volsnap provider.

Consider the following scenario: You create a transportable VSS snapshot on a Windows Server 2008-based computer that has Active Directory-related roles installed. The VSS_VOLSNAP_ATTR_AUTORECOVER flag is not enabled. In this scenario, VSS snapshot creation may fail.