microsoft / microsoft/winget-pkgs

upgrade always available

Open
#163,077 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Help-Wanted Issue-Bug Package-Update
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

Please confirm these before moving forward
  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have not been informed if the issue is resolved in a preview version of the winget client.
Category of the issue

Installation issue.

Brief description of your issue

When I run Winget from a Command Prompt I get this window:
image
The update completes, showing both modules have been updated.
If, however, I run the update a second time, the SAME 2 products are shown as requiring updating again.

Steps to reproduce

See description above.

Actual behavior

The same two products are repeatedly asking to be updated.

Expected behavior

IMO, once the update has been run successfully the FIRST time, a second update should NOT ask for those same two products to be updated again.

Environment
C:\>winget -v
v1.9.1792-preview

My environment: Windows 11 Professional 64-bit
Version: 23H2 OS Build 22631.3880
Screenshots and Logs

No response

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 the repeated upgrade with winget v1.9.1792-preview on Windows 11 23H2, recording the two product names and command output from both runs. Then inspect the corresponding package manifests in this repository and compare their versions; done means the second run no longer reports the same products, with focused reproduction or manifest evidence.

Written by the indexing model from the issue text.

Assessment

Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.