Well actually it is the other way around! I kick off an app and the .msi starts.
Main Topics
Browse All TopicsHi.
I have a strange problem. When I click on a prgram to run it, a .msi package for another installed program tries to install that package. After cancelling 2-3 times, the original selected program starts up.
The only thing I have installed recently is UniBlue Soy Eraser, but that is not running.
It is not on every program this happens. I have looked at the shortcut properties of the program, and they point to the right .exe file.
Can anybody tell me what is happening and how to cure this?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Try using this to narrow down the problem:
http://www.winhelponline.c
Business Accounts
Answer for Membership
by: slam69Posted on 2007-12-19 at 04:54:35ID: 20499127
Hi,
It is likely there is a shared dll that both apps use and so when you kick off teh msi it somehow gets back to teh other application. this is a common fault when upgrading to visual studio 2005 and sap is already installed. i would suggest removing the already installed app, installing the new app and then reinsatlling the other app over the top. this should work for you