Orphaned COM Entries in a Minor Upgrade

Title

Summary

If COM entries in a COM server is updated, delivering the update as a minor upgrade may cause the previous COM entries to be orphaned.

Synopsis

If COM entries in a COM server is updated, delivering the update as a minor upgrade may cause the previous COM entries to be orphaned.

Discussion

This is a limitation of the Windows Installer Minor Upgrade technology. Since COM is not unregistered unless the files/component is uninstalled, the entries are orphaned in a minor upgrade scenario since files are simply overwritten rather than removed/reinstalled.

Workaround

Perform a major upgrade if COM keys need to be updated. Otherwise, a custom action can be used to unregister the old COM server before it is updated.

Was this helpful?

Support Hub

Product

InstallShield

Visibility

Guest

URL Name

orphaned-com-entries-in-a-minor-upgrade

Are you sure you want to cancel the case creation?

Case closed successfully

Action performed successfully

Upload Attachment

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

Get Hotline support

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.

Summary

Synopsis

Discussion

Workaround

Related Articles

Please wait...

Case id: 00001065