Windows Installer does not remove previous version

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.
dominicwongAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AndyAinscowFreelance programmer / ConsultantCommented:
>>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.
Vadim RappCommented:
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.
Vadim RappCommented:
> 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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Why Diversity in Tech Matters

Kesha Williams, certified professional and software developer, explores the imbalance of diversity in the world of technology -- especially when it comes to hiring women. She showcases ways she's making a difference through the Colors of STEM program.

AndyAinscowFreelance programmer / ConsultantCommented:
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.
AndyAinscowFreelance programmer / ConsultantCommented:
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.  :-((
dominicwongAuthor Commented:
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.
dominicwongAuthor Commented:
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.
dominicwongAuthor Commented:
Thanks Andy and vadimrapp1 for your prompt responses and help. Much appreciated.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Installation

From novice to tech pro — start learning today.