Custom Search: (x86) being added to "Program Files" - 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!

tskiles
Posts: 12
Joined: Mon Sep 21, 2009 7:13 pm

Custom Search: (x86) being added to "Program Files"

I have a Launch Condition based on custom searches.

Unfortunately, a customer has enlightened me to the fact that under certain conditions, 32-bit Office 2013 will install in Program Files instead of Program Files (x86) but the registry settings are added to the Wow6432Node.

The launch condition fails and I am assuming it is because when the search returns a path to "C:\Program Files\Microsoft Office 15\..." , the Installer is being helpful and interpreting it as "C:\Program Files (x86)\Microsoft Office 15\..." because the path was stored in the Wow6432Node. However, in this case, I really want it to check the path exactly as it was stored.

I can fool the installer into installing by simply adding empty dummy folders in the Program Files (x86) folder which reinforces my theory.

Is there something I could do differently to force it to check the path it actually finds?
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Custom Search: (x86) being added to "Program Files"

Hi,

It is the Windows Installer that interprets the "Program Files" as "Program Files (x86)" when you have a 32-bit MSI package type. It works well in case of a 64-bit package.

I'm not sure why do you need the exact path to set the launch condition, I think you can only check if the search property is empty or not.

However, if you want the exact path, you can create a "File search" instead of a "Registry search" or you can use the method you mentioned.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
tskiles
Posts: 12
Joined: Mon Sep 21, 2009 7:13 pm

Re: Custom Search: (x86) being added to "Program Files"

Thank you for your response. I suspected it was the Windows Installer being "helpful".

I was using "The value contains a path to a directory" for the added insurance. My workaround was as you suggested, I switched it to "Retrieve the raw value". This seems to work fine.
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Custom Search: (x86) being added to "Program Files"

You're welcome. I'm glad you got this working.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”