I've made a MSI, (I applied a MST on the MSI and saved is with Orca as a new MSI)
When I install the MSI on PC 1 as user A it will work just fine. But when I logon to PC 2 an user A the MSI wants to install again.

Also when I logon on PC 1 as user B the MSI wants to install again..

Especially when ik install another MSI, de first thing Windows Installer wants to do is to complete the first MSI (Which won't work beacause the source location/files is not available)

Has anyone encoutered this issue?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


You can add a path in your mst file specifying the location of the source files. I beleive it is SOURCEPATH that you should be looking for, but I am used to doing it in Installshield tuner which has it already laid out for me.
Answered 06/25/2004 by: cdupuis
Third Degree Green Belt

Please log in to comment
Does you msi have any HKCU keys in it?

If it does then it will try to install those keys for every user that logs into that PC.

I dont know why its installing on PC2 because I dontg know enough about the environment.

How did you deploy it and what sort of network are you using?
Answered 06/25/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
I found the solution myself.

There is an event in the eventvwr stating that a "detection of product xxx-xx-xx failed". In the MSI file --> component table --> xxx-xx-xx --> remove the keypath entry of the troubled component.

Works perfectly now!!


Jm Brockhoff
Packaged 100+ MSI's + EXE's
Answered 06/28/2004 by: subsense
Purple Belt

Please log in to comment