microsoft / microsoft/winget-cli
Get/Install/Find-WinGetPackage PowerShell cmdlets fail with "An error occurred while connecting to the catalog"
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Relevant area(s)
WinGet CLI, PowerShell Module
Relevant command(s)
No response
Brief description of your issue
All these commands fails with the same error: An error ocurred connecting to the catalog:
PS C:\windows\system32> Get-WinGetPackage -ID '9P7KNL5RWT25'
Get-WinGetPackage : An error occurred while connecting to the catalog.
At line:1 char:1
+ Get-WinGetPackage -ID '9P7KNL5RWT25'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-WinGetPackage], CatalogConnectException
+ FullyQualifiedErrorId : RuntimeException,Microsoft.WinGet.Client.Commands.GetPackageCmdlet
PS C:\windows\system32> Find-WinGetPackage -ID '9P7KNL5RWT25'
Find-WinGetPackage : An error occurred while connecting to the catalog.
At line:1 char:1
+ Find-WinGetPackage -ID '9P7KNL5RWT25'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Find-WinGetPackage], CatalogConnectException
+ FullyQualifiedErrorId : RuntimeException,Microsoft.WinGet.Client.Commands.FindPackageCmdlet
PS C:\windows\system32> Install-WinGetPackage -ID '9P7KNL5RWT25'
Install-WinGetPackage : An error occurred while connecting to the catalog.
At line:1 char:1
+ Install-WinGetPackage -ID '9P7KNL5RWT25'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Install-WinGetPackage], CatalogConnectException
+ FullyQualifiedErrorId : RuntimeException,Microsoft.WinGet.Client.Commands.InstallPackageCmdlet
I've run as adminstrator and non-administrator. I've run Repair-WinGetPackageManager, which doesn't fix the issue. I've restarted.
> Repair-WinGetPackageManager -allusers -force -latest
VERBOSE: Creating MTA thread
VERBOSE: Running winget.exe with --version
VERBOSE: WinGet is in a good state.
Steps to reproduce
- Run
Get-WinGetPackage,Find-WinGetPacakge, orInstall-WinGetPackage.
Expected behavior
I expect them to not fail with that error.
Actual behavior
Failing with that error.
Environment
PS C:\windows\system32> winget --info
Windows Package Manager v1.28.190
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.18363.2274
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.28.190.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
> Get-Module Microsoft.WinGet.Client
ModuleType Version Name ExportedCommands
---------- ------- ---- ----------------
Binary 1.12.440 Microsoft.WinGet.Client {Add-WinGetSource, Assert-WinGetPackageManager, Disable-WinGetSetting, Enable-WinGetSetting...}
> $PSVersionTAble
Name Value
---- -----
PSVersion 5.1.18362.2212
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.18362.2212
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with Get-WinGetPackage, Find-WinGetPackage, and Install-WinGetPackage, then inspect the diagnostics under %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir. Compare the PowerShell module and winget --info details from the report; done means all three cmdlets connect to the catalog successfully in the reported environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100