Summary
This article explains how to create an install condition based on a specific registry entry.Synopsis
How to create an install condition based on a system search to detect whether a registry entry exists using Installshield. This install condition in the example below is useful for checking for the existence of another Basic MSI installation on the target machine. The install condition should only allow the installation to continue if the other Basic MSI installation does not exist on the target machine.Discussion
In order to create the install condition and the corresponding system search, follow these steps:
1. Open your Basic MSI project in the Installation Designer view of the InstallShield IDE.
2. Navigate to the Behavior and Logic > System Search view.
3. In the top, right-hand white area under the System Search columns and under any existing system search entries, right-click.
4. Click Add...
5. At the introduction screen to the System Search Wizard, click the Next button.
6. Select Registry entry from the dropdown box.
7. Click the Next button.
8. Select HKEY_LOCAL_MACHINE from the Registry Root dropdown box.
9. Copy and paste the following value into the Registry Key field: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{00203668-8170-44A0-BE44-B632FA4D780F}
(The value in curly braces should be the Product Code of the other Basic MSI installation being detected by the system search.)
10. Set the Registry Value field to the following value: UninstallString
11. Click the Next button.
12. Under the Store the value in this property field enter the name of the public property that will store the result of the system search. For this example, name the property as follows: SAMPLEPROPERTY
13. Select the Store the value in the property and use the property in an Install Condition radio button.
14. Click the Finish button.
15. Navigate to the Installation Information > General Information > Product Properties view.
16. Double-click the field next to the Install Condition label.
17. Set the condition to the following modified value: Not SAMPLEPROPERTY
18. Set the desired message under the Message column corresponding to the row with the Not SAMPLEPROPERTY condition.
19. Click the OK button.
20. Save the project.
21. Build the project.
22. Test the installer.
If the system search and install condition are configured correctly (as described above), the installation should only continue if the other Basic MSI installation is not detected through the presence of the previously specified registry entry (from steps 8-10) on the target machine. Otherwise, the installation should display the previously specified message (from step 18).
Every Basic MSI project should have a default value for the UninstallString Value name similar to the following:
MsiExec.exe /l{<Product Code>}
It is important to specify a Registry Value in the System Search of a Value Name that always has a default value. If a Registry Value is not specified, the System Search will check the value of the Default Value Name, which most likely will have a null value. If a null value is returned by the System Search, the specified property will be set to null. As a result, the Install Condition based on the System Search will not evaluate correctly.
Additional Information
For more information on Adding a System Search, see the InstallShield Help Library topic Adding a System Search.
For more information on using the System Search view, see the InstallShield Help Library topic System Search Wizard.
Was this helpful?
Related Articles
Unable to Change the Font Used for the Cancel Installation Dialog 4Number of Views An Installation Support File Could Not Be Installed. Interface Not Registered 4Number of Views Registering Your Product 4Number of Views Shortcut to Folder Created Using AddFolderIcon Opens the Open With Box 3Number of Views InstallShield fails to create Patch/Upgrade from a compressed setup.exe 6Number of Views
Revenera Assistant
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago