microsoft / microsoft/winget-pkgs

[Package Issue]: Zoom.Zoom

Open
#144,460 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

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

No applicable update found.

Brief description of your issue

The installed machine wide .msi package of Zoom that I install when using the --scope machine flag doesn't show up when I run winget upgrade (even though I know that a newer version exists).

I think that this behavior occurs because for some reason the version number notation of the .msi installed package differs from the WinGet repository (WinGet: 5.17.11.34827 / Registry displayversion for .msi: 5.17.34827 for example).

However, since I want to deploy the machine wide package, I now have to uninstall the current version first and then re-install it.

Steps to reproduce

winget install --exact --id Zoom.Zoom --accept-package-agreements --accept-source-agreements --architecture x64 --scope machine --version %old version number%

installs

winget upgrade

package not listed even though a new version is available

Actual behavior

winget upgrade

package not listed even though a new version is available

Expected behavior

winget upgrade

upgrade should be available

Environment
PS C:\Windows\system32> winget --info
Windows Package Manager v1.7.10661
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22631.3155
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.10661.0

Winget Directories                 
-----------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links               
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
Screenshots and Logs

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the machine-scope install and winget upgrade commands from the issue, then compare the installed Zoom MSI version with the repository metadata for Zoom.Zoom. Trace how the client matches installed MSI versions to package versions; done means the newer Zoom version appears in winget upgrade without uninstalling the current installation.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.