A file's time stamp may be incorrectly set when a program moves a file to a file server in Windows Server 2003

When a program moves a file to a local file share, the file's time stamp may be set to the current time. You expect the time stamp to be set to the time that the SetFileTime function specified.

Files are most frequently moved in this way by an installer program.

For example, this problem may occur when a Microsoft Windows Installer package installs files to a local shared folder that is accessed by using a Universal Naming Convention (UNC) path.

This problem occurs because of a problem with the Shadow I/O feature in the Windows redirector. Because of this problem, modified data is updated before the file content is written. When the file content is written, the time stamp is reset.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To work around this problem, add the DisableShadowLoopback entry to the following registry key:Give this entry the "REG_DWORD" type and a value of 1.

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

For more information about Windows Installer, visit the following Microsoft Web site: