Re: [WiX-users] Uninstalling bundle with broken BA
2014-09-08 16:44 GMT-03:00 Hoover, Jacob jacob.hoo...@greenheck.com:
As for the borked bundle, I'm not certain if you can easily assign the bundle
Id, but that’s what I would try doing
(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-UpgradeCode-td7578845.html).
I'm guessing you'd have to hack on WiX to get it to happen, but if you
could assign the same id as the original, you should be able to overwrite the
one in the cache and uninstall it.
I tried to change the bundle ID with a hex editor, but it turns out
the ID is also present in a compressed embedded XML, in
/BootstrapperApplicationData/WixBundleProperties/@Id, and I don't know
how to replace that. Hacking the WiX compiler to set the bundle ID
sounds like a tempting option, but I haven't yet managed to even
compile WiX.
It may just be easier to uninstall the packages your bundle installed
manually, then manually remove the bundle from the package cache and ARP.
...so I took this approach. Uninstalled the packages with msiexec,
then deleted the bundle and packages from the package cache, and
deleted the ARP entry and the registry keys related to dependency
providers (whatever that is) with my bundle ID.
--
Nicolás
-Original Message-
From: Sascha Sertel [mailto:sascha.ser...@gmail.com]
Sent: Monday, September 08, 2014 2:11 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Uninstalling bundle with broken BA
MsiZap will wipe out anything that is related to the product code. Run it
once and you will see the giant output of all the registry and file locations
it goes through.
As far as other bundle left-over go, you should be able to clear those out
yourself from paths like C:\Users\username\AppData\Local\Package Cache
C:\Users\username\AppData\Local\Temp
C:\Config,msi
Paths will be different on XP obviously, but you know what I mean. There are
also package cache locations under C:\Windows, you can see in the log file
where it's caching the package.
// Sascha
On Mon, Sep 8, 2014 at 11:55 AM, Nicolás Alvarez nicolas.alva...@gmail.com
wrote:
I can properly uninstall the MSIs via msiexec /x {GUID}. The problem
is removing the stuff left behind by Burn, such as the cached bundle
and packages. I doubt msizap knows anything about bootstrappers...
El lunes, 8 de septiembre de 2014, Sascha Sertel
sascha.ser...@gmail.com
escribió:
Let me introduce you to your new best friend: MsiZap
http://msdn.microsoft.com/en-us/library/aa370523(v=vs.85).aspx (
http://msdn.microsoft.com/en-us/library/aa370523(v=vs.85).aspx)
While I was doing custom BA development MsiZap helped me out of a
few botched installations where I was stuck in the same situation
and
couldn't
uninstall. As long as you have your product GUID MsiZap can clean up
everything left behind so you can start off fresh.
I usually call MsiZap like this:
MsiZap.exe T! {GUID}
Hope it helps!
// Sascha
On Sun, Sep 7, 2014 at 8:08 PM, Nicolás Alvarez
nicolas.alva...@gmail.com
javascript:;
wrote:
Hi,
I was experimenting with a custom BA, and I installed my bundle
with it. Now I can't uninstall it because my simplistic BA has no
way to plan uninstallation.
I can't just build a new bundle with the wixstdba because it would
have a new bundle ID, so it offers me to install again, not to
uninstall. If I go ahead and install it again with wixstdba, I get
two entries in ARP, and the old entry is still launching my custom
and broken BA.
What do I do now? :(
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstalling bundle with broken BA
Let me introduce you to your new best friend: MsiZap
http://msdn.microsoft.com/en-us/library/aa370523(v=vs.85).aspx (
http://msdn.microsoft.com/en-us/library/aa370523(v=vs.85).aspx)
While I was doing custom BA development MsiZap helped me out of a few
botched installations where I was stuck in the same situation and couldn't
uninstall. As long as you have your product GUID MsiZap can clean up
everything left behind so you can start off fresh.
I usually call MsiZap like this:
MsiZap.exe T! {GUID}
Hope it helps!
// Sascha
On Sun, Sep 7, 2014 at 8:08 PM, Nicolás Alvarez nicolas.alva...@gmail.com
wrote:
Hi,
I was experimenting with a custom BA, and I installed my bundle with
it. Now I can't uninstall it because my simplistic BA has no way to
plan uninstallation.
I can't just build a new bundle with the wixstdba because it would
have a new bundle ID, so it offers me to install again, not to
uninstall. If I go ahead and install it again with wixstdba, I get two
entries in ARP, and the old entry is still launching my custom and
broken BA.
What do I do now? :(
--
Nicolás
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstalling bundle with broken BA
I can properly uninstall the MSIs via msiexec /x {GUID}. The problem is
removing the stuff left behind by Burn, such as the cached bundle and
packages. I doubt msizap knows anything about bootstrappers...
El lunes, 8 de septiembre de 2014, Sascha Sertel sascha.ser...@gmail.com
escribió:
Let me introduce you to your new best friend: MsiZap
http://msdn.microsoft.com/en-us/library/aa370523(v=vs.85).aspx (
http://msdn.microsoft.com/en-us/library/aa370523(v=vs.85).aspx)
While I was doing custom BA development MsiZap helped me out of a few
botched installations where I was stuck in the same situation and couldn't
uninstall. As long as you have your product GUID MsiZap can clean up
everything left behind so you can start off fresh.
I usually call MsiZap like this:
MsiZap.exe T! {GUID}
Hope it helps!
// Sascha
On Sun, Sep 7, 2014 at 8:08 PM, Nicolás Alvarez nicolas.alva...@gmail.com
javascript:;
wrote:
Hi,
I was experimenting with a custom BA, and I installed my bundle with
it. Now I can't uninstall it because my simplistic BA has no way to
plan uninstallation.
I can't just build a new bundle with the wixstdba because it would
have a new bundle ID, so it offers me to install again, not to
uninstall. If I go ahead and install it again with wixstdba, I get two
entries in ARP, and the old entry is still launching my custom and
broken BA.
What do I do now? :(
--
Nicolás
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net javascript:;
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net javascript:;
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Nicolás
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstalling bundle with broken BA
MsiZap will wipe out anything that is related to the product code. Run it
once and you will see the giant output of all the registry and file
locations it goes through.
As far as other bundle left-over go, you should be able to clear those out
yourself from paths like
C:\Users\username\AppData\Local\Package Cache
C:\Users\username\AppData\Local\Temp
C:\Config,msi
Paths will be different on XP obviously, but you know what I mean. There
are also package cache locations under C:\Windows, you can see in the log
file where it's caching the package.
// Sascha
On Mon, Sep 8, 2014 at 11:55 AM, Nicolás Alvarez nicolas.alva...@gmail.com
wrote:
I can properly uninstall the MSIs via msiexec /x {GUID}. The problem is
removing the stuff left behind by Burn, such as the cached bundle and
packages. I doubt msizap knows anything about bootstrappers...
El lunes, 8 de septiembre de 2014, Sascha Sertel sascha.ser...@gmail.com
escribió:
Let me introduce you to your new best friend: MsiZap
http://msdn.microsoft.com/en-us/library/aa370523(v=vs.85).aspx (
http://msdn.microsoft.com/en-us/library/aa370523(v=vs.85).aspx)
While I was doing custom BA development MsiZap helped me out of a few
botched installations where I was stuck in the same situation and
couldn't
uninstall. As long as you have your product GUID MsiZap can clean up
everything left behind so you can start off fresh.
I usually call MsiZap like this:
MsiZap.exe T! {GUID}
Hope it helps!
// Sascha
On Sun, Sep 7, 2014 at 8:08 PM, Nicolás Alvarez
nicolas.alva...@gmail.com
javascript:;
wrote:
Hi,
I was experimenting with a custom BA, and I installed my bundle with
it. Now I can't uninstall it because my simplistic BA has no way to
plan uninstallation.
I can't just build a new bundle with the wixstdba because it would
have a new bundle ID, so it offers me to install again, not to
uninstall. If I go ahead and install it again with wixstdba, I get two
entries in ARP, and the old entry is still launching my custom and
broken BA.
What do I do now? :(
--
Nicolás
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net javascript:;
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net javascript:;
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Nicolás
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstalling bundle with broken BA
MsiZap is evil.. DON'T use it. If you did have a borked MSI, fix the MSI and
then use Orca to match the needed ID's. From there you can recache the fixed
MSI and do a proper uninstall.
As for the borked bundle, I'm not certain if you can easily assign the bundle
Id, but that’s what I would try doing
(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-UpgradeCode-td7578845.html).
I'm guessing you'd have to hack on WiX to get it to happen, but if you could
assign the same id as the original, you should be able to overwrite the one in
the cache and uninstall it.
It may just be easier to uninstall the packages your bundle installed manually,
then manually remove the bundle from the package cache and ARP.
-Original Message-
From: Sascha Sertel [mailto:sascha.ser...@gmail.com]
Sent: Monday, September 08, 2014 2:11 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Uninstalling bundle with broken BA
MsiZap will wipe out anything that is related to the product code. Run it once
and you will see the giant output of all the registry and file locations it
goes through.
As far as other bundle left-over go, you should be able to clear those out
yourself from paths like C:\Users\username\AppData\Local\Package Cache
C:\Users\username\AppData\Local\Temp
C:\Config,msi
Paths will be different on XP obviously, but you know what I mean. There are
also package cache locations under C:\Windows, you can see in the log file
where it's caching the package.
// Sascha
On Mon, Sep 8, 2014 at 11:55 AM, Nicolás Alvarez nicolas.alva...@gmail.com
wrote:
I can properly uninstall the MSIs via msiexec /x {GUID}. The problem
is removing the stuff left behind by Burn, such as the cached bundle
and packages. I doubt msizap knows anything about bootstrappers...
El lunes, 8 de septiembre de 2014, Sascha Sertel
sascha.ser...@gmail.com
escribió:
Let me introduce you to your new best friend: MsiZap
http://msdn.microsoft.com/en-us/library/aa370523(v=vs.85).aspx (
http://msdn.microsoft.com/en-us/library/aa370523(v=vs.85).aspx)
While I was doing custom BA development MsiZap helped me out of a
few botched installations where I was stuck in the same situation
and
couldn't
uninstall. As long as you have your product GUID MsiZap can clean up
everything left behind so you can start off fresh.
I usually call MsiZap like this:
MsiZap.exe T! {GUID}
Hope it helps!
// Sascha
On Sun, Sep 7, 2014 at 8:08 PM, Nicolás Alvarez
nicolas.alva...@gmail.com
javascript:;
wrote:
Hi,
I was experimenting with a custom BA, and I installed my bundle
with it. Now I can't uninstall it because my simplistic BA has no
way to plan uninstallation.
I can't just build a new bundle with the wixstdba because it would
have a new bundle ID, so it offers me to install again, not to
uninstall. If I go ahead and install it again with wixstdba, I get
two entries in ARP, and the old entry is still launching my custom
and broken BA.
What do I do now? :(
--
Nicolás
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version
control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.
clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net javascript:;
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.
clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net javascript:;
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Nicolás
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.
clktrk ___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
[WiX-users] Uninstalling bundle with broken BA
Hi, I was experimenting with a custom BA, and I installed my bundle with it. Now I can't uninstall it because my simplistic BA has no way to plan uninstallation. I can't just build a new bundle with the wixstdba because it would have a new bundle ID, so it offers me to install again, not to uninstall. If I go ahead and install it again with wixstdba, I get two entries in ARP, and the old entry is still launching my custom and broken BA. What do I do now? :( -- Nicolás -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
