[Package Issue]: Zoom.Zoom Manifest Issue for MSI

[PckgrBot]

Please confirm these before moving forward

• I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
• I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue

Installation issue.

Brief description of your issue

Zoom manifest is not working correctly, it thinks that the latest version of MSI is installed when the previous version is.

Steps to reproduce

Install previous version of Zoom MSI

Actual behavior

Reports as latest version installed

Expected behavior

Should show the actual version installed.

Environment

N/A

Screenshots and Logs

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• [Package Issue]: Zoom.Zoom (#68659), similarity score: 0.77
• [Package Issue]: Zoom.Zoom (#112413), similarity score: 0.77
• [Package Issue]: Zoom.Zoom Incorrect Installed Version Reported (#88334), similarity score: 0.73

Closed similar issues:

• [Package Issue]: Zoom.Zoom (#117708), similarity score: 0.77
• Winget installs zoom's installs through .msi package (#15419), similarity score: 0.73

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[SpecterShell]

Is it because the manifest (5.17.29988) of this version has a wrong version for the MSI installers?

[PckgrBot]

I tested with my own winget repo and when I use the other display version format it seems to understand which version is installed.

I also noticed in the comments field it shows the same version format.

@Trenly any chance you can look at this?

[Trenly]

@PckgrBot - DisplayVersion must match what is written to control panel exactly in order for the mapping to be correct. I raised PRs for the 2 latest versions to see if it fixes the issue. It seems like many of the older versions also have this issue though, so if the two PR's fix the issue with the latest versions, it would be a good idea to go back and fix the previous manifests

[Trenly]

Seems theres a bigger issue at play here -

• VersionRange causes issues when packages have multiple DisplayVersion winget-cli#4125

I think we have three options -

1. Do nothing, and leave the bug as it is
2. Split the package into Zoom.Zoom.exe and Zoom.Zoom.msi
3. Remove one of the installer types from the manifest entirely

[SpecterShell]

Seems theres a bigger issue at play here -

* [VersionRange causes issues when packages have multiple DisplayVersion winget-cli#4125](https://github.com/microsoft/winget-cli/issues/4125)

I think we have three options -

1. Do nothing, and leave the bug as it is

2. Split the package into Zoom.Zoom.exe and Zoom.Zoom.msi

3. Remove one of the installer types from the manifest entirely

4. Change the PackageVersion to the DisplayVersion of MSI installers.

[Trenly]

4. Change the PackageVersion to the DisplayVersion of MSI installers.

I considered that, but think that it would still be broken -

• Version Range not taking into account Package Versions without DisplayVersion winget-cli#2503

[PckgrBot]

So will this be remaining a bug?

[SpecterShell]

Well now I prefer to move the MSI installers to a separate package like Zoom.Zoom.MSI.