Visual C++ 2009 SP1 Problem

[Googoohead]

We're trying to nail down a serious problem and thought I would try looking for some help here...

We using the Visual C++ 2009 SP1 with the ATL patch. When we install our product then run it, our application crashes. We thing, but are not sure if it's related to the WinSxS files.

Installshield included .cat and .policy files for each of the ATL/MFC merge modules. This was fine for the 9.0.30729.1 merge modules but don't work for the 9.0.30729.4148 merge modules.

We decided to directly grab the merger modules and skip the .cat & .policy files.

Thanks!

[hsteinbeck]

I too am having problems with VC90.MFC merge module version 9.0.30729.4148. Since using this package my installations work when installing for the first time but when I do a major upgrade an ocx file that I register fails because it cannot find the VC90.MFC library. The version it is looking for is 9.0.21022.8 which is defined in the manifest of the ocx file. Clearly it should be backwards compatible but something in the merge module breaks this functionality on a Major upgrade.
If I edit the ocx library in Visual Studio and alter the MFC version in the manifest to 9.0.30729.4148 my ocx file can be registered on the system where it would fail before.

I suspect something is jacked up in the merge modules that were released with that VC++ security update:
http://support.microsoft.com/kb/973924

[cbragg]

I had similar problems and managed to resolve them just before you posted too 😄 the post is here:

http://community.acresso.com/showthread.php?p=445031#post445031

Hope my findings help you too

[hsteinbeck]

Running vc_redist.exe, (both 9.0.30729.1 and 9.0.30729.4148) does fix the problem. But Microsoft is still not off the hook on this one. Microsoft distributed some bad merge modules and they need to fix them ASAP.
If one installation package unwittingly uses these bad merge modules, it will blow up VC90 dependencies for it and all other applications on the system.
Case in point:
http://www.oooforum.org/forum/viewtopic.phtml?p=340778

edit: This issue occurs on Vista and 2008 platforms. (I have not tested Win 7). A test I ran on 2003 did not have this issue. So its the uplevel components that are involved.

[hsteinbeck]

Microsoft has a hot fix available that fixes this issue, even though it does not specifically refer to the problem. Essentially the hot fix is back porting the MSI 5.0 guts to 4.5.
http://support.microsoft.com/default.aspx?scid=kb;en-us;972397&sd=rss&spid=3198

By the way this also finally fixes a much older issue with upgrading VC merge modules I had discussed here
http://community.flexerasoftware.com/showthread.php?t=176078

[mickgalvin]

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