Binary files are not updated by the Windows Installer service

Consider the following scenario:

• You install Microsoft Windows Installer 4.5 on a computer that is running Windows Server 2003 Service Pack 2 (SP2).
• You create a junction point in a folder that is located on the computer. The junction point points to another folder on a different volume. For example, you create a junction point in the C:\temp folder, and the junction point points to the E:\test folder.
• You install an application in the folder that has the junction point.
• You save some binary files of the application in the destination folder of the junction point.
• You try to use a Microsoft Windows Installer package (.msi file) that updates the binary files when they are being used.

In this scenario, the update process for the binary files is pending until the next restart. However, the binary files are not updated after the next restart.

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.

Prerequisites

To apply this hotfix, your computer must be running Windows Server 2003 Service Pack 2 (SP2).

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:

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 (KBnumber.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 and of Windows XP Professional x64 Edition

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

Workaround for Windows Server 2003

To work around this issue, follow these steps when the update process for the binary files is pending for the next restart:

1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Open the following registry key:
   
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
4. In the right pane, click PendingFileRenameOperations.
5. On the Edit menu, click Modify.
6. Modify the value by adding an exclamation point (!). For example:
   
   Original value: \??\d:\folder1\TMB6.tmp \??\d:\folder1\binary.dll
   Modified value: \??\d:\folder1\TMB6.tmp !\??\d:\folder1\binary.dll
7. Click OK, and then exit Registry Editor.

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

For more informationabout how to create NTFS junction points and about how to manipulate NTFS junction points, click the following article number to view the article in the Microsoft Knowledge Base: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: