Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Windows Installer does not remove previous version

Posted on 2014-01-14
8
Medium Priority
?
739 Views
Last Modified: 2014-01-14
Hi experts
I had a problem with my Windows Installer. It does not remove the previous installed version.

On the 'Properties' of the Installer:
I'd updated the 'Version', and click 'Yes' when prompted to change 'ProductCode'.
I had the 'RemovePreviousVersion' set to 'True'.
I had the 'DetectNewerInstalledVersion' set to 'True'.
I had the 'UpgradeCode' remain unchanged.

Could someone point to me what I am missing?

Thanks in advance.

PS. I am using VS2008.
I didn't have this problem before until I moved everything to a new HD. So something might have missed out from my settings.
0
Comment
Question by:dominicwong
  • 3
  • 3
  • 2
8 Comments
 
LVL 45

Expert Comment

by:AndyAinscow
ID: 39778568
>>and click 'Yes' when prompted to change 'ProductCode'.

I think you should have said no to that - the code should be how a previous version is identified.  Try setting the code to the value you had before and see if that will remove the previous version upon installation.
0
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 39779231
Please post detailed installation log:

msiexec /l*v c:\installation.log /i <path>\installation.msi

@AndyAinscow, the product code in question applies to this version, not previous version. Previous version is identified by upgrade code, i.e. Installer searches for my upgrade code*; finds product code of the previous version, and then uninstalls product with that found product code.

*) more accurately - for the upgrade code specified in UPGRADE table. There can be several, so it's possible to upgrade several different products. It's also possible to upgrade completely different product, if you know its upgrade code.
0
 
LVL 40

Accepted Solution

by:
Vadim Rapp earned 1000 total points
ID: 39779252
> I didn't have this problem before until I moved everything to a new HD

Always try things on clean machine. The best is to have virtual machine with saved snapshot, representing just-installed state, which you can always restore in one click. When you test on machine "contaminated" by previous installations (especially imperfect ones made in the course of development), you never know whether the problem is in the new installation, or in the those previous ones, and all this creates an infinite amount of difficult problems. So you may in fact disregard my prev. comment about the installation log, with the best luck we will only find one of those 1,000 reasons introduced by previous installations. Try on clean v.m., post if you still have a problem.
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
LVL 45

Assisted Solution

by:AndyAinscow
AndyAinscow earned 1000 total points
ID: 39779428
Hmmm.
From the help files (for my windows installer):

Product Code

Every Windows Installer installation must have a unique product code, which is used as the principal identification for the application.



I have had this behaviour described here when I did change the product code for an existing app by mistake.
0
 
LVL 45

Expert Comment

by:AndyAinscow
ID: 39779443
Ooops - I've done some more digging.
My memory was wrong, I had changed both product and upgrade codes when things went wrong.

Ignore my last comment.  :-((
0
 

Author Comment

by:dominicwong
ID: 39780693
Thanks AndyAinscow and vadimrapp1.
What happened was my old HD was corrupted so I couldn't easily go back to examine.
I reckon something might be missing in my Installer project as I'd experimented it by building two versions. The newer one doesn't uninstall the older one.
I need to do more digging.
0
 

Author Comment

by:dominicwong
ID: 39780751
I managed to resolve this issue.

There was a static red-colour icon next to the icon file under the Installer project.
The path of this icon file that had pointed to an old location. This icon file was referenced by the 'User's Program Men' under the 'File System (Installer)'.

There wasn't any error when I built the Installer project to produce installer files. I can't understand why an icon file could lead to this issue. But fixing the path of this icon file managed to resolve this issue.
0
 

Author Closing Comment

by:dominicwong
ID: 39780756
Thanks Andy and vadimrapp1 for your prompt responses and help. Much appreciated.
0

Featured Post

Ask an Anonymous Question!

Don't feel intimidated by what you don't know. Ask your question anonymously. It's easy! Learn more and upgrade.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Exception Handling is in the core of any application that is able to dignify its name. In this article, I'll guide you through the process of writing a DRY (Don't Repeat Yourself) Exception Handling mechanism, using Aspect Oriented Programming.
Simulator games are perfect for generating sample realistic data streams, especially for learning data analysis. It is even useful for demoing offerings such as Azure stream analytics, PowerBI etc.
This course is ideal for IT System Administrators working with VMware vSphere and its associated products in their company infrastructure. This course teaches you how to install and maintain this virtualization technology to store data, prevent vuln…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…

916 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question