/build/static/layout/Breadcrumb_cap_w.png
06/09/2017 988 views
I am doing upgrade in my MSI package to uninstall previous version with the help of upgrade code.upgrade is happening but previous application Product code remains in registry.And all files are modify.please let me know the reason.

Answer Summary:
0 Comments   [ + ] Show comments

Comments


Answer Chosen by the Author

1
Can you please specify:
1) Which registry keys exactly have remained in the registry?
2) Whether or not the product сodes of the old and the new package are similar? Could it be that it is the new package's product code in the registry?
3) Does your new package has "RemoveExistingProducts" Action (https://msdn.microsoft.com/en-us/library/windows/desktop/aa371197(v=vs.85).aspx) in the InstallExecuteSequence table? Maybe the upgrade did not happen and the new package simply overwrote the old files with the new ones?
4) Finally, check if the component, to which those remained registry keys are linked, does not have the Permanent (16) attribute set
Answered 06/12/2017 by: pace-support
2nd Degree Black Belt

  • Sorry for delay response, i need check 3rd & 4th Point i will get back to you.
  • 1.Old app reg key remaining
    2.Different product codes not similar
    3.I need to check i will get back to you
    4.I need to check i will get back to you

All Answers

0
As ever, you should log the installation. You can then check the state of every feature, component and action.
Answered 06/12/2017 by: VBScab
Red Belt

  • What exactly i need check in uninstall log file to confirm whether uninstall is success or not which action is it Remove Existing product?Please confirm.
0
My friend, if you don't know how to read an installation log, you have serious problems. How are you ever going to debug your packages when they fail, like...errrr....now?

You need to determine what installation state the various components were in and what the package did to them when it ran.

One thing I meant to add in my earlier post was to ask whether the UpgradeCode is the same in both packages.
Answered 06/19/2017 by: VBScab
Red Belt

  • yes same only.Thanks for your support. I got the answer for the above issue.Why registry key remaining here is Old application is installed by sccm server in user assigned mode which means when ever specific user logon it will install application default.And in software center installed & uninstall button will be disabled.when my package deploy it will override application files not the registry key.
    In these cases we need to decommission old application from sccm server than only we can achieve clean uninstall.
  • can you please help me how to go through log file step by step actions will normally perform in all the msi log files
0
RemoveExistingProducts is an action in the InstallExecute sequence which removes a previous app as defined in the Upgrade table. For the most reliable results it needs to be sequenced between Install Validate and InstallInitialize. If you are unfamiliar with this information then you need to get some help from a more experienced colleague or use Google to research these terms.
Answered 06/19/2017 by: EdT
Red Belt

0
RemoveExistingProducts is an action in the InstallExecute sequence which removes a previous app as defined in the Upgrade table. For the most reliable results it needs to be sequenced between Install Validate and InstallInitialize. If you are unfamiliar with this information then you need to get some help from a more experienced colleague or use Google to research these terms.
Answered 06/19/2017 by: EdT
Red Belt

0
I got the answer for the above issue.Why registry key remaining here is Old application is installed by sccm server  in user assigned mode  which means when ever specific user logon it will install application default.And in software center installed & uninstall button will be disabled.when my package deploy it will override application files not the registry key.
In these cases we need to decommission old application from sccm server than only we can achieve clean uninstall.
Answered 06/20/2017 by: @Imran9
Yellow Belt