Hello,
Please note that when a 32-bit application writes or reads a value under the
HKEY_LOCAL_MACHINE\SOFTWARE, the application reads from the
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node on a 64-bit OS.
Their 32-bit counterparts are resolved to redirected locations as follows:
- ProgramFilesFolder - C:\Program Files (x86)\
- CommonFilesFolder - C:\Program Files (x86)\Common Files\
- SystemFolder - C:\Windows\SysWOW64\
- HKEY_LOCAL_MACHINE\SOFTWARE - HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node
This is the default behavior for Windows Installer.
The correct approach is to select the
Mixed 32/64-bit matching the platform option in the
Install Parameters page. This way, the package runs as a 32-bit package on 32-bit systems and as a 64-bit package on x64 systems.
The .MSI does not support mixed package type, thus the package type will be turned into an .EXE package type. The .EXE bootstrapper built by Advanced Installer is a 32 bit one, this contains the x86 and x64 MSI files as well as the files to be installed from the CAB. When launched the EXE checks for the operating system architecture and it launches the correct MSI.
Also, you need to select the
64-bit Component from the
Component Properties that has been assigned to the related registry.
Please let me know if you have any questions.
Best regards,
Dan
FOLLOW US
Get the latest news in Application Packaging