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.

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...