microsoft / microsoft/winget-cli

Running winget through the app execution alias gives no output

Open
#2,025 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Brief description of your issue

Running winget from the app execution alias located in %LOCALAPPDATA%\Microsoft\WindowsApps gives no console output. It still works fine if I run it from C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.18.431.0_x64__8wekyb3d8bbwe however I get no console output if I run it from the app execution alias. I've already tried stable versions and older versions and disabling and re-enabling the alias with no luck. I checked logs and running it from the alias doesn't create a log.

This may be more of a problem with windows than with winget, not sure.

Steps to reproduce

Just happened randomly, sometimes a reboot or re-install fixes it other times it doesn't.

Expected behavior

I should get console output from running winget

Actual behavior

I do not console output from running winget

Environment
Windows Package Manager (Preview) v1.3.0-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19044.1586

Logs: %TEMP%\WinGet

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the missing output by comparing winget from %LOCALAPPDATA%\Microsoft\WindowsApps with the executable under C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.18.431.0_x64__8wekyb3d8bbwe. Check whether either invocation produces files under %TEMP%\WinGet; done means the app execution alias reliably produces the expected console output.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.