microsoft / microsoft/winget-cli

Error upgrading with package id

Open
#2,385 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Matching Help-Wanted 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

Not sure if it's related to the package Everything, an unexpected result is that winget upgrade voidtools.Everything shows No applicable update found. but winget upgrade listed this update.

Steps to reproduce
PS C:\Users\ziok_> winget upgrade
Name                        Id                   Version      Available
------------------------------------------------------------------------
Everything 1.4.1.1009 (x64) voidtools.Everything < 1.4.1.1014 1.4.1.1017
1 upgrades available.
PS C:\Users\ziok_> winget upgrade voidtools.Everything
No applicable update found.
PS C:\Users\ziok_> winget upgrade --all --silent
Name                        Id                   Version      Available
------------------------------------------------------------------------
Everything 1.4.1.1009 (x64) voidtools.Everything < 1.4.1.1014 1.4.1.1017
1 upgrades available.

(1/1) Found Everything [voidtools.Everything] Version 1.4.1.1017
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://www.voidtools.com/Everything-1.4.1.1017.x64.msi
  ██████████████████████████████  1.84 MB / 1.84 MB
Successfully verified installer hash
Starting package install...
Successfully installed
Expected behavior

It should work as expected, upgrade the package with the specified Id.

Actual behavior

It shows No applicable update found.

Environment
Windows Package Manager (Preview) v1.4.2011-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.25163.1010
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.2011.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

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

Reproduce the discrepancy with the reported winget upgrade and winget upgrade voidtools.Everything commands, then inspect the diagnostic files under %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir. Trace how an explicit package ID is matched against the listed update; done means the specified ID upgrades successfully in the reported environment.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.