After you sync a file in Windows Vista or in Windows Server 2008, the Date Modified time for the destination file may be updated to the current time

After you sync a file in Windows Vista or in Windows Server 2008, the Date Modified time for the destination file may be updated to the current time. This behavior may cause a re-sync of the file attributes and may cause the Windows Search service to re-index the whole file.

For example, you click Always Available Offline to pin a network folder in Windows Vista. You visit the folder, and then create a file in the folder. You select Work Offline for the folder, and then replace the file. When you sync the file, the file is synced from the client to the server correctly. However, when you sync the file again, the file is synced from the server to the client again, even though no content changed during this period.

This problem occurs because Client-Side Caching (CSC) uses the ReplaceFile function to sync files in Windows Vista. When CSC replaces a file, two time stamps are copied from the source file. One time stamp is passed from the previous destination file, and the Date Modified time is updated to the current time. This causes CSC to sync attributes from the server on the next sync.

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

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 a previously released hotfix.

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 and 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.6000.20xxx	Windows	RTM	LDR
  6.0.6001.22xxx	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 (.manifest) files and the MUM (.mum) files that are installed for each environment are listed separately. The 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, whose attributes are not listed, are signed by using a Microsoft digital signature.

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

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

For help with Windows Search problems in Windows Vista, visit the following Microsoft web page: For more information about the ReplaceFile function, visit the following Web site:

Additional file information for Windows Vista and Windows Server 2008

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

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

Additional files for all supported Itanium-Based versions of Windows Server 2008