Writing in the x64 part of the registry with an otherwise x86 mai pack created in Wix

Question

I'm writing an installer pack for a product using Wix, the whole thing is in x86, but now i need to add a key to the x64 part of the registry. I looked around and found this stack answer which I thought would solve my problem. But I'm getting a ICE80 error (not a warning) which tells me that I basically need to change my Package Platform attribute to x64.

I would however rather avoid that because as I mentioned it's only one registry key that needs to be in x64.

So my question is: Is there another way to resolve the ICE80 error or do I need to build two msi packages, one for x86 and one for x64.

Here is some of my code to further illustrate what I'm trying to do:

        <Component Id="Foo" Guid="{GUID}" Win64="yes">
    <RegistryKey Root="HKLM" Key="Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\IniFiles">
      <RegistryValue Type="integer" Name="Hello" Value="1"/>
    </RegistryKey>
    <Condition><![CDATA[VersionNT64]]></Condition>
  </Component>

  <Component Id="Bar" Guid="{GUID}">
    <RegistryKey Root="HKLM" Key="Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\IniFiles">
      <RegistryValue Type="integer" Name="Hello" Value="1"/>
    </RegistryKey>
  </Component>

Any help is appreciated!

score 6 · Accepted Answer · answered Oct 02 '12 at 15:35

6

Windows Installer doesn't support a 32-bit package writing to the 64-bit registry (or file system). A 64-bit package can write to both 32-bit and 64-bit portions.

answered Oct 02 '12 at 15:35

Bob Arnson

21,377
2
40
47

So my only option is to make two installers, one 32 bit and another 64 bit? – A.Game Oct 02 '12 at 19:36
This is how I solved it: I made a x64 bit console app that does the job for me which i then run during the installation, and then remove when i'm done. Not very pretty but it works, as it is only one key i need to write :) – A.Game Oct 04 '12 at 21:32
No longer true - see the other comment below about using Win65=yes + suppression of ICE80 – fmike7 Jun 04 '21 at 20:40

score 2 · Answer 2 · answered May 20 '16 at 14:48

Perhaps it didn't work then. I am using Wix v10 and in my x86 WIX project, and adding Win64="yes"initially generated ICE80 error. Once I suppressed that warning (in Visual Studio, "Tool Settings" -> "Suppress specific validation:" column), I no longer get that error. When I ran the x86 installer on Windows 2012 R2, those x64 reg keys were created.

score 0 · Answer 3 · answered Oct 02 '12 at 08:29

0

Add Win64="yes" to the registry entry you want to put in the 64-bit in the registry..:) I have not included the condition in my own and it works perfectly with just the Win64 attribute.

answered Oct 02 '12 at 08:29

Natalie Carr

3,707
3
34
68

I removed the condition and it is still giving me the same error :/ Do you have the x86 and the x64 components in the same package? Or maybe it has to do with the Wix version? I'm running 3.5 – A.Game Oct 02 '12 at 14:06
Are you getting any error if you take the win64 attribute out? – Natalie Carr Oct 02 '12 at 15:02
Is package platform attribute is set to x86? – A.Game Oct 03 '12 at 11:40
1

Hi, sorry I am mistaken, I have two msi's being created one 32-bit and the other 64-bit. Apologies I got mixed up..:( – Natalie Carr Oct 03 '12 at 11:43
Why don't you use a custom action if it is only one key? – Natalie Carr Oct 04 '12 at 10:21
The problem with that is that my CustomAction.dll is also a in 32-bit. This is how I solved it: I made a x64 bit console app that does the job for me which i then run during the installation, and then remove when i'm done! – A.Game Oct 04 '12 at 21:30

Writing in the x64 part of the registry with an otherwise x86 mai pack created in Wix

3 Answers3