Skip to main content

Troubleshoot an MSI uninstall

When trying to uninstall ElasticSearch through Add/Remove Programs in Windows, the uninstall silently failed. No error messages, no information in the Event Viewer, nothing...

Let’s see how we can investigate what is going wrong. Therefore we’ll try to do the uninstall through the commandline instead of using the Add/Remove Programs feature in Windows.

Uninstall an MSI from the commandline

The command we need to use is msiexec. This can be used to install an MSI program. Of course we want to do an uninstall so we need to include the /x or /uninstall parameter.

If you have the MSI file available you can use the following command:

msiexec.exe /x “c:\elasticsearch.msi”

If you don’t have the MSI file anymore you can do an uninstall using the Product GUID (I’ll show you how to get the product GUID below):

msiexec.exe /x {11111111-1111-1111-1111-11111111111}

Find the Product GUID of an installed Program

There are multiple ways to get the Product GUID of the product you want to uninstall.

I have used the following Powershell “one-liner”:

 

The output will look like this:

Troubleshoot a failing uninstall

Of course in our case we want to troubleshoot the uninstall process. Therefore we can include extra parameters to write the output of the uninstall process to a log file:

msiexec.exe /x {11111111-1111-1111-1111-11111111111} /L*V! "C:\elasticsearchuninstall.log"

This allowed me to investigate why the uninstall failed. I’ll share my findings tomorrow…

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...