Guess there are two of us in the same boat. The culprit is the MFC msm. If I add the 9.0.21022.8 MFC merge module (which is 1.5MB in size) to my build I go from a 2.7MB msi to a 4.3 MB msi - seems like good math. But if I add the more recent 9.0.30729.4148 MFC merge module (which is 4MB in size) to my build I go from a 2.7MB msi to a 9.8MB msi. Crazy. -mick ... View more

I'd like to know how anyone is using the Visual C++ 9.0.30729.4148 merge modules at all especially if developing for both x86 and x64. From what I see, the InstallShield "Redistributables view" gets its description of the merge modules from its cross reference modules.ini file or, if not found there, from the "Subject" contained in the msm file's "Summary Information Stream". The problem is that all the Visual C++ 9.0 merge modules show the architecture as being "x86" and thus it becomes sheer luck as to what you really select. This appears to be the same situation as to what was behind a previous hotfix Q113765 Am I missing some update to support the Visual C++ 9.0.30729.4148 merge modules? I'm using IS 2010 SP1. To get me going using both the x86 and x64 versions of the newer files, I added the following to modules.ini and things are now working but I feel like I'm hacking: policy_9_0_Microsoft_VC90_ATL_x86.36F772C3_DEA7_32C0_AD18_338903366207:0=Visual C++ 9.0.30729.4148 ATL (x86) WinSXS MSM policy_9_0_Microsoft_VC90_ATL_x64.5D0F2E32_BA63_3326_AD42_DD69D5B3E05D:0=Visual C++ 9.0.30729.4148 ATL (x64) WinSXS MSM policy_9_0_Microsoft_VC90_CRT_x86.EB5BA578_FF7F_3863_8E53_7A003222B7FC:0=Visual C++ 9.0.30729.4148 CRT (x86) WinSXS MSM policy_9_0_Microsoft_VC90_CRT_x64.F88F7F82_F6E0_309C_981C_800644564D24:0=Visual C++ 9.0.30729.4148 CRT (x64) WinSXS MSM policy_9_0_Microsoft_VC90_MFC_x86.71F730CE_8B24_3BC2_83EA_36396DE29B9E:0=Visual C++ 9.0.30729.4148 MFC (x86) WinSXS MSM policy_9_0_Microsoft_VC90_MFC_x64.C8ECA3D5_581C_3816_B0A1_3556BB7418CE:0=Visual C++ 9.0.30729.4148 MFC (x64) WinSXS MSM policy_9_0_Microsoft_VC90_MFCLOC_x86.036BF802_B20B_38B9_9A44_2CF929804212:0=Visual C++ 9.0.30729.4148 MFCLOC (x86) WinSXS MSM policy_9_0_Microsoft_VC90_MFCLOC_x64.0FF966D0_8D3B_384F_A9DF_616A29748413:0=Visual C++ 9.0.30729.4148 MFCLOC (x64) WinSXS MSM policy_9_0_Microsoft_VC90_OpenMP_x86.EB6C11E5_449C_3BA3_9086_80B18BCFF947:0=Visual C++ 9.0.30729.4148 OpenMP (x86) WinSXS MSM policy_9_0_Microsoft_VC90_OpenMP_x64.8B5E3873_2E2B_3803_92AE_0E3F6E368DD5:0=Visual C++ 9.0.30729.4148 OpenMP (x64) WinSXS MSM Microsoft_VC90_ATL_x86.0901F145_82C9_3BF6_A91B_31F6791950EA:0=Visual C++ 9.0.30729.4148 ATL.Policy (x86) WinSXS MSM Microsoft_VC90_ATL_x64.69B1CE59_83A2_3B04_8B0C_F929BA23DD66:0=Visual C++ 9.0.30729.4148 ATL.Policy (x64) WinSXS MSM Microsoft_VC90_CRT_x86.AA2EBBCC_4E3B_3442_865E_7BB3E9F45F0C:0=Visual C++ 9.0.30729.4148 CRT.Policy (x86) WinSXS MSM Microsoft_VC90_CRT_x64.DD7E30AD_4555_3131_8F48_1849E9DBC229:0=Visual C++ 9.0.30729.4148 CRT.Policy (x64) WinSXS MSM Microsoft_VC90_MFC_x86.1B1242B0_08E9_3D59_826D_ADAA4BB763B5:0=Visual C++ 9.0.30729.4148 MFC.Policy (x86) WinSXS MSM Microsoft_VC90_MFC_x64.1D1BABF3_B608_379B_8FD1_BDA1F6098DD6:0=Visual C++ 9.0.30729.4148 MFC.Policy (x64) WinSXS MSM Microsoft_VC90_MFCLOC_x86.1D3B0A01_2635_3323_932D_3D66D5C4B0FD:0=Visual C++ 9.0.30729.4148 MFCLOC.Policy (x86) WinSXS MSM Microsoft_VC90_MFCLOC_x64.2CD3AE3F_43DE_3351_B00B_6EF53A377CA6:0=Visual C++ 9.0.30729.4148 MFCLOC.Policy (x64) WinSXS MSM Microsoft_VC90_OpenMP_x86.A0B0BCE9_2994_36F2_BE66_D23C884372E8:0=Visual C++ 9.0.30729.4148 OpenMP.Policy (x86) WinSXS MSM Microsoft_VC90_OpenMP_x64.996FE33F_0401_3E3C_9CD6_4EC749D14C77:0=Visual C++ 9.0.30729.4148 OpenMP.Policy (x64) WinSXS MSM ... View more

I'm in the same boat. Very frustrating... Whats weird is that it it does not occur with msi projects, only installscript projects. ... View more