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
- :
- Uninstall leaving .OCX file behind.
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
Jun 18, 2013
12:10 PM
Uninstall leaving .OCX file behind.
My installation is installing the Flash Active X control (a .OCX file) as a dependency (Thank you Crystal Reports!).
The uninstall is leaving this one file behind and not deleting it.
Even though I am logged in as a domain admin, I have to take ownership of the install folder and then grant myself access to the folder before I can delete it manually.
What do I have to do to get the uninstall to work properly?
The uninstall is leaving this one file behind and not deleting it.
Even though I am logged in as a domain admin, I have to take ownership of the install folder and then grant myself access to the folder before I can delete it manually.
What do I have to do to get the uninstall to work properly?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 24, 2013
05:01 AM
Hello,
The things that weren't being uninstalled were the components which were registered in the Windows registry (using the self-register option)(and the folders that contained them).
So, first remove the entries from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls that pointed to your setup components and remaining respective foldersin programfiles folder,shortcuts(if any) manually.
After that, create a supported custom action(EXE or vbscript or jscript) to remove all the respective registry entries from registry (that the uninstallation had not remove) and remaining folders,then schedule it to run during uninstallation.
Hope this helps
Thanks
Chiranjeevi
The things that weren't being uninstalled were the components which were registered in the Windows registry (using the self-register option)(and the folders that contained them).
So, first remove the entries from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls that pointed to your setup components and remaining respective foldersin programfiles folder,shortcuts(if any) manually.
After that, create a supported custom action(EXE or vbscript or jscript) to remove all the respective registry entries from registry (that the uninstallation had not remove) and remaining folders,then schedule it to run during uninstallation.
Hope this helps
Thanks
Chiranjeevi