From what I can see in your screenshots, you are trying to search for a key in the WOW6432Node.
"Registry key exists" type of search should return "1" when the registry key exists, so the condition you are using is good.
Can you please make sure that, in the "Search" page, you don't have the "Search the 64-bit portion of the registry" checked?
As you may probably know, the WOW6432Node key is used to present a separate view of HKEY_LOCAL_MACHINE\SOFTWARE for 32-bit applications that run on a 64-bit version of Windows. When a 32-bit application queries a value under the HKEY_LOCAL_MACHINE\SOFTWARE\<company>\<product> subkey, the application reads from the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\<company>\<product> subkey.
If the "Search the 64-bit portion of the registry" is checked, your search will be invalidated.
The application that insert registry is 32bit,and registry is correct. if i check Search the 64-bit portion of the registry then the search will not return results since it will search for 64bit app. and will not find registry entry (and that is also true) .
With this what i want to achieve is if registry exist (that mean my 32bit app is installed), the installer can continue, if not then installer should finish.
The main question that bothered me is that condition pop up is always showing and installation fails no matter that registry is there.
Although the search condition return that registry exist and and lunch condition says search_property="1" the installation fails (show pop up ), i expect since the registry is there the installation to continue.
The application that insert registry is 32bit,and registry is correct. if i check Search the 64-bit portion of the registry then the search will not return results since it will search for 64bit app. and will not find registry entry
This is why I said that you should not have that option checked.
Can you please attach a screenshot of how you are configuring the search from the "Search" page?
First of all, thanks for your sent project, it was helpful.
I have tested this again and indeed I was able to reproduce it using Advanced Installer 14.9.
This seems to be a bug in what regards a .EXE setup which has custom launch condition/s based on a registry search, which has been fixed starting with Advanced Installer 15.0.1.
The workarounds to this are:
1- Go to "Prerequisites" page and uncheck the "Check predefined launch conditions before searching for prerequisites" option.
2- Upgrade to a newer Advanced Installer version (>= 15.0.1).
3- Change the "Package Type" to "Single MSI" from the "Builds" page.
