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"

On a computer running an operating system listed in the Applies To section, you create or extend a volume. 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, 32,768 MB, etc. (NOTE: 1 GB equals 1,024 MB).

You may experience one or more of the following problems

1. When you run the ChkDsk.exe utility on the volume in read-only mode (no switches) you receive an error message similar to one of the following:
   
   1. The Volume Bitmap is incorrect.
      Windows found problems with the file system.
   2. Error detected in index $I30 for file 5.
      <Number> index entries processed.
      Index verification completed.
   3. Errors found. CHKDSK cannot continue in read-only mode.
2. Restoring computer settings from System Restore point results in an unbootable operating system or corrupt files.
3. Restoring files from an effected volume using the "Previous Versions" tab may result in restored files being in a corrupted state.
4. When you use a backup application that leverages the Windows VSS Volume Shadow Copy feature to create snapshots during a backup, one or more files are found to be corrupt after a restore.

Note NTBackup, Windows Server Backup, System Center Data Protection Manager (DPM) or any third-party backup application’s backed-up data can be impacted. Please review the More Information Section on correcting this with Microsoft DPM or contact your third-party backup solution manufacturer to determine if they are using the Windows VSS Volume Shadow Copy feature to create their backups.

When a VSS Volume Shadow copy is invoked on an extended volume, the volume bitmap used to track cluster usage may not accurately reflect clusters that are in use by files that fall on an 8GB file system boundary. Consequently, data read or copied from a shadow copy may not accurately represent the file data. When the data is saved to the destination, it is saved in a corrupted state.

Microsoft has determined this to be a bug in the product and has corrected the issue in either a service pack or a hotfix depending upon the OS where the volume originated.

A hotfix is available for the following operating systems:

• Windows Server 2003 Service Pack 2 (SP2)
• 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

The fix is included in the following service packs:

• Windows 7 Service Pack 1 (SP1)
• Windows Server 2008 R2 Service Pack 1 (SP1)

Information about SP1 for the above can be found at: http://support.microsoft.com/kb/976932

Hotfix information

Important This hotfix has been re-released to address an issue in which the digital signature on files produced and signed by Microsoft will expire prematurely, as described in Microsoft Security Advisory 2749655.

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 Server 2003 Service Pack 2 (SP2)
• 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 Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base: 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: 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:

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 Server 2003 file information notes

• In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KB976329.cat) that is signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2003

For all supported x64-based versions of Windows Server 2003

For all supported IA-64-based versions of Windows Server 2003

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 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

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported IA-64-based versions of Windows Server 2008

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 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.1.760 0 . 20xxx	Windows 7 and Windows Server 2008 R2	RTM	LDR

• 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

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

For all supported IA-64-based versions of Windows Server 2008 R2

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: -
If you are using System Center Data Protection Manager (DPM) as your backup application, we recommend that you perform a manual RecoveryPoint with IntegrityCheck after the hotfix is applied. This will ensure that any new backups created by DPM will be consistent. See the following Technet article for details on creating a new RecoveryPoint: http://technet.microsoft.com/en-us/library/cc627335.aspx

Note: Any backups created prior to installing the fix and running the manual RecoveryPoint with an IntegrityCheck job may be corrupt if they meet the scenario criteria.

System Center Advisor rule information

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008

Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008

Additional files for all supported IA-64-based versions of Windows Server 2008

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

Additional files for all supported IA-64-based versions of Windows Server 2008 R2