The Chkdsk.exe tool cannot detect bad clusters or bad sectors on a Windows Server 2003-based computer when the size of a compressed file is larger than 4 gigabytes (GB)

When you scan a volume on a Windows Server 2003-based computer by using the chkdsk /r command, you receive a status message that resembles the following:This status message incorrectly indicates that Windows replaced bad clusters. This status message can occur if the following conditions are true:

• The current volume has a compressed file.
• The size of the compressed file is larger than 4 gigabytes (GB).

During a surface scan, the Chkdsk.exe tool tries to read the contents of all compressed files on the volume. A failure to read one or more clusters in a file will indicate that a failure occurred when the Chkdsk.exe tool read the data on the volume.

If the Chkdsk.exe tool encounters a compressed file that is larger than 4 GB, an arithmetic error occurs that stops the scan of the 4-GB compressed file. When this issue occurs, the Chkdsk.exe tool assumes that an error occurred when the Chkdsk.exe tool tried to read the data on the volume.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

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 this specific problem. 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

This hotfix requires that Microsoft Windows Server 2003 with Service Pack 1 (SP1) or with a later service pack is installed on the computer.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 Server 2003 with Service Pack 1 (SP1), x86-based versions

Windows Server 2003 with Service Pack 2 (SP2), x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003 with Service Pack 2 (SP2), x64-based versions

Windows Server 2003 with Service Pack 1 (SP1), Itanium-based versions

Windows Server 2003 with Service Pack 2 (SP2), Itanium-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Vista Service Pack 1.

After you install this hotfix, and you run the chkdsk /r command, you receive a message that resembles the following:For help with common system maintenance tasks in Windows Vista, visit the following Microsoft Web page: