Microsoft Store app is published but not discoverable through WinGet msstore source
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Start by reproducing the issue with winget source reset --force, winget source update, and the reported winget show and winget search commands against the msstore source. Inspect the linked verbose log and the packageManifests request; the issue is done when Product ID 9NNZR5BZQJ42 returns a manifest and is discoverable through msstore.
Written by the indexing model from the issue text.
Description
Relevant area(s)
WinGet CLI
Relevant command(s)
winget show, winget search
Brief description of your issue
My Microsoft Store application "Well of Legends" (Product ID: 9NNZR5BZQJ42) is published and publicly available in the Microsoft Store, but it cannot be discovered through the WinGet msstore source.
A known-good Microsoft Store package (Company Portal, Product ID: 9WZDNCRFJ3PZ) is discovered successfully from the same machine and the same msstore source.
Microsoft Dev Center Support investigated this under case 2607280050002589 and asked me to report the issue to the WinGet team using the msstore tag.
Steps to reproduce
- Reset and update the WinGet sources:
winget source reset --force
winget source update
- Verify that a known-good Microsoft Store package can be retrieved:
winget show --id 9WZDNCRFJ3PZ --source msstore --accept-source-agreements
Result:
Found Company Portal [9WZDNCRFJ3PZ]
- Search for my published Microsoft Store application:
winget search --id 9NNZR5BZQJ42 --source msstore --exact --accept-source-agreements --verbose-logs
Result:
No package found matching input criteria.
- The same issue occurs with:
winget show --id 9NNZR5BZQJ42 --source msstore --accept-source-agreements
The application is publicly available in the Microsoft Store.
Expected behavior
WinGet should discover and return the Microsoft Store package for Well of Legends when queried using its Store Product ID 9NNZR5BZQJ42 through the msstore source.
Actual behavior
WinGet returns:
No package found matching input criteria.
Verbose logging shows that WinGet successfully sends a request to:
https://storeedgefd.dsx.mp.microsoft.com/v9.0/packageManifests/9NNZR5BZQJ42?Market=CZ
The Microsoft Store backend responds with HTTP 200 OK, but no package manifest is returned.
The log then reports:
No manifest results returned.
Search result size: 0
No app found matching input criteria
and terminates with error:
0x8a150014
A known-good Store Product ID works correctly through the same msstore source.
WinGet-2026-08-21-11-40-16.999.log
Environment
Windows Package Manager v1.29.290
Windows: Windows.Desktop v10.0.26200.9168
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.29.290.0
- Dominant language
- C++
- Stars
- 26.6k
- Forks
- 1.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 41
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from microsoft/winget-cli
-
Issue-Docs Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
microsoft/winget-cli#6692 ·
Maintainers usually reply within 2 days
-
Issue-Docs Possible-Duplicate
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/winget-cli#6493 · 1 comment ·
Maintainers usually reply within 2 days
-
Issue-Feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-cli#6427 ·
Maintainers usually reply within 2 days
-
Issue-Docs msstore
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
microsoft/winget-cli#6331 · 1 comment ·
Maintainers usually reply within 2 days
-
Command-Source Issue-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-cli#6148 ·
Maintainers usually reply within 2 days
All issues in microsoft/winget-cli
Similar issues
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stratum-mining/sv2-tp#167 ·
Maintainers usually reply within 1 day
-
better error message bug low priority semantics strings
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Sign up button opens the Sign in page instead of the Sign up page for Enterprise edition serversOpenauth bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MerginMaps/mobile#4795 ·
Maintainers usually reply within 2 days