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!

mhubel
Posts: 28
Joined: Fri Jul 20, 2007 2:01 pm
Contact: Website

not detecting installed prerequisite

With an installation with multiple prerequisites, the test is version number and a registry entry. One of the prerequisites works properly and does not attempt to re-install, the other works on some machines but not others. In all cases a manual look with regedit shows the required entry but the installer does not detect it.

The offending file is attached. The offending registry entry is:

HKEY_LOCAL_MACHINE\SOFTWARE\CUSTPDF Writer

The registry entry appears identical on both working and non-working systems (as seen in an export).
Attachments
LX_Event_install_1.aip
(60.72 KiB) Downloaded 400 times
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: not detecting installed prerequisite

Hello,

This may happen when you are installing on a 64-bit machine. Please keep in mind that by default our Prerequisite search support will look for the above registry key in the following location:

Code: Select all

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\CUSTPDF Writer
as the search will be redirected under the "Wow6432Node" registry zone.

So, in order to avoid this behavior you should check the "Use 64-bit locations when evaluating conditions on a 64-bit machine" option from "Prerequisites Install Conditions" tab.

Let us know if this helped.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
mhubel
Posts: 28
Joined: Fri Jul 20, 2007 2:01 pm
Contact: Website

Re: not detecting installed prerequisite

That did seem to fix it. I would have thought the check box:

"Use 64-bit locations when evaluating conditions on a 64-bit machine"

would do exactly the opposite and only use the Wow6432Node node when checked.

Return to “Common Problems”