If this is not the right group for this, please suggest where to ask.
A number of Microsoft programs (Windows Live Suite, Intellipoint drivers, Office, others) install "microsoft application error reporting" (dw20shared.msi - {95120000-00B9-0409-0000-0000000FF1CE})
They do not remove it on uninstall. Manually removing it (from the msi or "msiexec /x {95120000-00B9-0409-0000-0000000FF1CE}") also fails.
> If this is not the right group for this, please suggest where to ask.
> A number of Microsoft programs (Windows Live Suite, Intellipoint drivers, > Office, others) install "microsoft application error reporting" > (dw20shared.msi - {95120000-00B9-0409-0000-0000000FF1CE})
> They do not remove it on uninstall. Manually removing it (from the msi or > "msiexec /x {95120000-00B9-0409-0000-0000000FF1CE}") also fails.
Maybe the better question is why install software that misbehaves in the first place?
If it were me, and I *really* had some reason to install MS software to begin with, I'd first test to make sure the programs will work OK without the error reporting. If it's a service then you could first try disabling it. If your "Live Suite" or other software won't run with the service disabled then you have another issue. (Also, those programs might start the service themselves.)
Next, one option is to write your own uninstaller based on the MSI content. The details should be all in there, both Reg. settings and files added. But since this is MS software, if you're on XP or later and have not removed Windows File Protection then you may be blocked from uninstalling files.
Another option would be to edit the MSI file. That may or may not be possible. Offhand I don't know how to mark it -- or unmark it -- for no uninstall. One hint I see in the MSI help is that to prevent a file being uninstalled one can "set msidbComponentAttributesPermanent in the Attributes column of the Component table".
Either way, it's likely to be a long, tedious job.
> If this is not the right group for this, please suggest where to ask.
> A number of Microsoft programs (Windows Live Suite, Intellipoint drivers, > Office, others) install "microsoft application error reporting" > (dw20shared.msi - {95120000-00B9-0409-0000-0000000FF1CE})
> They do not remove it on uninstall. Manually removing it (from the msi or > "msiexec /x {95120000-00B9-0409-0000-0000000FF1CE}") also fails.
> As this is a system component I'd leave it installed and disable Error > Reporting using group policies.
It is not a system component, the system (XP) does not install it and can do just fine without it. It is a shared MS component, that can be used by many different apps but that's not a reason why it shouldn't be uninstallable.
> Another option would be to edit the MSI file. That > may or may not be possible. Offhand I don't know how > to mark it -- or unmark it -- for no uninstall. One hint > I see in the MSI help is that to prevent a file being > uninstalled one can > "set msidbComponentAttributesPermanent in the > Attributes column of the Component table".
no component had msidbComponentAttributesPermanent flasg set. Setting ARPNOREMOVE to 0 in the properties table also didn't help.
> no component had msidbComponentAttributesPermanent flasg set. Setting > ARPNOREMOVE to 0 in the properties table also didn't help.
Then it looks like your only other option would be to dissect the MSI and write an uninstaller. From what I can see it seems to mainly add a COM object and some Registry settings.
The notable files are several VC runtimes and these:
DWTRIG20.EXE (appears to be an ActiveX EXE) DWINTL20.DLL DWDCW20.DLL DW20.EXE
If you want to disable it you might be able to just unregister the Ax EXE, but that would be somewhat reckless. :) It seems to be tied into PCHealth and Dr. Watson. It would take some work to figure out exactly what you can and should change to make a clean uninstall. But the data is all in the MSI. If you're ambitious see the unpacker here: www.jsware.net/jsware/msicode.php5 In the unpacker download is a sample set of scripts for auto-creating a VBScript-based installer from the data in an MSI file. If you have an installer then you have an uninstaller.
Do you really want to go to all that trouble, though? Can't you just disable Dr. Watson, error reporting, or whatever other crap is running in connection with the package that you don't want?
|
