Hi Carlo and welcome to Advanced Installer forums,
When a 32-bit application writes or reads a value under the C:\Windows\System32 directory , the application reads from the C:\Windows\SysWOW64 directory 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\
This is the default behavior for Windows Installer. A 32-bit installation package, on 64-bit machines, cannot install resources into 64-bit locations (i.e. "Program Files" folder).
In order to implement your scenario, you can select the
Mixed 32/64-bit matching the platform option for the package type.
This package runs as a 32-bit package on 32-bit systems and as a 64-bit package on x64 systems. It allows you to have a single installation package that will install on both platform types (32-bit and 64-bit platforms) and can install files or registry in the real system paths regardless of the platform.
When the "
Mixed 32/64-bit matching the platform"
package type is selected in the
Install Parameters page, then the wizard will launch and will guide you step by step through every stage required to organize your “Mixed 32/64-bit matching the platform” package, as it can be seen in the below image:
Here is an article which may be useful to you:
How do I create a package that will be installed like a 64-bit package on 64-bit platforms and as 32-bit package on 32-bit platforms ?.
This easy approach is to use the
Mixed 32/64-bit matching the platform wizard.
If you have other questions, please let us know.
Kind regards,
Dan
FOLLOW US
Get the latest news in Application Packaging