#3238 Win64="yes" is not working in 3.6 wix while it was working in wix 2.0 with x86 platform


Hi Guys,

The issue is that I have an x86 installer with wix 2.0 and it is working till .NET 3.5 but it is failing in Winodws 8 which has default .NET 4.0. It works fine if I installed .NET 3.5.

Now I am planning to move from wix v2.o to v3.6 to support till .NET 4.5. While migrating the product.wxs I am facing an issue in wix 3.6. I am using a component that has Win64="yes" attribute in x86 platform installer. In v2.0 it is complied and working file but it is failing in wix v3.6 when it executes on light.exe (it complies using candle.exe well).

Currently it is x86 installer but only one component that is registered in x64 hive depending upon the whether Outlook x64 installed otherwise it is registered in x86 mode. I want a x86 installer as it was with v2.0 wix but one component should be registered in x64.

Wix v3.6 it is giving following error:
error LGHT0204 : ICE80: This package contains 64 bit component 'OL_DLL_COMP64' but the Template Summary Property does not contain Intel64 or x64.

The component is defined as:
<Component Id="OL_DLL_COMP64" Guid="$(var.OL_DLL_COMP_GUID64)" Win64="yes">
<Condition>VersionNT64 AND <![CDATA[OUTLOOK64BITINSTALLED = "TRUE"]]></Condition>
<Registry Id="regMM164" Root="HKCR" Key="CLSID\{1B81DAAA-4E2F-4D78-A461-C9F64D0D6D03}" Value="Connect Class" Type="string"/>
<Registry Id="regMM264" Root="HKCR" Key="CLSID\{1B81DAAA-4E2F-4D78-A461-C9F64D0D6D03}\\InprocServer32" Value="&lt;span&gt;[#MeetMe_Shim_dll]&lt;/span&gt;" Type="string"/>

Can you please guys help me out to resolve this issue in x86 installer. I don't want separate installer for x86 and x64.

Thanks in advance.



  • Bob Arnson

    Bob Arnson - 2013-03-11
    • status: open --> expected-behavior
  • Bob Arnson

    Bob Arnson - 2013-03-11

    Windows Installer doesn't support both x64 and x86 platforms from a single package. That's an MSI limitation.

  • Navanit katiyar

    Navanit katiyar - 2013-03-12

    As I mentioned in my previous mail that it was working with wix 2.0. So what happened in wix 3.7.

  • Bob Arnson

    Bob Arnson - 2013-03-12

    It was a bug in WiX v2.0 that it didn't detect the invalid combination.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks