Some third-party applications that use external manifest files stop working after you install Windows server 2003 Service Pack 1

After you install Microsoft Windows Server 2003 Service Pack 1 (SP1) on a computer, some third-party applications stop working. This problem occurs if the applications depend on the components in external manifest files.

This problem occurs because the search priority of the side-by-side (SxS) manifest file is changed when you install Window Server 2003 SP1.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. 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

Windows Server 2003 SP1 must be installed on the computer.

Restart requirement

You must 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, x86-based versions

Windows Server 2003, x64-based versions

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

After you install the hotfix

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.

After you install the hotfix, you must create the PreferExternalManifest registry entry. To do this, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type PreferExternalManifest, and then press ENTER.
5. Right-click PreferExternalManifest, and then click Modify.
6. In the Edit DWORD Value dialog box, click Decimal under Base.
7. In the Value data box, type 1, and then click OK.
8. On the File menu, click Exit to close Registry Editor.

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 Server 2003 Service Pack 2.

Side-by-side assemblies let applications specify which version of a system DLL component or of a classic Component Object Model (COM) component to use. For example, if an Enterprise Services application relies on a particular version of a dependent assembly, the application can still use that version of the assembly even after newer versions have been installed.

The application manifest is an XML file that has information about where a DLL component is installed. The manifest file is used to create an activation context for the application. An activation context lets an application load a particular DLL version or COM object instance.