Msi fails to uninstall

Like mentioned here it's not a conventional msi, seems to be more of a package exe? I've gotten SCCM to detect but changing the detection method. I've been trying to find a way for sccm to properly launch the helper. I think the quickest route to a solution for this that doesn't involve rearchitecting all of both install and update from scratch and building a conventional MSI would be something like this:. Obviously a lot of unknowns in there.

And there's probably something else that needs to be done that I'm not thinking of right now. It's a surprisingly deep problem. So with that said what do you recommended using as the install verification given that currently your MSI does not actually work like an expected MSI. In reply to wildtyphoon87 from comment 9 With Firefox MSI not being a true MSI, just a hacked wrapper, my recommendation and what we will do from now on, is wrapping the exe installer with Win32 Intune MDM , with custom detection rule to check install success and firefox.

Just checking by executable name does not really do much if there is a build over build upgrade happening because it would already exist, you would also need to check for file details, I am wondering what the FF dev team is recomendingas the best solution since as of now MSI guid is not an option.

I know i could just start picking pieces of metadata at random but I would prefer to have something from the team as the next best option. In reply to wildtyphoon87 from comment Yes, the most reliable indicator is the version info on the firefox. If file version info isn't easy to check, the application. As a second alternate, the uninstall registry key that we do create contains the install path and also the version number.

To have a full MSI installer would be very helpful. Intune has a switch called "Ignore App version" but only for the MSI Method and not for Win32, so that Firefox could be up to date without always deploying a fixed version. It is really annoying to have Firefox updating itself and then Intune is installing the older version over and over again. This results in Firefox Profiles marked as not compatible. But we would like to have Firefox updating itself.

Hello, It's not understandable why Firefox is the only important software out there in the world without a working MSI package.

Its bit embarrassing. Each little Tool has a working installer, so its not a big deal. I work as admin in a small company with about 50 Workstations. We and a lot others companies using SCCM as solution to keep our environment up to date. By the way, allow autoupdate a software is never an option. Some business critical procedures will be affected and we need a careful rollout and deep testing before.

So there is no way around SCCM deployments. It's great Firefox does finally support gpo's. Now its just a small step ahead for a true and real integration for Firefox in Business enviroments.

Lets do it! If i can help, i will. I checked some internet sites and found a dozen of tools to build an msi package. Also widely used and long existing opensource tool. Bugbug thinks this bug is a regression, but please revert this change in case of error. Hi, Harald. Thanks for offering to help! If you think you can do something to improve this situation, please feel free to start working on it. I'll try to provide some more context about the current situation.

It can be a bit tricky to use, but it's doing the job. We're using this XML file that I wrote. Currently that file is generating the thin wrapper that's discussed in bug , and that route was chosen because it allowed us to get something shipped quickly that would help in at least some situations and that we could start collecting feedback on.

The feedback that I've seen has contained a surprising to me amount of complaints about this particular bug, so even though I was initially dismissive, I now think that was the wrong attitude and I'd like to get this addressed somehow. The reasons why we have the problems this bug is about are complicated, but they boil down to the surprising level of difficulty in migrating existing installations and being compatible with our existing update system which the majority of our users do need.

Above in comment 8 I laid out an idea I have about a way to kind of weave around those problems by still using our current uninstaller and having MSI launch it for us. I would simply change the file and copy it to the users install folder. This further angers the MSI Gods because the file versions are now different than the ones that were put there by the installer.

What can I do to easily remove old versions of my application and install the new? I am planning a Major revision and am expecting many headaches over a hundred or so installs otherwise. What have I failed to comprehend? Scope : Now that was a lot of questions at once. Firstly, how large is your distribution? How many machines are we talking about? FixIt : You can try this FixIt tool from Microsoft as a "quick fix", but running that on many computers manually is cumbersome to say the least.

Not sure if it can be automated. Never tried. MSI Uninstall : An MSI does not normally need the original source to uninstall, unless it erroneously calls the ResolveSource standard action or a custom action does something strange.

This old answer explains in more detail: Why does MSI require the original. Major Upgrade Uninstall : It could be that during a major upgrade there is some source resolution going on - frankly I am not sure. Did you try to invoke uninstall by its own, manually? In other words run an uninstall command only, and not install the new version on top of the old one and do a major upgrade uninstall?

I will run a test when I get a chance. Fresh Installation Location : As a workaround you could install your new version in a different place than your old version and de-couple it from the past versions.

There could be conflicts in terms of COM servers and other global registrations, but if there isn't you can just leave the old version in place potentially removing its shortcuts and leave it there.

Emergency "solution". It tries to actively maintain that installation state as explained here: Why does the MSI installer reconfigure if I delete a file? Don't fight MSI - it fights back.

Try to follow the paradigm - or you get a ride with the windmill Upload your finished setup and maybe also binaries there to see what different tools do to your binaries. Sorry if this is obvious, adding as a tip for whoever else reads this. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Access Database Engine is most commonly included as part of other applications which are interacting with Access data sources, and uninstalling Access Database Engine could impact functionality of these applications.

Before removing Access Database Engine, ensure that any applications which require this component are removed or no longer needed. The following are some additional details about using the RemoveMSI element in your configuration. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Note Support for Windows 7 ended on January 14, Note Access Database Engine is most commonly included as part of other applications which are interacting with Access data sources, and uninstalling Access Database Engine could impact functionality of these applications.

Submit and view feedback for This product This page. View all page feedback.