4 replies to this topic

[kutz]

Hi,

I use InstallShield 10. I built a Basic MSI-Project. During Deinstallation I got the message that the uninstallation have no rights to delete the HKEY_LOCAL_MACHINE\Software - Branch.
But it deleted already a lot......

Does anyone know why this happens or had anyone of you a similar problem?
This happened now on 2 PCs with a lot of trouble to install the OS again .

Best Regards,
Steffen

[Stefan Krueger]

Double check the properties of the registry keys in your project.

[kutz]

Hi,

thanks a lot for your help.
Indeed I found at the table registry a row like:

Name *
Value <leer>

This explains the uninstallation of the whole BRANCH . What I still don't understand is how installshield came to this entry.

I could now reproduce the error if I set the COM Extract at Build to yes.
If I do this one strange row is created with
Root: 2
Key: software
Name: *
Value: <leer>

Why InstallShield creates this entry?
Is this an InstallShield - Bug or could it be that the DLL I register has an error?

I looked with the help of RegSpyUI.exe to the DLL but didn't found something exceptionel.

Thanks for any help.

Regards,
Steffen

[andyguest13]

I have had the same problem; I finally figured out the culprit by forcing an immediate COM extract in IS Pro of the executable i suspected. It dumped the output at the end of this message into the Results window. I tracked it further down to a Microsoft Office DLL I import into my app - MSo9.DLL. But when i use RegSpyUI on that, the output is empty - except if i export a .REG file and look at that, then i see the offending root classes key whihc the uninstaller squeals about but goes ahead and deletes anyway! I thought i might be able to stop this SOFTWARE\CLASSES stuff going into my MSI using filters.xml but that would stop absolutely everything goping in wouldn't it?. Anyway - i am stuck!! Any help please. Is it a bug in IS PRO? Thanks, Andy.

CLSID
CLSID\{EEB283BA-9CD5-4185-844D-D435ED086453}
CLSID\{EEB283BA-9CD5-4185-844D-D435ED086453}\Programmable
CLSID\{EEB283BA-9CD5-4185-844D-D435ED086453}\TypeLib
Interface
Interface\{549C81F1-40E0-48DD-974E-DE22C9C48F34}
Interface\{549C81F1-40E0-48DD-974E-DE22C9C48F34}\ProxyStubClsid
Interface\{549C81F1-40E0-48DD-974E-DE22C9C48F34}\ProxyStubClsid32
Interface\{549C81F1-40E0-48DD-974E-DE22C9C48F34}\TypeLib
TypeLib
TypeLib\{763CDDF1-6ECB-4736-B35C-84F1E94B2087}
TypeLib\{763CDDF1-6ECB-4736-B35C-84F1E94B2087}\1.0
TypeLib\{763CDDF1-6ECB-4736-B35C-84F1E94B2087}\1.0\0
TypeLib\{763CDDF1-6ECB-4736-B35C-84F1E94B2087}\1.0\0\win32
TypeLib\{763CDDF1-6ECB-4736-B35C-84F1E94B2087}\1.0\FLAGS
TypeLib\{763CDDF1-6ECB-4736-B35C-84F1E94B2087}\1.0\HELPDIR


SOFTWARE
SOFTWARE\Microsoft
SOFTWARE\Microsoft\Windows
SOFTWARE\Microsoft\Windows\CurrentVersion
SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer
SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

[Stefan Krueger]

I don't recall exactly, but it may have been a bug in an older version of Installshield. Are you using one of the more recent versions, or at least did you install all hotfixes?