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!

syn3rgy
Posts: 3
Joined: Wed Apr 22, 2020 11:35 am

defaulting to C:\Windows\Program Files\....

Hi,
I am very new to advanced installer and trying to create a very simple install package that also adds some registry entries.
2 issues i am encountering so far:

1) when creating the installer package and i add the files to Application Folder so i can have them installed to C:\program files (x86)\ProductName\
when building and running the installer, it always seems to default to c:\windows\program files(x86)\ProductName and i cannot for the life of me find where\how to change this.

2) If i just test run the installer, it should add some registry keys which i have included under the Registry section, these do not seem to get added.

Any help would be greatly appreciated.

Thank you
Catalin
Posts: 7853
Joined: Wed Jun 13, 2018 7:49 am

Re: defaulting to C:\Windows\Program Files\....

Hello and welcome to Advanced Installer forums,
when creating the installer package and i add the files to Application Folder so i can have them installed to C:\program files (x86)\ProductName\
when building and running the installer, it always seems to default to c:\windows\program files(x86)\ProductName and i cannot for the life of me find where\how to change this.
This can be changed from the "Install Parameters" page --> "Installation Folders" section --> "Application folder" field. By default, the value is:

Code: Select all

[ProgramFilesFolder][Manufacturer]\[ProductName]
which should be just what you are looking after.
If i just test run the installer, it should add some registry keys which i have included under the Registry section, these do not seem to get added.
First of all, please keep in mind that in order to modify the registry, one should provide elevated privileges (administrator privileges). For instance, you should run the setup as an administrator. This can be done in the following way:

- if your resulted setup is an MSI, run the command line as administrator (right click --> "Run as administrator") and then run your msiexec using a command line as it follows:

Code: Select all

msiexec /i <path_to_your_MSI>
- if your resulted setup is an EXE, simply right click on it --> "Run as Administrator"

- if you want your package to always run as an administrator, you can go to "Install Parameters" page and check the "Run as administrator" option. Please note that this will automatically convert your package to an EXE (if it's not already an EXE).

If you have already done this, there might be 1 more thing here, which is the registry redirection. Please note that if a 32-bit process tries to modify the registries on a 64-bit machine, all the modifications will be redirected to the WOW6432Node key. Therefore, if your package is of 32-bit type ("Install Parameters" page --> "Installation Behavior" section --> "Package Type" field) and you install it on a 64-bit machine, the process will redirect all the modifications (in our case, the creation of the registries, under the WOW6432Node key).

Hope this helps.

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”