Aaron Parker

The app doesn't have an in-built update mechanism that we can piggy back on, and the installer is hosted on a OneDrive link which doesn't expose anything about the application...

Right now, we use this to return version numbers and downloads, which is the same call that https://welcome.webex.com uses: ```powershell irm https://welcome.webex.com/webappng/api/v1/download webexAPPFileLink : https://welcome.webex.com/client/T33L/mac/arm64/Cisco_Webex_Meetings.pkg pageBuildVersion : 41.7.2.6 webexAPPBuildVersion :...

That's not from `https://welcome.webex.com/webappng/api/v1/download` right? I don't see the same output.

Replaying the same query from the browser fails to return the expected output. E.g.: ```powershell Invoke-RestMethod -Uri "https://welcome.webex.com/webappng/api/v1/download" -Headers @{ "sec-ch-ua" = "`"Chromium`";v=`"92`", `" Not A;Brand`";v=`"99`", `"Microsoft Edge`";v=`"92`"" "sec-ch-ua-mobile" =...

This approach doesn't work either: ```powershell $params = @{ Uri = "https://welcome.webex.com/webappng/api/v1/download" UserAgent = "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36 Edg/92.0.902.73" Headers = @{"referer"...

Those links are returning binary data (e.g. https://repository.eset.com/v1/com/eset/apps/business/esa/windows/metadata). The JSON is embeded in it, but extracting that JSON will be a challenge.

The display names for these folders is configure with hidden file named `desktop.ini`. That file probably exists in each folder and has an entry for the display name for the...

Excellent. Thanks for posting the solution

In which application? Check your browser settings

Are the Windows Installer GUIDs not matching what's on the client?