This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- registry entry creation issue under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 25, 2013
11:48 AM
registry entry creation issue under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
hi,
we were providing 32 bit installer to customers for the past few years and customers used to install it on 64 bit machines , now we got a requirement that they need 64 bit installer only, so for this, I changed "Template Summary" from Intel;1033 to x64;1033 and saved, I created my package and when I installed it on 64 bit machines, it is still creating my product entries under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node.
in earlier releases 32 bit installer on 64 bit machines and creating product entries under wow6432Node was fine, but now we do not need wow6432Node entries any more. it should create product entries under normal hive(HKEY_LOCAL_MACHINE\SOFTWARE) only.
am I missing anything to change apart from "Template Summary", or somewhere my installscript is changing any values, our project is in basic msi. please help me on this.
thanks in advance
gmp
we were providing 32 bit installer to customers for the past few years and customers used to install it on 64 bit machines , now we got a requirement that they need 64 bit installer only, so for this, I changed "Template Summary" from Intel;1033 to x64;1033 and saved, I created my package and when I installed it on 64 bit machines, it is still creating my product entries under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node.
in earlier releases 32 bit installer on 64 bit machines and creating product entries under wow6432Node was fine, but now we do not need wow6432Node entries any more. it should create product entries under normal hive(HKEY_LOCAL_MACHINE\SOFTWARE) only.
am I missing anything to change apart from "Template Summary", or somewhere my installscript is changing any values, our project is in basic msi. please help me on this.
thanks in advance
gmp
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 25, 2013
12:02 PM
Make sure that the underlying component of the registry entry in question is marked as 64-bit. For more information, see the 64-bit Component setting in the Component Settings help topic.
Hope that helps.
Hope that helps.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 26, 2013
07:09 AM
hi Hidenori Yamanishi,
I made "Yes" for "64-Bit component", but still my installer is creating product entries under "32 bit version of windows" only.
from http://helpnet.flexerasoftware.com/installshield20helplib/Content/helplibrary/Targeting64Bit-MSI.htm#introduction_229763594_1282016 link
<>
Creating 64-Bit Components
To specify that a component is 64 bit, select Yes for the component’s 64-Bit Component setting. If you build a release that has at least one 64-bit component and the Template Summary property is set to a 64-bit value, the result is a 64-bit package.
<>
do I need to have at least one 64 bit component apart from registry component in my project?. My project has only one exe and other xml files, I did not make "Yes" for 64-Bit Component for any of these files, that's why my installer is still writing under "32 bit version of windows?"
your suggestions are valuable.
thanks in advance
gmp
I made "Yes" for "64-Bit component", but still my installer is creating product entries under "32 bit version of windows" only.
from http://helpnet.flexerasoftware.com/installshield20helplib/Content/helplibrary/Targeting64Bit-MSI.htm#introduction_229763594_1282016 link
<>
Creating 64-Bit Components
To specify that a component is 64 bit, select Yes for the component’s 64-Bit Component setting. If you build a release that has at least one 64-bit component and the Template Summary property is set to a 64-bit value, the result is a 64-bit package.
<>
do I need to have at least one 64 bit component apart from registry component in my project?. My project has only one exe and other xml files, I did not make "Yes" for 64-Bit Component for any of these files, that's why my installer is still writing under "32 bit version of windows?"
your suggestions are valuable.
thanks in advance
gmp
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 27, 2013
02:46 PM
If you are creating a 64-bit package you should set the each component as 64-bit.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)