Registry problem, can't seem to find correct key

[Ton_B]

I've came across this problem before, see: Add Additional data to Add/Remove programs list

Jimo, found the solution for the proble, on how to add additional information to the "Add/Remove program" window.

But I'm having trouble finding the correct registry keys.

It seems IA 6 creates it's own reg.key in:
HKLM\\Software\\Microsoft\\Windows\\Currentversion\\Uninstall\The key created will be something like this:
{2AE36F8B-71B6-4579-B1A3-97591A1E8F45}

Inside this key, all of the values filled out in the options-dialog, such as Publisher and version etc. will be placed here.

Bu I really do not want to use this "number" but simply create a name sucht as "HKLM\\Software\\Microsoft\\Windows\\Currentversion\\Uninstall\\$TITLE$
In that case I can add some additional informaton, like Readme, to the add/remove program window.

Does someone has any idea how I can detect that long number or, how I can change the numer into $TITLE$

Thanx.

Ton.

[MichaelNesmith]

Actually, this is not an accurate observation. InstallAware does use the $TITLE$ location for its Control Panel Add-Remove listing. The other location you noticed are the entries that Windows Installer creates, which cannot be supressed. Supressing or damaging those entries can hurt the installation state of your product - so don't do that. Just write to $TITLE$ instead.

[Ton_B]

I did create some keys inside the HKLM\\...\\$TITLE$ key, but these values are not shown in the add/remove program list.
The MSI setup will create a key like {2AE36F8B-71B6-4579-B1A3-97591A1E8F45} But these values are not used for showing information in the Add/Remove program window.
Instead, information from the key in HKEY_CURRENT_USER\\...\\$TITLE$ are used.

Why are these valus stored inside Current users instead of Local machine ????
When running the .Exe setup it will be stored inside the HKLM, but running the .MSI setup, suddenly it will be stored inside HKCU ?

[mka]

A very old thread, but I have the same question; why HKCU when using MSI?
I have tried explicit to set ALLUSER=TRUE.
--mka

[FrancescoT]

Dear Mka,

the UNISTALL key gets Always stored under HKLM when ALLUSER is TRUE... just verified with installing a MSI package.

Regards