64bit windows, registry, Wow6432Node is used - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

ChrisGue
Posts: 116
Joined: Tue Feb 03, 2009 7:26 pm

64bit windows, registry, Wow6432Node is used

I use the AI 7.1.3 enterprise

I have defined a value in the resitry in
HKLM\Software\[Manfucaturer]\[ProductName]

A t64 bit windows the value is written under 'Wow6432Node'.
I need it to be written to HKLM\Software\[Manfucaturer]\[ProductName] without the 'Wow6432Node', as well as I have a 64 bit and a 32 bit component.

Is there a way to do that?
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: 64bit windows, registry, Wow6432Node is used

Hello,

You can define your 64-bit registry values from the Registry page and mark their corresponding components as "64-bit Component" from the Organization page.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
ChrisGue
Posts: 116
Joined: Tue Feb 03, 2009 7:26 pm

Re: 64bit windows, registry, Wow6432Node is used

thanks, I think I got that.
buit how to define the same key e.g. HKLM\Software\[Manfucaturer]\[ProductName]\Path as a 64 bit item componente AND a 32 bit component?
I cannot add 'Path' twice?
And the branch is in AI the same although it is not on 64 bit machines.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: 64bit windows, registry, Wow6432Node is used

Hello,

If the registry value is indeed for a 64-bit application then it cannot be installed on 32-bit machines, so there is no need to add the second 32-bit value.
If the registry value is for a 32-bit application then the normal behavior is for it to be installed in the "Wow6432Node" on 64-bit machines.

Here is an article that explains the "Wow6432Node".

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
ChrisGue
Posts: 116
Joined: Tue Feb 03, 2009 7:26 pm

Re: 64bit windows, registry, Wow6432Node is used

If the registry value is indeed for a 64-bit application then it cannot be installed on 32-bit machines
But the registry key marked as 64 bit component is set on a 32 bit machine correctly. And that is what I need.
There is a 32 bit AND a 64 bit component reading the same registry key. Though I need on a 32 bit machine the key set.
If the registry value is for a 32-bit application then the normal behavior is for it to be installed in the "Wow6432Node" on 64-bit machines.
On 64 bit machine there is a 64 bit AND a 32bit component as it is an windows explorer extension and though both is required. And both do read the same registry value. Well for the 32 bit component it is in the Wow6432Node, so I need to set both keys during the installation.

How to solve that?
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: 64bit windows, registry, Wow6432Node is used

Hi,
There is a 32 bit AND a 64 bit component reading the same registry key. Though I need on a 32 bit machine the key set.
I'm afraid I do not understand. Are you saying you need to have the registry entries created under "Wow6432Node" and directly under "HKLM\Software" on
64-bit machines? If so, why?

Does your application reads a hardcode path from the registry and is not automatically redirected by OS on 64-bit machines?
so I need to set both keys during the installation.
An applications launched in Windows will be automatically redirected to the specific hive, i.e. the 32 or 64 bit one. It will not check for the same registry entry
under both hives, i.e. "Wow6432Node" and directly under "HKLM\Software".

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
ChrisGue
Posts: 116
Joined: Tue Feb 03, 2009 7:26 pm

Re: 64bit windows, registry, Wow6432Node is used

I have an explorer extension dll .
It reads the key e.g. HKLM\Software\Mycompany\MySoftware.

The component exists as 32 and as 64 component.
On a 32 bit windows only the 32 component is used.
On 64 bit windows the 64 component is used in the explorer.
So that is all fine

But as far as I know, 32 bit applications on a 64 bit machine, which shows the file open dialog (which then is in 32 bit), which loads my explorer extension dll, thus loads the 32 bit component.
That's why for explorer extensions a 32 AND 64 bit component are required on a 64 bit machine.

The 32 component on 64 bit window will be redirected to HKLM\Wow6432Node\Mycompany\MySoftware.
The 64 bit component will read HKLM\Software\Mycompany\MySoftware.
So, I need both values to be set.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: 64bit windows, registry, Wow6432Node is used

Hello,

Can you please specify what do you mean by "component"? Just to be on the same page, I am referring to an Organization component specific to any installer design. Here is the user guide definition.
But as far as I know, 32 bit applications on a 64 bit machine, which shows the file open dialog (which then is in 32 bit), which loads my explorer extension dll, thus loads the 32 bit component.
That's why for explorer extensions a 32 AND 64 bit component are required on a 64 bit machine.
This cannot be true. An usual application's design implies that one of its components cannot exist both as 32-bit and 64-bit on a 64-bit machine. It is either 64-bit or 32-bit, but I'm inclining towards 32-bit in your case.

How did you design your application, as a 32-bit application or as 64-bit application? Does your application use any other 64-bit components?

If the versions of the registry entries are indeed 32-bit and 64-bit here is an user guide article that explains how to install them in the same location.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
ChrisGue
Posts: 116
Joined: Tue Feb 03, 2009 7:26 pm

Re: 64bit windows, registry, Wow6432Node is used

mihai.petcu wrote:Can you please specify what do you mean by "component"? Just to be on the same page, I am referring to an Organization component specific to any installer design. Here is the user guide definition.
With a component I mean a dll, which belongs to the main feature.
mihai.petcu wrote:This cannot be true. An usual application's design implies that one of its components cannot exist both as 32-bit and 64-bit on a 64-bit machine. It is either 64-bit or 32-bit, but I'm inclining towards 32-bit in your case.
As I wrote, it is not a normal application, it is an windows explorer extension dll to add a context menu in the file context menu. And many system dlls on a 64 bit windows DO exist as 64 and as 32 bit version (in system32 and und SysWOW64).
It is the same with dll which adds e.g. a context menu item in the explorers file context menu. When I rename the 32 bit dll the context menu items are no longer displayed in the file open dialog of a 32 bit program (on x64).
Same in the windows explorer (same machine) when I rename the 64 dll. So in deed both are used.

I have now added the 2nd value as described at the link you posted. Thank you. That is working now.

Best regards,
Christoph
ans
Posts: 17
Joined: Tue Jul 26, 2011 9:06 pm

Re: 64bit windows, registry, Wow6432Node is used

Hi ChrisGrue, did you solve your problem meanwhile? What did you do to be able to write to both branches of the registry?

I am having the same issue. My solution consists of a number of DLLs built for 32 and 64 bit at the same time. This is because these tools are designed to link to third-party applications that also come in 32/64 flavors (pro audio music software, similar to your browsers). The DLLs are sorted under

C:\Program Files\Common Files\Manufacturer\Tools
C:\Program Files (x86)\Common Files\Manufacturer\Tools

In order for the host apps to find the tools, they are referenced in the registry depending on the bitness of the host app. This does currently not work for me.

Return to “Common Problems”