-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Labels
In-PRIssue related to a PRIssue related to a PRIssue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.PowerShellIssue related to WinGet PowerShell Module or cmdletIssue related to WinGet PowerShell Module or cmdletmsstoreIssue related to "msstore" REST sourceIssue related to "msstore" REST source
Milestone
Description
Brief description of your issue
Get-WinGetPackage
returns CatalogError:
~ Get-WinGetPackage
Get-WinGetPackage: An error occurred while searching for packages: CatalogError
I don't know where to get the associated logs from, but I believe it's failing update msstore
source. How do I know this? Well for one, Get-WinGetPackage -Source winget
works fine. And also winget list
output shows me Failed when searching source; results will not be included: msstore
(root cause of which is I believe #4785)
I think the expected behavior would be that instead of completely failing if one source errors out, Get-WinGetPacakge
should return the packages it's able to find successfully i.e., making the behavior consistent with winget list
Steps to reproduce
- Have msstore source failing
- Do
Get-WinGetPackage
- See the cmdlet fail as well
Expected behavior
Get-WinGetPackage should return packages from winget or other configured sources
Actual behavior
Command errors out with CatalogError
Environment
~ Get-Module Microsoft.WinGet.Client | Select Version
Version
-------
1.9.2411
Metadata
Metadata
Assignees
Labels
In-PRIssue related to a PRIssue related to a PRIssue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.PowerShellIssue related to WinGet PowerShell Module or cmdletIssue related to WinGet PowerShell Module or cmdletmsstoreIssue related to "msstore" REST sourceIssue related to "msstore" REST source