Add/Remove entry missing after install

[tzachk]

Hi support.

We have discovered that sometimes the Add/Remove entry is missing for our software.
I can find the entry in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ . The entry does not contain an UninstallString key, but even after I add it manually, I still don't get the Add/Remove entry.

We also discovered that running the installer again, does not detetct the software is already installed.

The software itself is functioning correctly.

Any ideas?

Regards,
T.

[tzachk]

Update:
I've discovered that the application is only visible in the Add/Remove to the user that installed it. Other administrators can't see it. IS there a settings to change in order to make it visible from all users?

Regardsw,
Tzach

[FrancescoT]

Dear Tzachk,

This behaviour is controlled by "ALLUSERS" IA pre-defined variable and generally, the variable setting it is handled by "StartMenu" dialog during setup interview. I suggest you to check how this variable is initialized with your script.

ALLUSERS: Initially TRUE if platform is NT, FALSE if not. Set to TRUE to perform an installation for all users and FALSE to perform an installation for the current user only.

Regards

[tzachk]

Hi Francesco,

Setting ALLUSERS to true fixed the issue.
I have an issue that you might help me with. We have previous installations made with ALLUSERS = False. Is there a way, that I can alter the registry using an admin account, that will change existing specific user install to all users install?

Regards,
T

[FrancescoT]

Dear Tzachk,

unfortunately it is not possible.
That information is part of MSI database of the installed package. It is resolved at setup execution and it can't be manipulated via registry.

Regards

[tzachk]

Hi Francesco,

Copying two registry Keys enabled me to have the uninstall appear on another user Add/Remove.
For some reason when I try to uninstall, it starts a new install instead of uninstall.
Can you tell me in which MSI database it is set?

Regards,
T.

[FrancescoT]

Dear Tzachk,

honestly, I haven't tried and I believe that what you are doing could cause other possible unwanted effects.
I can only suggest you to not use a similar approach.

By the way, the ALLUSERS property is stored internally with the MSI file.
To know the location of the cached setup source files, you should check under;
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{<GUID of the installed Package>}

Hope this helps you.

Regards

[tzachk]

Hi Francesco,

I'm not doing it out of choice.
We have one client that they install with one user, but do an upgrade with another.
Before having to do a complete uninstall of the organization, I'm trying to find another way.

Can you tell me where in the msi the ALLUSERS property is set?
The cached local files in the registry I already found. By the way, for some reason, when uninstalling the product, this key stays within the registry. Any reason why?

Regards,
Tzach

[tzachk]

Hi Francesco.

I can't find the ALLUSERS or MSIINSTALLPERUSER in the msi files, for both per user or per machine install.

Any idea?

Regards,
Tzach

[FrancescoT]

Dear Tzach,

I verified and I suppose the variable is initialized internally ... this because it is not required by the MSI engine to explicitly set it.

As reported by MSI SDK
The recommended default installation context is per-user. If ALLUSERS is not set, the installer does a per-user installation.

Anyway, even if present, how do you use it?.

If your target is to know if your actual installation as been installed per-user or not, you can verify where the cached setup source files are stored.
These files are stored under User AppData\local folder with a per-user installation (es. on on WIN 7 should be as "C:\Users\<user>\AppData\Local\{<GUID of the installed Package>}" on WIN 7).

Regards

[tzachk]

Hi Francesco,

I know where the cached files needs to be on per user and per machine.
I also know which registry entries need to be in HKCU in order to display the application in the Add/Remove.
What I'm missing is the actual ability to start an Upgrade or Remove sequence if the install was per user and the current user is not the installing user.
The current user (which is not the installing user), will get the application entry in the Add/Remove after my registry fixing, but when I click Remove, instead of starting the Remove process, the installer shall start a new install.
I need to know from where InstallAware gets the environment variable of UPGRADE and MAINTENANCE, so that I can replicate it and have the non installing user perform an Upgarde or Remove.

Thanks,
T.

[FrancescoT]

Dear Tzach,

I'm sorry to disappoint you, but I still suspect that what you are trying to do it is not feasible.

Anyway, all the informations regarding an installed package using Windows Installer are stored under Windows registry.
The MSI engine generates at runtime a GUID (... not handled by IA) which is used to keep tracks and to refer to the installed package and if I recall correctly, it is the same used with the "UninstallString" Reg key to identify the cached sourses files.

I may suggest you to have a look at the available Microsoft Windows Installer SDK documentation for more detailed information about MSI engine.

Regards

[tzachk]

Dear Francesco,

I may be after a big disapointment, but I'm still giving my best shot.
If you could let me know whats set (which registry key?)the InstallAware UPGRADE and MAINTENANCE environment variables, it would be a great help.

Regards,
Tzach.

[FrancescoT]

Dear Tzach,

that's the problem!
IA just relies to Windows Installer SDK for that and those informations, are not handled or manipulated by IA in any way.
it is the MSI engine that directly does it .
In other words, IA just executes the MSI engine which runs in maintenace mode by itself and if it is the case.

That's the reason why I suggested you to refer to Windows Installer SDK documentation. It is the only place where you can have those info.

I'm sorry but I really can't do much more.

Regards