Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--include-unknown does not work #3477

Closed
colejohnson66 opened this issue Jul 27, 2023 · 4 comments
Closed

--include-unknown does not work #3477

colejohnson66 opened this issue Jul 27, 2023 · 4 comments
Labels
Command-Upgrade Issue related to WinGet Upgrade Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate Issue is a duplicate
Milestone

Comments

@colejohnson66
Copy link

colejohnson66 commented Jul 27, 2023

Brief description of your issue

As shown in the screenshot, the --include-unknown flag does not work. I ran a normal upgrade with winget upgrade --all, and, at the end was informed that "32 package(s) have version numbers that cannot be determined." As instructed, I used --include-unknown to list them, but I got an empty result.

A screenshot of Windows Terminal showing invocations of winget upgrade --include-unknown and winget upgrade --all --include-unknown

Steps to reproduce

Run winget upgrade --include-unknown (and optionally with --all) and observe an error message.

Expected behavior

A list of packages (probably mostly Steam apps/games) that have unknown versions.

Actual behavior

A message informing me that "[n]o installed package found matching [the] input criteria."

Environment

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

Windows: Windows.Desktop v10.0.23506.1000
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.21.1573.0

Winget Directories                 
-----------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
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

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
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage Issue need to be triaged label Jul 27, 2023
@Trenly
Copy link
Contributor

Trenly commented Jul 27, 2023

If you run winget list, do any of the packages with version unknown have ID's have any information in the Source column?

@denelon denelon added Issue-Bug It either shouldn't be doing this or needs an investigation. Command-Upgrade Issue related to WinGet Upgrade and removed Needs-Triage Issue need to be triaged labels Jul 27, 2023
@denelon
Copy link
Contributor

denelon commented Jul 27, 2023

I think this is a duplicate of #2458

We're getting a count before removing the ones that don't have a configured source.

@denelon
Copy link
Contributor

denelon commented Jul 27, 2023

Duplicate of #2458

@denelon denelon marked this as a duplicate of #2458 Jul 27, 2023
@microsoft-github-policy-service
Copy link
Contributor

Hello @colejohnson66,

We've identified this as a duplicate of another issue or PR that already exists. This specific instance is being closed in favor of the linked issue. Please add your 👍 to the other issue to raise its priority. Thanks for your contribution!

Template: msftbot/duplicate/closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Command-Upgrade Issue related to WinGet Upgrade Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate Issue is a duplicate
Projects
None yet
Development

No branches or pull requests

3 participants