`winget show -e <package>` only show info on packges updates that has not yet been installed, and not the currently installed.

[eabase]

Relevant area(s)

WinGet CLI

Relevant command(s)

winget show

Brief description of your issue

I have a pinned a package since some time ago, and I recently got an "update". However, the update should not be shown as the package was pinned, so I tried to pin it again, but it's already pinned but not possible to remove from normal list.

Steps to reproduce

# winget list --upgrade-available --include-unknown

Name             Id              Version Available Source
---------------------------------------------------------
osquery          osquery.osquery 5.19.0  5.20.0    winget


# winget show -e 'osquery.osquery'
Found osquery [osquery.osquery]
Version: 5.20.0     <----------------------- ISSUE !
Publisher: osquery
...

Expected behavior

That winget show -e 'osquery.osquery' show the info about the version of the currently installed package.

Actual behavior

Shows info about package that is not (yet) installed, but available as update.

Environment

Windows Package Manager v1.12.350
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.26100.6899
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.27.350.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads
Configuration Modules              %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules

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

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
ProxyCommandLineOptions                   Disabled
DefaultProxy                              Disabled

[github-actions]

The following issues might be duplicates:

• winget list --upgrade-available --include-unknown shows pinned package as available when it should not #5878
• Confusing winget upgrade/list summaries for pinned, explicit-target, and --include-unknown packages #5879

AI-generated content by genai-issue-dedup may be incorrect.

[eabase]

Note

Not a duplicate. Your bot is responding too fast, I was still editing the issue!

[Trenly]

winget show is designed to show the details of the latest version available for a package as they appear in any available source. If you want to show the manifest details for a specific version - such as the currently installed version - you can use the -v flag.

It appears to me that using winget show -e 'osquery.osquery' -v 5.19.0 gives the intended results.

[eabase]

It appears to me that using ... '-v 5.19.0` gives the intended results.

Indeed, and that is not a very UX friendly logic.

The default should be what's currently installed, not some hypothetical different version, whose version numbers I know nothing about without having to do several other commands. And it goes against what other package managers does.

If you still insist in keeping this reverse logic, I suggest to at least inform the user that they have another package version, already installed.

[denelon]

Most customers use a flow like:

winget search <query>
then
winget show <id>
then
winget install <id>

The "show" command was designed to show some detailed package information based on what's available in WinGet's configured sources, and which installer would be selected by WinGet for an install or upgrade flow.

The WinGet List command was designed to show information about "installed" applications.

Pinning was designed to allow a user to control WinGet's behavior with respect to the Upgrade flow. Unfortunately, some applications have their own "built-in" update mechanism which WinGet can't effectively block.

Running winget upgrade would show packages that WinGet would upgrade. This would "exclude" pinned packages unless the upgrade matches the pinning requirements.

Running winget list --upgrade-available is showing installed applications where an upgrade is available in the repository. This was an intentional design decision.