System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
On a computer that is running Windows Server 2008 or Windows Vista, you configure a diff area on a volume. Additionally, you specify that snapshots will be created on another volume.
You create copy-on-write snapshots for a volume.
You restore these snapshots in order, from the latest snapshot to the earliest snapshot.
In this scenario, all earlier snapshots are deleted unexpectedly after the second snapshot is restored. Additionally, the following Error event is logged in the System log:
Event ID: 29 Source: volsnap Type: Error Description: The shadow copies of volume <drive letter> were aborted during detection.
When the Volume Shadow Copy driver (Volsnap.sys) reverts a volume to a selected snapshot, the snapshot that comes immediately before the selected snapshot becomes growable. Therefore, I/O requests for the volume will be updated in the diff area. However, the Volsnap.sys driver does not manage this process correctly. This behavior results in a corrupted diff area for the snapshots. Therefore, the remaining snapshots are deleted.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
To apply this hotfix, you must have one of the following operating systems installed on the computer.
Windows Vista Service Pack 1 (SP1)
Windows Vista Service Pack 2 (SP2)
Windows Server 2008
Windows Server 2008 Service Pack 2 (SP2)
Restart requirement
You have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
Registry information
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Vista and Windows Server 2008 file information notes
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.0.6000.16xxx
Windows Vista
RTM
GDR
6.0.6000.20xxx
Windows Vista
RTM
LDR
6.0.6001.18xxx
Windows Vista SP1 and Windows Server 2008 SP1
SP1
GDR
6.0.6001.22xxx
Windows Vista SP1and Windows Server 2008 SP1
SP1
LDR
6.0.6002.18xxx
Windows Vista SP2 and Windows Server 2008 SP2
SP2
GDR
6.0.6002.22xxx
Windows Vista SP2 and Windows Server 2008 SP2
SP2
LDR
Service Pack 1 is integrated into the original release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008, of Windows Server 2008 SP2, of Windows Vista SP1, and of Windows Vista SP2
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Volsnap.sys
6.0.6001.22527
225,352
18-Sep-2009
23:46
x86
Volume.inf
Not Applicable
2,062
18-Sep-2009
18:04
Not Applicable
Volsnap.sys
6.0.6002.22229
225,336
18-Sep-2009
13:23
x86
Volume.inf
Not Applicable
2,062
18-Sep-2009
07:43
Not Applicable
For all supported x64-based versions of Windows Server 2008, of Windows Server 2008 SP2, of Windows Vista SP1, and of Windows Vista SP2
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Volsnap.sys
6.0.6001.22527
267,848
19-Sep-2009
00:46
x64
Volume.inf
Not Applicable
2,082
18-Sep-2009
18:53
Not Applicable
Volsnap.sys
6.0.6002.22229
267,336
18-Sep-2009
12:59
x64
Volume.inf
Not Applicable
2,082
18-Sep-2009
07:43
Not Applicable
For all supported IA-64-based versions of Windows Server 2008 and of Windows Server 2008 SP2
Additional file information for Windows Server 2008 and for Windows Vista
Additional files for all supported x86-based versions of Windows Server 2008, of Windows Server 2008 SP2, of Windows Vista SP1, and of Windows Vista SP2
Additional files for all supported x64-based versions of Windows Server 2008, of Windows Server 2008 SP2, of Windows Vista SP1, and of Windows Vista SP2