01/03/2005 2299 views
Hello everybody!

I got a heavy problem with our AD: I had a MSI-file set up for distribution on the network and suddenly got a better program for the case we needed it for. It was only for a small group of users and I hoped none of the affected machines would have downloaded it. But actually some did and to all my luck the installer was broken in some way: whenever the user had the file-extension coming up in his explorer, a windows Installer window would pop up and ask him for the (now missing) isntaller files on the network. This is quite annoying, because we don't actually have the installer file anymore. Can somebody please help me and tell me, who I can prevent the system from trying to install the program? It is really annoying when you have to click away a window every few minutes...

Thanks for your help,

0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

Timmah...your in trouble.

Your best bet is to create a script or msi package to remove the application as part of its install. You need to have your package remove all the keys installed originally.

Not easy but I have done it before. Good luck.
Answered 01/07/2005 by: MSIMaker
Second Degree Black Belt

Yeah, luck seems to be what I actually need... Do you still have some kind of "blueprint" for me? The thing is, that this damn program isn't already installed and still keeps asking about the install-package...

I am really stuck...

Thanks a lot for your help,

Answered 01/07/2005 by: Timmah
Yellow Belt

I hope I understood your problem ;-) then... try...

msicuu2.exe (Windows Installer Clean Up Install) d/l @ MS Office update site would help.....
Answered 01/07/2005 by: olivier
Orange Senior Belt

I think he has a totally broken source path link.

Ok start here.

Find a machine that you can reproduce the error on and do it. Hit the extension. You will get the Windows Installer service trying to repair the app and fail. No prob just cancel it.

Now open EventViewer.

In there you will see the error. Under Windows Installer error.

Eventviewer will tell you exactly what is trying to be repaired. You will get a Product GUID and also a component GUID.

You can use these numbers to remove the keys from the registry so that it stops self repairing.
Answered 01/07/2005 by: MSIMaker
Second Degree Black Belt