FIX: Merge modules can only be installed in the application folder in a Setup project in Visual Studio .NET 2003

This article has been archived. It is offered "as is" and will no longer be updated.
When you create a Microsoft Visual Studio .NET 2003 Setup project and you include the merge modules, you cannot change the target location for the merge modules. The merge modules can only be installed in the application folder.

Note In Microsoft Visual Studio .NET 2002, you can install the merge modules in any folder that you want.

This problem may also occur when you do an administrative or silent installation. In this scenario, the merge modules are copied to the root folder of the installation drive.

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio .NET 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


No prerequisites are required.

Restart requirement

You do not have to restart your 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 tool in Control Panel.
  Date         Time   Size     File name  --------------------------------------------------------------  25-Jun-2003  22:55  101,376  Vc_user_atl71_rtl_x86_---.msm  25-Jun-2003  22:55  201,728  Vc_user_crt71_rtl_x86_---.msm  25-Jun-2003  22:55  100,864  Vc_user_mfc71_loc_rtl_x86_---.msm  25-Jun-2003  22:59  919,552  Vc_user_mfc71_rtl_x86_---.msm  25-Jun-2003  22:55  151,040  Vc_user_stl71_rtl_x86_---.msm
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
The following merge module (.msm) files are included with Visual Studio .NET 2003:
  • ATL 7.1 (VC_User_ATL71_RTL_X86_---.msm )
  • Microsoft C Runtime Library 7.1 (VC_User_CRT71_RTL_X86_---.msm)
  • MFC 7.1 (Localized) (VC_User_MFC71_Loc_RTL_X86_---.msm)
  • MFC 7.1 (VC_User_MFC71_RTL_X86_---.msm)
  • Microsoft C++ Runtime Library 7.1 (VC_User_STL71_RTL_X86_---.msm)

Article ID: 823879 - Last Review: 01/17/2015 05:19:11 - Revision: 2.1

Microsoft Visual Studio .NET 2003 Professional Edition, Microsoft Visual Studio .NET 2003 Enterprise Architect, Microsoft Visual Studio .NET 2003 Enterprise Developer, Microsoft Visual Studio .NET 2003 Academic Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbvsnet2003presp1fix kbqfe kbbug kbfix KB823879