microsoft / microsoft/winget-cli
No Output for Winget running as system from "C:\program files\windowsapps\Microsoft.DesktopAppInstaller_1.18.2691.0_x64__8wekyb3d8bbwe"
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
On about 10% of our desktop estate winget.exe produces no console output when running as the Local System Account from "C:\program files\windowsapps\Microsoft.DesktopAppInstaller_1.18.2691.0_x64__8wekyb3d8bbwe"
Winget runs as expected when run as a standard user. This is only happening on about 10% of our devices. The other 90% winget.exe runs as expected for the local system account when run from "C:\program files\windowsapps\Microsoft.DesktopAppInstaller_1.18.2691.0_x64__8wekyb3d8bbwe"

Windows: Windows.Desktop v10.0.19044.2251
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2691.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 with winget.exe from the Microsoft.DesktopAppInstaller package path and compare its behavior under a standard user and the Local System Account on an affected device. Review the diagnostic files in %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir and compare them with a device where output works. Done means identifying the cause of the missing console output and restoring output for the affected configuration.
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
- Needs clarification
- Newbie friendliness
- 25/100