Opened on 06/02/2014 at 10:16:26 AM
Closed on 06/16/2014 at 10:32:23 AM
Last modified on 07/15/2014 at 05:04:42 PM
#604 closed defect (fixed)
ABP for IE11 cannot be uninstalled via the install file
Reported by: | vickyyu | Assignee: | oleksandr |
---|---|---|---|
Priority: | Unknown | Milestone: | Adblock-Plus-1.2-for-Internet-Explorer |
Module: | Adblock-Plus-for-Internet-Explorer | Keywords: | ie_devbuild_1.2 |
Cc: | Blocked By: | ||
Blocking: | Platform: | Internet Explorer | |
Ready: | yes | Confidential: | no |
Tester: | Verified working: | no | |
Review URL(s): |
Description (last modified by vickyyu)
Environment
IE 11.0.9600.17107 (System language is Chinese)
Windows 8.1 64 bit
How to reproduce
1.Install ABP for IE 1.2.
2.Run it on IE.
3.Go to the download folder where the install file located.
4.Click uninstall on the file.
Observed behaviour
After clicking the "uninstall" button, when open IE again, ABP icon is still showing on the browser,it is only possible to uninstall it via control panel - apps & programs
Expected behaviour
It is supposed to be uninstalled after clicking uninstall on the install file
Attachments (0)
Change History (8)
comment:1 Changed on 06/02/2014 at 10:31:49 AM by philll
- Keywords devbuild_1.2 added
comment:3 Changed on 06/02/2014 at 11:57:58 AM by philll
- Owner set to eric@adblockplus.org
comment:4 Changed on 06/02/2014 at 01:13:08 PM by oleksandr
- Owner changed from eric@adblockplus.org to oleksandr
comment:5 Changed on 06/03/2014 at 08:07:19 PM by eric@adblockplus.org
comment:6 Changed on 06/12/2014 at 09:04:41 AM by philll
- Keywords ie_devbuild_1.2 added; devbuild_1.2 removed
comment:7 Changed on 06/16/2014 at 10:32:23 AM by oleksandr
- Resolution set to fixed
- Status changed from new to closed
comment:8 Changed on 07/15/2014 at 05:04:42 PM by trev
- Milestone set to Adblock-Plus-for-Internet-Explorer-1.2
- Platform set to Internet Explorer
Note: See
TracTickets for help on using
tickets.
The way that the WiX tool 'burn' works, it creates its own installation ID, in addition to the ones found in the MSI's under its control. I see two ways of eliminating this behavior:
-- Stop using 'burn' (already been under discussion).
-- Disable the individual MSI's from presenting an uninstall option on the context menu. I'm not sure that's possible.