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

add an option to list only packages with versions that cannot be determined #4836

Open
ak1dd opened this issue Sep 29, 2024 · 2 comments
Open
Labels
Command-List Issue related to WinGet List Issue-Feature This is a feature request for the Windows Package Manager client.

Comments

@ak1dd
Copy link

ak1dd commented Sep 29, 2024

Description of the new feature / enhancement

When you run "winget update --all" and have packages with versions that cannot be determined you are recommended to "Use --include-unknown to see all results" IMO this is very vague and using --include-unknown simply seems to remove the recommendation message when you use it and further execution of "winget update --all" again shows the recommendation with no direction or explanation. It doesn't seem to "...see all results" in any way I understand.

Proposed technical implementation details

I have a lot of installed applications. I'd like to be able to do something like "winget list --unknown-only" and show just the packages with versions that cannot be determined and not have to sort through a huge list or parse it with something else. I could just pin them or find versions winget can determine. I'd like the recommendation to read something like "Use "winget list --unknown-only to see unknown results"

@ak1dd ak1dd added the Issue-Feature This is a feature request for the Windows Package Manager client. label Sep 29, 2024
Copy link

We've found some similar issues:

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage Issue need to be triaged label Sep 29, 2024
@mdanish-kh
Copy link
Contributor

While this doesn't directly address your request of having it in the CLI, you may find WinGet's PowerShell module to be useful here as an immediate workaround

After installing the module, you can use Get-WinGetPackage (winget list equivalent cmdlet) and do:

Get-WinGetPackage | Where InstalledVersion -eq "Unknown"

This will list all packages with unknown versions. If you even want to automate the pinning process you can do something like

Get-WinGetPackage | Where InstalledVersion -eq "Unknown" | Select -ExpandProperty Id | ForEach-Object { winget pin add $_ }

This gets all installed versions with value "Unknown", gets their ID and calls winget pin on each of them

@microsoft-github-policy-service microsoft-github-policy-service bot added Command-List Issue related to WinGet List and removed Needs-Triage Issue need to be triaged labels Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Command-List Issue related to WinGet List Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
None yet
Development

No branches or pull requests

2 participants