[wix-users] WOW6432Node / CLSID

Christopher Painter chrpai at iswix.com
Sun Mar 31 17:39:23 PDT 2019

While I don't have your DLL, I was able to quickly create a 64bit MSI that creates the registry value in the correct location by following this:


In both the merge module and product  projects set the Package @ Platform attribute to x64.
In the product project change the installation directory parent to ProgramFiles64Folder

        <Component Id="owc8984A410245EF44F4ED3F43CB8F51225" Guid="16742348-b656-4411-fa5e-56ec1a03fb9b" Win64="yes">
          <Class Id="{E6D572FE-8E55-4A99-AB31-3C1AF6A4BC35}" Context="InprocServer32" ForeignServer="[#owf8984A410245EF44F4ED3F43CB8F51225]" />
          <File Id="owf8984A410245EF44F4ED3F43CB8F51225" Source="$(var.SourceDir)\test.dll" KeyPath="yes"/>

Built and installed and registry key/value is created in 64bit hive correctly.

From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Mark Haroldson via wix-users <wix-users at lists.wixtoolset.org>
Sent: Sunday, March 31, 2019 2:59 PM
To: wix-users at lists.wixtoolset.org
Cc: Mark Haroldson
Subject: [wix-users] WOW6432Node / CLSID

I have run into a problem. I have 100% 64 bit app. But when I attempt to register my com dll via WIX is being added to the WOW6432Node/CLSID node.

The component is marked as 64 bit and other registry entries (HKLM) are getting placed into the correct location but for whatever reason everything going to HKCR is being put into the WOW6432Node.

Here is a snippet of what I am doing.

        <Component Id="Registry.11" Guid="27ae4001-a77e-45c4-9f15-03e19648251c" Win64="yes">
          <RegistryKey Root="HKCR" Key="CLSID\{E6D572FE-8E55-4A99-AB31-3C1AF6A4BC35}\\InProcServer32">
            <RegistryValue Id="RegValue.2" Type="string" KeyPath="yes" Value="[INSTALLDIR.bin]XXXPCP.dll" />

          <CreateFolder />

Any ideas?


WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

More information about the wix-users mailing list