Article ID: 976329 - Last Review: April 14, 2010 - Revision: 2.0
Error message when you run the ChkDsk.exe utility in read-only mode on a Windows-based computer: "The Volume Bitmap is incorrect" or "Error detected in index $I30 for file 5"
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.
Consider the following scenario on a computer that is running Windows Vista or Windows Server 2008:
You create a new volume on the computer. The size of the volume is a multiple of 8 gigabytes (GB). For example, the size of the volume is 8,192 megabyte (MB), 16,384 MB, or 32,768 MB.
Note 1 GB equals 1,024 MB.
You extend the size of the volume by using the Disk Management tool or by using the Diskpart.exe utility.
You run the ChkDsk.exe utility on the volume in read-only mode.
In this scenario, you receive the following error message:
The Volume Bitmap is incorrect. Windows found problems with the file system.
Or, consider the following scenario on a computer that is running Windows 7 or Windows Server 2008 R2:
You create a new volume on the computer. The size of the volume is a multiple of 8 GB.
You extend the size of the volume by multiple of 8 GB, by using the Disk Management tool or by using the Diskpart.exe utility.
You run the ChkDsk.exe utility on the volume in read-only mode.
In this scenario, you receive the an error message that resembles the following:
Error detected in index $I30 for file 5. <Number> index entries processed.
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
Additionally, if you restore data that was backed up on the system, the restore operation may not finish successfully.
Note If you do not specify a switch when you run the ChkDsk.exe utility, the ChkDsk.exe utility runs in read-only mode.
When the ChkDsk.exe utility runs in read-only mode, the ChkDsk.exe utility uses the Volsnap.sys driver to read the volume bitmap. However, the Volsnap.sys driver incorrectly reports that the volume bitmap is incorrect.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might 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.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, your computer must be running one of the following Windows operating systems:
Windows Vista Service Pack 1 (SP1)
Windows Vista Service Pack 2 (SP2)
Windows Server 2008
Windows Server 2008 Service Pack 2 (SP2)
Windows 7
Windows Server 2008 R2
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791
(http://support.microsoft.com/kb/935791/
)
How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849
(http://support.microsoft.com/kb/968849/
)
How to obtain the latest service pack for Windows Server 2008
Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both of these operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, SR_Level (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
SR_Level
Service branch
6.0.600
0
.
20xxx
Windows Vista
RTM
LDR
6.0.600
1
.
22xxx
Windows Vista and Windows Server 2008
SP1
LDR
6.0.600
2
.
22xxx
Windows Vista and Windows Server 2008
SP2
LDR
Service Pack 1 is integrated into the 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.
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, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Volsnap.sys
6.0.6001.22550
225,864
27-Oct-2009
13:42
x86
Volsnap.sys
6.0.6002.22252
225,848
27-Oct-2009
13:30
x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Volsnap.sys
6.0.6001.22550
268,360
27-Oct-2009
14:13
x64
Volsnap.sys
6.0.6002.22252
267,832
27-Oct-2009
13:39
x64
For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Volsnap.sys
6.0.6001.22550
625,736
27-Oct-2009
13:37
IA-64
Volsnap.sys
6.0.6002.22252
625,720
27-Oct-2009
13:30
IA-64
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
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 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Volsnap.sys
6.1.7600.20659
245,128
04-Mar-2010
07:28
x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Volsnap.sys
6.1.7600.20659
295,312
04-Mar-2010
08:08
x64
For all supported IA-64-based versions of Windows Server 2008 R2