microsoft / microsoft/winget-cli
Search found results but install could not find the package. "No package found matching input criteria."
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Brief description of your issue
Winget search found the results but when we try to install the app it does not work.
winget search roblox

Although I am able to install it via Microsoft Store.

Steps to reproduce
-
First search your application
winget search roblox
-
Second install your application
winget install --accept-package-agreements --accept-source-agreements --exact --silent --id 9NBLGGGZM6WM
Expected behavior
Give appropriate error messages of why it could not find and install.
Actual behavior
Does not give a reason why it could not find a package to install. Even verbose logs does not give out any detail.
Environment
Windows Package Manager v1.2.10271
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.19042.1645
Package: Microsoft.DesktopAppInstaller v1.17.10271.0
Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
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
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 issue with winget search roblox and the provided winget install command, then inspect the diagnostic logs under %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir. Trace the search and install entry points to determine why the Store identifier is not resolved, and verify that the failure reports a useful reason.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100