winget-cli: Winget reporting the wrong version for some apps

Brief description of your issue

Winget shows the wrong version for some apps and trys to upgrade when they are fully up to date as showen below

Steps to reproduce

Download Safing Portmaster than run “winget upgrade”

Expected behavior

It to show the correct version

Actual behavior

It shows the wrong version and trys to upgrade even when up to date Screenshot 2023-01-04 174136 Screenshot 2023-01-04 174213

Environment

Windows Package Manager v1.3.2691

Windows: Windows.Desktop v10.0.22621.963
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2691.0


Safing Portmaster v1.0.4

About this issue

Original URL
State: closed
Created a year ago
Reactions: 4
Comments: 16 (8 by maintainers)

Most upvoted comments

I have the same issue with powershell. My installed version is 7.3.4, though winget shows it as 7.3.1

aadithya96 on May 4, 2023

You’ll have to manually uninstall the older version from Apps&Features or appwiz.cpl

mdanish-kh on May 4, 2023

Does carapace update itself?

The version information is coming from the registry when WinGet creates the entries for portable packages. If they update themselves, there is no mechanism for WinGet to know the version needs to be updated. We might need to implement some additional special logic for portable packages with a built-in upgrade mechanism.

denelon on Apr 20, 2023

This also seems to happens for standalone executables?

for example:

Name                             Id                       Version        Available      Source
----------------------------------------------------------------------------------------------
Carapace                         rsteube.Carapace         0.23.0         0.24.4         winget

$ carapace -v 
> 0.24.4

This refuses to go away…

https://github.com/microsoft/winget-pkgs/blob/378cbdd2da94fe64ab662ca192639781004b122b/manifests/r/rsteube/Carapace/0.24.4/rsteube.Carapace.installer.yaml#L14

I have also several others apps that always show as outdated (because they fail to update), and while https://github.com/microsoft/winget-cli/issues/1439 is not implemented, this is very annoying

Name                             Id                       Version        Available      Source
----------------------------------------------------------------------------------------------
FACEIT                           FACEITLTD.FACEITClient   1.31.5         1.31.13        winget
EA app                           ElectronicArts.EADesktop 12.148.0.5405  12.164.0.5421  winget
Microsoft .NET SDK 6.0.203 (x64) Microsoft.DotNet.SDK.6   6.0.203        6.0.408        winget

Araxeus on Apr 20, 2023

What is that UI coming from? It doesn’t look like Windows Apps & Features.

In general, we currently have challenges with many of the VC redists due to the various architectures being installed. We have work in progress to improve the situation. We have a set of heuristics that truncate architecture and other things listed in parenthesis at the end of the “displayName”. We need to improve the logic for manifests with the correct “AppsAndFeatures” entries.

denelon on Jan 5, 2023

Install and run. Super easy. Perhaps even available in the Store. https://github.com/marticliment/WingetUI

NoSubstitute on Jan 5, 2023

The version displayed by WinGet is what is displayed in Windows Apps & Features.

The “installer” is responsible for setting the registry keys for those values.

The functionality for 1.3 is described in the blog:

https://devblogs.microsoft.com/commandline/windows-package-manager-1-3/#new-version-reporting

denelon on Jan 4, 2023