Summary
This article explains why the uninstall registry key may not get removed due to sEstimatedSize2 being left behind and where this value comes from.Symptoms
After uninstalling on a Windows 10 or Windows Server 2016 machine, the uninstall registry key, "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{ProductCode}" may have a registry value named sEstimatedSize2 left behind.Cause
The sEstimatedSize2 registry value is not created by InstallShield. This can be observed right after an installation completes as sEstimatedSize2 should not be seen in the uninstall registry key for the corresponding product. The registry value has been observed to be created by a Win32 service called Storage Service (StorSvc.dll) on Windows 10 and Windows Server 2016 some time after installation.Resolution
This is a Microsoft issue regarding Storage Service and cannot be resolved by Flexera.Workaround
To make sure the uninstall registry key gets removed during uninstallation, the RemoveRegistry table or a custom action can be used to programmatically remove the registry data during uninstall.Additional Information
Removing Registry Data Created by Your ProductWas this helpful?
Related Articles
Files Are Left Behind After An Uninstall Or Major Upgrade 3Number of Views Why Are Temporary Files Left Behind After Installation 3Number of Views What is "Uninstall" evidence? 26Number of Views Oracle DB is reporting in after uninstallation 6Number of Views Launch a Custom Action Only When Uninstall is Selected From Add/Remove Programs 10Number of Views
Revenera Assistant
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
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