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?
FOLLOW US
Get the latest news in Application Packaging