V4 failing to uninstall MSI

Hi everyone,

Pretty much configured v4 to how I want it but it is failing to find the MSI to uninstall.

We add our own custom variables to eliminate human errors and this still works very well in v4 when we add to the array $adtSession however, the cmdlet to uninstall an installed msi install doesnt appear to be working correctly:

AppGuid = ‘{12345678SOMEGUID91011121314}’

main uninstall

Write-ADTLogEntry -Message "Uninstalling $($adtSession.Appvendor, $adtSession.Appname, $adtSession.Appversion)"
Start-ADTMsiProcess -Action 'Uninstall' `
-ProductCode "$($adtSession.AppGuid)" `
-LogFileName "$($adtSession.Appvendor, $adtSession.Appname, $adtSession.Appversion)" `
-ArgumentList '/QN'

The below also does not work:

Uninstall-ADTApplication -Name ‘Google Chrome’ -ApplicationType 'MSI'
-LogFileName “OldGoogleChromeUninstall” `
-ArgumentList ‘/QN’

I dont get any errors just the below in the toolkit log:

[Uninstall] :: Found no application based on the supplied FilterScript.

Not sure why this is happening when the other variables in the script we have customised work fine for what they need to do.

If you do something like Get-Package -Name Google* on the targeted system, can you see Google Chrome listed at all?

Yep, Google 100% installed.

Google Chrome 131.0.6778.205 msi

Are you certain your test device has has the MSI version of Chrome installed? This is my system that has the exe version, working as expected. That’s the only reason why it wouldn’t be working.

So that’s working… Are you saying it’s not when you provide a specific filter down to the ApplicationType?

I’m placing this down to a device issue as I have just tried the same thing on two other devices and the cmdlets work fine. Apologies.

I think my environmental variables are off/incorrect on the device I was testing on. Maybe one for others to look at f experiencing the same issues.

The only other thing which is unrelated I have seen are the verbose logs for the msi’s truncates the last digits of the version numbers:

Not a major thing I suppose but I thought I’d point this out.

I’ll review how the function is constructing that log name next week when I’m back home from holidays.