microsoft / microsoft/winget-cli

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

Open
#4,510 16 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Command-Upgrade Issue-Bug
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

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

image

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

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 winget upgrade --all -h and then winget upgrade --include-unknown in the reported Windows Package Manager environment. Compare the package counts and version-unknown results after the upgrade completes. Done means the discrepancy is explained and the upgrade output consistently reports the packages shown by --include-unknown.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.