winget-cli: Sometimes, winget doesn't work.

Installed this morning using the bundle from the GitHub page (v1.0.11451) and using Add-AppxPackage. Running into the same issue, but this is what I discovered.

If I run PS as the account that I’m logged in as, WinGet works. This works for a non-admin AD account as well as an different AD with admin creds. Now if I escalate privileges for PS using the admin account while logged with the standard user, it doesn’t work.

All app store packages were fully updated at the time of testing.

[Edit] For poops and giggles I tried it with ye old cmd terminal, got the same results as above.

I’m running into the same “version 0.0.0.0” issue after installing winget 0.1.42101 Preview directly from the GitHub Releases page in Windows 10 version 10.0.19041.388. winget was first installed in an Admin account and later installed in my regular/“Standard” account. Both are local accounts.

Get-Command winget displays “version 0.0.0.0” whether it’s run in an Admin or “Standard” PowerShell window, so it seems like there’s a different issue going on here as it works in both accounts.

Some additional output for reference: Running winget in an Admin CMD window while in a “Standard” account displays The system cannot execute the specified program. Running it in a regular CMD window in both the Admin account and the “Standard” account displays the regular expected help output. Running it in an Admin CMD window in the Admin account works just fine.

PowerShell output when run from an Admin window in the “Standard” account:

Program 'winget.exe' failed to run: The file cannot be accessed by the systemAt line:1 char:1
+ winget
+ ~~~~~~.
At line:1 char:1
+ winget
+ ~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

I ran into this issue while trying to verify #528.

This happens to me too. I had just installed v1.0.11451 from github releases. Though it was likely broken before too. At first, the command wasn’t recognized. So I added the WindowsApps directory to my user path: %userprofile%\AppData\Local\Microsoft\WindowsApps

Even afterwards, the command wasn’t recognized. If I navigate manually to %userprofile%\AppData\Local\Microsoft\WindowsApps and run .\winget, there is no output.

If I run Get-Command on winget, it comes up as version 0.0.0.0.

I’ve tried resetting and reinstalling a few times, but mine seems to be in a broken state.

PS C:\Users\lygaj\AppData\Local\Microsoft\WindowsApps> winget
winget: The term 'winget' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Suggestion [3,General]: The command winget was not found, but does exist in the current location. PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\winget". See "get-help about_Command_Precedence" for more details.
PS C:\Users\lygaj\AppData\Local\Microsoft\WindowsApps> .\winget
PS C:\Users\lygaj\AppData\Local\Microsoft\WindowsApps>

I’m having the same issue (installed via GitHub releases), however, when attempting to do it via PS (with admin priv.) I get the following error

Program 'winget.exe' failed to run: The file cannot be accessed by the systemAt line:1 char:1
+ winget.exe
+ ~~~~~~~~~~.
At line:1 char:1
+ winget.exe
+ ~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

I also tried to cd into the directory where it is installed too and that did not work. If it helps, I have winget installed both on the admin and standard account. I have checked and the App Execution Alias on both accounts for winget is enabled.