tag:blogger.com,1999:blog-9537945.post4439743339630766993..comments2023-08-20T04:16:39.520-05:00Comments on Deployment Engineering Archive: InstallShield COM ProblemsChristopher Painterhttp://www.blogger.com/profile/12167478740431444267noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-9537945.post-20965571017068502282008-08-16T06:56:00.000-05:002008-08-16T06:56:00.000-05:00Always good to run validation to sort out problems...Always good to run validation to sort out problems such as this. Not sure if ICE would have caught this, but a custom registry checker ICE can easily be created to do so.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-9537945.post-53983746163259577712008-08-13T20:03:00.000-05:002008-08-13T20:03:00.000-05:00We just ran into this when our upgrade killed Outl...We just ran into this when our upgrade killed Outlook 2007. There are spurious * entries in the COM extracted registry entries - like for instance "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" and a few other choice locations. When the uninstaller is invoked, these keys are cleared. Ouch!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-9537945.post-30189841525791315412007-08-14T12:26:00.000-05:002007-08-14T12:26:00.000-05:00Sairen, that would not surprise me as they made se...Sairen, that would not surprise me as they made several changes in 11.5 to COM extraction. <BR/><BR/>Christopher thanks for mentioning this. I certainly stopped and started to browse our MSI package for these entries.Danhttps://www.blogger.com/profile/07138642769361999429noreply@blogger.comtag:blogger.com,1999:blog-9537945.post-2430897983530479192007-08-13T08:44:00.000-05:002007-08-13T08:44:00.000-05:00I called Macrovision's tech support to get some ot...I called Macrovision's tech support to get some other clarification on this problem, and the person I spoke to said it actually applied to versions 11.5 or later (!!)Anonymousnoreply@blogger.com