Re: [WiX-users] Fw: Uninstall a cached msi

[Wilson, P. <Phi...@wo...>]

I wouldn't exactly recommend it either, but if you can't re-create the
MSI file (because it's not even yours or it's been on your system for
months and you can't re-create it) then it's almost the only solution. I
say "almost" because there's always MsiZap assuming that a) you trust it
and b) you don't care that it doesn't remove everything.=20
=20
Given that MsiGetProductInfo tells you exactly where it is
(INSTALLPROPERTY_LOCALPACKAGE) I wouldn't go quite so far as calling it
an "undocumented data store".=20

Phil Wilson=20


________________________________

From: Rob Mensching [mailto:Rob...@mi...]=20
Sent: Thursday, October 19, 2006 11:02 AM
To: Wilson, Phil; Wix-user mailingList
Subject: RE: Re: [WiX-users] Fw: Uninstall a cached msi



Yeah, and I would never recommend people going into an undocumented data
store and start tweaking stuff they find there.

=20

From: wix...@li...
[mailto:wix...@li...] On Behalf Of Wilson,
Phil
Sent: Thursday, October 19, 2006 8:09 AM
To: Wix-user mailingList
Subject: Re: [WiX-users] Fw: Uninstall a cached msi

=20

I've fixed these problems with a hack - find the cached MSI file in
<Windows>\installer and edit it with Orca to change the condition on the
offending custom action (in the execute sequence I assume) to 0.=20

=20

Phil Wilson=20

________________________________

From: wix...@li...
[mailto:wix...@li...] On Behalf Of Rob
Mensching
Sent: Thursday, October 19, 2006 8:02 AM
To: Rai Wasif; Wix-user mailingList
Subject: Re: [WiX-users] Fw: Uninstall a cached msi

The best way is to create a fixed MSI with the same ProductCode and
Version, then do a recache/reinstall.

=20

msiexec /fv fixed.msi

=20

That will end up replacing the bad MSI so you can attempt uninstall
again.