This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- MSI uninstall creates bluescreen
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Aug 10, 2017
07:31 AM
MSI uninstall creates bluescreen
I'm getting better with time with Installshield and creating MSI but recently i've been working on a MSI that has been created couple years ago by a colleague that does not work here anymore.
Long story short, when I'm running the uninstall of the product, it tries to access certain registry key like HKLM\SYStem\Currentcontrolset which has nothing to do with the product itself and tries to delete the whole tree.
I'm a bit lost on where to look at in Installshield to prevent this action in the uninstall process.
Can somebody give me some directions ? Thanks in advance
Long story short, when I'm running the uninstall of the product, it tries to access certain registry key like HKLM\SYStem\Currentcontrolset which has nothing to do with the product itself and tries to delete the whole tree.
I'm a bit lost on where to look at in Installshield to prevent this action in the uninstall process.
Can somebody give me some directions ? Thanks in advance
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Aug 14, 2017
10:18 AM
Sounds like this:
https://flexeracommunity.force.com/customer/articles/en_US/ISSUE/Q113345
They broke the HTML table in the latest KB article, though. Ignore that broken rowspan tag.
Gist of it is: the older COM Extraction would include a root level key if some *.dll's, *.ocx, etc. touch the key for some reason, but otherwise don't write anything to it. You can manually tweak an already built MSI file to fix this, or you can rebuild it with a newer InstallShield to see if the new filters correct it.
https://flexeracommunity.force.com/customer/articles/en_US/ISSUE/Q113345
They broke the HTML table in the latest KB article, though. Ignore that broken rowspan tag.
Gist of it is: the older COM Extraction would include a root level key if some *.dll's, *.ocx, etc. touch the key for some reason, but otherwise don't write anything to it. You can manually tweak an already built MSI file to fix this, or you can rebuild it with a newer InstallShield to see if the new filters correct it.