Does not install on Windows 10 Enterprise LTSC 2019

[rgov]

Relevant area(s)

PowerShell Module

Relevant command(s)

Install-Module Microsoft.WinGet.Client -Force -Scope AllUsers
Repair-WinGetPackageManager

Brief description of your issue

I am running Windows 10 Enterprise LTSC 2019, version 1809, x64.

I would like to be able to install WinGet from an elevated PowerShell with just a few commands.

The first command successfully downloads and installs some dependencies.

The second command fails:

Repair-WinGetPackageManager : Failed to repair winget. Try running with -AllUsers in administrator mode.              
At line:1 char:1                                                                                                      
+ Repair-WinGetPackageManager                                                                                         
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~                                                                                         
    + CategoryInfo          : NotSpecified: (:) [Repair-WinGetPackageManager], WinGetRepairException                  
    + FullyQualifiedErrorId : RuntimeException,Microsoft.WinGet.Client.Commands.RepairWinGetPackageManagerCmdlet      

If I pass -AllUsers, it also fails:

Repair-WinGetPackageManager : No applicable license found.                                                            
At line:1 char:1                                                                                                      
+ Repair-WinGetPackageManager -AllUsers                                                                               
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                                                               
    + CategoryInfo          : NotSpecified: (:) [Repair-WinGetPackageManager], WinGetIntegrityException               
    + FullyQualifiedErrorId : RuntimeException,Microsoft.WinGet.Client.Commands.RepairWinGetPackageManagerCmdlet      

Claude sent me on an hour-long wild goose chase trying to download random kilobyte-long URLs for dependent packages from Microsoft and it was not pleasant.

Also:

1. Why do I have to run a "repair" command to do a first-time install of a package?
2. A repair tool that simply reports it cannot repair without any logged output whatsoever is frustrating.

[github-actions]

Possible duplicate(s):

Thank you for submitting this issue.

The issue(s) below may already track your request or bug. Please take a look — if one of them matches, give that issue a 👍 and close this one as a duplicate. Older or curated issues are preferred as the canonical one to follow.

• if winget-cli is installed from unelevated terminal with scope currentuser, necessary license is not installed #6212 — Repair-WinGetPackageManager fails with "No applicable license found" when winget was installed without the license (same error, same root cause)
• Repair-WinGetPackageManager does not handle missing Microsoft.UI.Xaml.2.7 or license #3374 — Repair-WinGetPackageManager does not handle missing license / fails in restricted environments
• Repair-WingetPackageManager not working as expected in system context #4271 — Repair-WinGetPackageManager not working as expected in system/admin context (same cmdlet, same failure mode)
• cannot repair winget - NamedResource Not Found #5028 — Cannot repair winget; fails during the repair flow similar to this report

Template: msftbot/duplicate/surfaced by Duplicate Surfacing

[rgov]

Dupe of #4271 I guess. I'm in a network session (over SSH). What a waste of time.