Summary
This article describes how to configure your setup to persist these property values for further operations on the installed package.Synopsis
Windows Installer does not persist changes made at runtime to the MSI Database, which makes it not possible by default to gain access to property values that a User or other Custom Action may have changed during the initial installation while running Maintenance or Uninstalls. This article describes how to configure your setup to persist these property values for further operations on the installed package.
Discussion
1. Create a registry key similar to the following:
HKLM\Software\My Company Name\My Product Name\
2. Set a value for this key using the name/value pair of your custom property:
Name: MYPROP
Value: [MYPROP]
This will write the value of the custom property to the registry during installation.
3. Create a System Search to search for the registry entry, and then store it in the same named property you used in step 2 (MYPROP).
Given the above steps, what will take place is that during Uninstall and Maintenance the AppSearch action will still run, and reset the default value of MYPROP to the value you wrote to the registry during the initial installation. This will also allow for changes to the property during the User Interface of Maintenance operations, since the new value will be written for later usage.
Was this helpful?
Related Articles
Disable Maintenance and Uninstall for a Basic MSI Project 6Number of Views Add/Remove Programs Hangs When Launching an Application During Uninstall 4Number of Views Launch a Custom Action Only When Uninstall is Selected From Add/Remove Programs 10Number of Views Basic MSI Project: Uninstall Does Not Remove the Device Driver Folder 5Number of Views sEstimatedSize2 Value is Left Behind in the Uninstall Registry Key After Uninstallation 4Number of Views
Revenera Assistant - Beta
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