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 bug
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Jan 04, 2016
02:00 AM
sEstimatedSize2 registry getting created in Uninstall\{ProductCode} hive
On Windows 10 and Windows Server 2016, multiple entries are getting created for cost estimation of MSI.
Under HKLM..\Uninstall\{ProductCode} EstimatedSize entry is created during MSI execution, but after some time i can see another entry getting automatically created sEstimatedSize2, the values indicated in this registry is same as that of EstimatedSize.
The issue is, during uninstall the {ProductCode} hive remains with that sEstimatedSize2 registry.
Anybody have any idea why this is getting created?
Under HKLM..\Uninstall\{ProductCode} EstimatedSize entry is created during MSI execution, but after some time i can see another entry getting automatically created sEstimatedSize2, the values indicated in this registry is same as that of EstimatedSize.
The issue is, during uninstall the {ProductCode} hive remains with that sEstimatedSize2 registry.
Anybody have any idea why this is getting created?
(2) Replies
‎Feb 09, 2016
11:07 PM
‎Mar 09, 2016
10:50 AM
I have found that in Windows 10, sometimes when I uninstall our product, it will leave behind the registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, and the only values in it will be (Default) and sEstimatedSize2. The result is that you cannot install the product at this point. I've done some digging into this and found a thread in which someone from Lenovo is claiming this to be an msi bug that was introduced in Windows 10 version 1511 (KB3116278) back in November of 2015. It doesn't appear to me yet that MS is aware of this issue or has any plans to address it. I may need to add a custom action to the end of my setup to check for this registry key and delete it if found.
Update: More information found on this: https://social.msdn.microsoft.com/Forums/en-US/10cb99f9-c751-4298-8e1f-af135d9aafba/sestimatedsize2-registry-getting-created-in-uninstallproductcode-hive?forum=windbg
It seems that if i have an install on my machine more than a few days, at some point something modifies the registry and adds the sEstimatedSize2 entry. Because of this modification the installer does not remove the uninstall registry key.
Update: More information found on this: https://social.msdn.microsoft.com/Forums/en-US/10cb99f9-c751-4298-8e1f-af135d9aafba/sestimatedsize2-registry-getting-created-in-uninstallproductcode-hive?forum=windbg
It seems that if i have an install on my machine more than a few days, at some point something modifies the registry and adds the sEstimatedSize2 entry. Because of this modification the installer does not remove the uninstall registry key.