microsoft / microsoft/winget-cli
WinGet not listing packages as installed
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
I have an internal WinGet repository where I have uploaded several of our internal applications that I push out to our internal machines. After pushing out certain installers (mainly installers from SAP), they do not show up in a WinGet export as being installed, even though they are. If I run winget list, it tells me the application is installed. I have matched all parameters of the application from what WinGet shows with the package I am pushing out, but it is still not being detected. This seems to be more of an issue with applications that do not install with a proper GUID. For example, SAP GUI installs with a GUID of "SAPGUI".
Steps to reproduce
Create a custom WinGet package of a problematic installer.
Install the application using WinGet.
Export list of installed packages.
Expected behavior
When an application is installed from WinGet, it should be listed in an export of installed packages.
Actual behavior
When an application is installed from WinGet, it is not being listed in an export of installed packages.
Environment
Windows Package Manager v1.6.2631
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.19045.3448
System Architecture: X64
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
Reproduce the report by installing a custom package, then compare the output of winget list with winget export for an installer whose installed identifier is SAPGUI. Start by tracing the list and export handling for installed package identifiers; done means packages installed through WinGet, including those without a conventional GUID, appear in the export.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100