About app version

[KaranKad]

Some apps have long release number on their website and in about section of the app, but when installed, control panel/settings app show the release in short version.

In about section and website

In settings app

If I keep the manifest according to the app and website, winget thinks the app is outdated because it checks the app version according to control panel/settings app and tries to install it.

I have latest version of CPU-Z v1.96.1 installed but the app in control panel reports as 1.96, so winget thinks its outdated and tries to upgrade the app.

In about section

winget upgrade command showing app has update

In settings app

Some apps don't have version number at all

This would be a non issue if apps reported their version properly, but sadly they don't.

[OfficialEsco]

Since winget upgrade just got out of experimental there is a few issues, WinGet is looking at the version which is shown in the Control Panel/Settings App (Which is the version you should type in the Version field)

Main issue thread: microsoft/winget-cli#976
Feature Request for the bot: #13620
Alternative Version Feature Request: microsoft/winget-cli#980

I also see that winget upgrade is trying to upgrade to latest, which IMO it should not try to do

[KaranKad]

Control Panel/Settings App (Which is the version you should type in the Version field)

I will update manifests according to it then.

[jedieaston]

I also see that winget upgrade is trying to upgrade to latest, which IMO it should not try to do

It tries to do this for Spotify too, which is rather annoying. At least MSIs are upgraded right now which is nice.

[denelon]

We're tracking Issues in the client repository where we think logic changes might help. I think I've seen most of these reported on microsoft/winget-cli#976. I'm going to go ahead and convert this to a discussion, so it isn't closed as an issue.

The current experimental store source doesn't report versions for packages. All we have is "latest" as a sentinel value. That results in store packages always thinking there is an upgrade available. Packages installed from the store generally get automatically updated as long as no policy restricts that behavior.

I'm interested in more discussion here around maybe changing to version "unknown" or something like that so the behavior could make more sense. Maybe we need an option for upgrade to try upgrading things marked "latest" or "unknown".

Spotify is behind a vanity URL and the installer changes frequently. It's been quite a challenge to keep the right hash on the manifest. We've added a couple of features to try and help. microsoft/winget-cli#870 and microsoft/winget-cli#920.