The Fc.exe command does not work correctly in Windows Vista or in Windows Server 2008 when the two files that you are comparing have the TAB or SPACE character around the 128th byte in a character string

On a computer that is running Windows Vista or Windows Server 2008, you use the Fc.exe command to compare two files. However, if the two files have the TAB character or the SPACE character anywhere in the 7 bytes that come before the 128th byte in a character string, the Fc.exe command does not work correctly.

Currently, the Fc.exe command reads 127 bytes in a character string at one time. By default, the Fc.exe command expands the TAB character into spaces before the command compares two files that contain the TAB character. The command may expand the TAB character into as many as 8 spaces, depending on where the TAB character is located in the string. For example, if the TAB character occurs at index 120, 121, 122, 123, 124, 125, or 126, the TAB character should be expanded to 7 spaces, 6 spaces, 5 spaces, 4 spaces, 3 spaces, 2 spaces, or 1 space, respectively. However, this behavior causes the Fc.exe command to work incorrectly.

After you apply this hotfix, the FC.exe command will read 128 bytes every time that it runs. Because 128 is multiple of 8, this resolves the problem.

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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

No prerequisites are required.

Restart requirement

You do not 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 Vista and Windows Server 2008 file information notes

• The files that apply to a specific product, milestone (RTM, SPn) can be identified by examining the file version numbers as shown in the following table:

  Version	Product	Milestone	Service branch
  6.0.600 0. 20 xxx	Windows	RTM	LDR
  6.0.600 1. 22 xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	LDR

• Service Pack 1 is integrated into 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 MUM files (.mum) installed for each environment are listed separately. 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 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

Additional file information for Windows Server 2008 and for Windows Vista

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

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

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

To work around this problem, run the Fc.exe command together with the /b (binary) switch.

Note Binary mode does not show the location of the differences between the two files.

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

Fc.exe is a command that compares two files or two sets of files and then displays the differences between them.