Getting a massive amount of packages whose version cannot be determined after using 'winget upgrade'

[AvogatoWizardWhisker]

Brief description of your issue

I ran winget upgrade to update available packages. When it was done, i got the following text

86 package(s) have version numbers that cannot be determined. Use --include-unknown to see all results.

But when run winget upgrade --include-unknown, there was only one package whose version is unknown

Steps to reproduce

1. Run winget upgrade --all -h
2. Waiting for available packages to update
3. After finishing the update, I get the message 86 package(s) have version numbers that cannot be determined. Use --include-unknown to see all results.

Expected behavior

I'm expecting for packages to successfully update.

Actual behavior

When winget finished updating packages, this message shows up 86 package(s) have version numbers that cannot be determined. Use --include-unknown to see all results. Even tho i run winget upgrade --include-unknown, there's only one package (NirSoft.BlueScreenView) with unknown version.

Environment

Windows Package Manager v1.7.11261
Windows: Windows.Desktop v10.0.26217.5000
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.11261.0

[github-actions[bot]]

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:

• --include-unknown shows a lower number of packages after running "winget upgrade --all" (#2458), similarity score: 0.87
• Winget refuses to update packages, ignoring --all as well (#2891), similarity score: 0.80

Closed similar issues:

• winget upgrade --all reports packages with unknown version numbers, that --include-unknown does not list (#2929), similarity score: 0.86
• --include-unknown does not work (#3477), similarity score: 0.80
• --include-unknown not functioning as expected (#1939), similarity score: 0.79

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

[AvogatoWizardWhisker]

I double checked with winget upgrade --include-unknown, there was only one package

[Trenly]

@florelis accurately described the issue in #2458

I took a quick look at the code and saw two possible sources for inconsistencies with the unknown count

1. When listing available upgrades we first filter the unknown installed versions and count them there, but we may later remove other packages that are not available from any source. So the count of unknown includes those un-available packages that are not listed with --include-unknown. That's probably what happened here.
2. When performing the upgrades we first filter the unknown versions and count them there, but we later remove packages where the update is not applicable (e.g., mismatched architecture). So the count of unknown includes the non-applicable updates that are not applied with --include-unknown.