upgrade --all installs packages that are already up to date

[jpbnetley]

Brief description of your issue

When I run the winget upgrade --all winget tries to upgrade software that are already the latest.
In this example, it tried to update 2 software.

• AIMP
• Discord.

I should mention that I had these apps installed form their respected websites before I had winget installed.

Steps to reproduce

I opened the term application as admin, and executed winget upgrade --all
In the attached screenshot, you will see I have discord, and AIMP open with their versions before I ran the update.

Discord's installed version is 1.0.9002
AIMP's installed version is 4.70.2251

Initially I thought it might be related to this issue: #696 (comment)
But when I checked the versions for both apps, I saw that winget lists the same versions that was installed.
To see the discord version, I ran: winget search discord
To see the AIMP version, I ran: winget search aimp

Expected behavior

I expected that when the upgrade command is executed, that software that are up to date doesn't try to download and install the same version.

Actual behavior

Up to date software gets re-downloaded and installed (in the example, Discord and AIMP).

Environment

[winget --info]
Windows Package Manager version: v1.0.11451
Windows: Windows.Desktop version: v10.0.19043.985
Package: Microsoft.DesktopAppInstaller version:  v1.11.11451.0

Any other software?

[jpbnetley]

I did see this issue looks to be related: #1009

And saw he ran winget upgrade
I did the same, and saw that the versions don't match, this the reason it tries to install already up to date versions.

Name                          Id                                     Version                Available            Source
-----------------------------------------------------------------------------------------------------------------------
AIMP                          AIMP.AIMP                              v4.70.2251, 23.05.2021 4.70.2251            winget
Battle.Net                  Blizzard.BattleNet                     Unknown                      1.22.0.12040       winget
Discord                      Discord.Discord                        0.0.309                          1.0.9002             winget

I am guessing thats the reason.

[iDolmatov]

It was previously discussed that the version displayed and the version number are not the same. There are even times when the commercial version number is different from the actual version number in the program itself.
Variations in the display of the version number. So either you have to teach winget to interpret the version numbers, or read the version number from the program file (exe, dll, etc), which will be specified with a relative path in the manifest.

I cooperate with the AIMP player team and at the moment I was only able to make a limitation so that it would not be possible to downgrade the version number when updating. When a forced downgrade occurs, the player stops working with newer databases.

[lordraiden]

Something similar happened to me. #1009

I did a first upgrade --all this 2 apps where updated, after that version becomes unknown and it tries to update every time although it is already updated.
Version number was recognized before upgrading with winget

[nlxdodge]

PS C:\Users\NLxDoDge> winget upgrade
Name                Id                              Version                Available    Source
----------------------------------------------------------------------------------------------
AIMP                AIMP.AIMP                       v4.70.2251, 23.05.2021 4.70.2251    winget
Battle.Net          Blizzard.BattleNet              Unknown                1.22.0.12040 winget
Bulk Rename Utility TGRMNSoftware.BulkRenameUtility Unknown                3.4.3.0      winget
Discord             Discord.Discord                 1.0.9000               1.0.9002     winget
MEGASync            Mega.MEGASync                   Unknown                4.5.1.0      winget
Mozilla Thunderbird Mozilla.Thunderbird             78.10.2                78.11.0      winget
GOG Galaxy          GOG.Galaxy                      Unknown                2.0.37.384   winget
Windscribe          Windscribe.Windscribe           2.2 Build 10           latest       winget

These are all packages that have issues on my personal system. Each of these is the latest version, but tries to update.
For example: Windscribe uses latest as a version and some software reports an Unkown version on my system. But I installed everything with Winget.

Windows Package Manager v1.0.11451
Windows: Windows.Desktop v10.0.19043.1023
Package: Microsoft.DesktopAppInstaller v1.11.11451.0

[cheeseandjamsandwich]

I just experienced this issue.
It turned out that Blender and Teracopy that were repeatedly wanting to Upgrade each had two versions installed, listed in 'Apps and Features'. The current version and a previous version.
Uninstalling the older versions fixed this.

[delirium-sidhe]

Found another package that updates infinitely:

Name              Id                Version Available Source
------------------------------------------------------------
TechPowerUp GPU-Z TechPowerUp.GPU-Z Unknown 2.40.0    winget

[toygark]

I have the same problem with Windscribe.

Windscribe Windscribe.Windscribe 2.2 Build 10 latest winget

[krystofkrticka]

I also have this problem and I have it with Display Fusion installed from steam because in program and features there are two entries of display fusion one is for steam and the other one is for display fusion when installed normally.

"DisplayFusion 9.8" is the entry which is also created by standard installer when installing display fusion from official website but that entry called just "DisplayFusion" without any numbers is created by steam but winget falsely detects the steam entry instead of standard entry.

Here is screenshot of winget upgrade

In some cases Unknown version is created by laziness of app developer to add proper version number to application.

[dennisvanderpool]

I have same issue. Battle.Net keeps retrying due to the Unknown

[ImJoakim]

I am also experiencing this issue..

@leochras #1191 (comment)