winget is not recognized as the name of cmdlet

Question

If I try to execute winget as admin, I will get error saying "winget is not recognized as the name of cmdlet" This is seeing on any Windows 11 computer. I already checked variable below. Is the any way to archive this? Because Intune new Store does not contain all apps yet, I am scripting some packages do get installed via WinGet. Application would work if User Context is used, but not with System context.

This problem is seeing only in Windows 11, Windows 10 does not have this problem. Also App Installer from Store is installed, it does not make any difference.

Answer 1

I found the win get upgrade on windows 11 was broken and no matter what I tried it kept coming up with the same error(s) as shown in the picture above.

I found this simple fix using the code below Just copy and paste the entire code, and it should be problem solved (this is what fixed it for me)

$progressPreference = 'silentlyContinue'
Write-Host "Installing WinGet PowerShell module from PSGallery..."
Install-PackageProvider -Name NuGet -Force | Out-Null
Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery | Out-Null
Write-Host "Using Repair-WinGetPackageManager cmdlet to bootstrap WinGet..."
Repair-WinGetPackageManager
Write-Host "Done."

Answer 2

Hi Pavel

I ran into this problem a while ago and the solution was to write down the file path, check my below script:

#upgrade Microsoft Teams 
#Date 20/9/2022
#this script working with windows 10
#this script working with Microsoft MDM
#By.Khaled Elsayed 

write-host " Upgrade Microsoft Teams " -ForegroundColor Green
write-host " don't close this window, it will be close automatically" -ForegroundColor red
write-host "_________________________________________________________"

Set-ExecutionPolicy -ExecutionPolicy Bypass -Force
$ResolveWingetPath = Resolve-Path "C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_*_x64__8wekyb3d8bbwe"
    if ($ResolveWingetPath){
           $WingetPath = $ResolveWingetPath[-1].Path
    }

$config
cd $wingetpath
cmd.exe /c "winget.exe upgrade microsoft.teams --accept-package-agreements --accept-source-agreements --silent --force"
exit

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

The issue to get Winget recognized behind system context will be solved with this command:

Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe

But the major issue in Winget is, that it does not use winget resource after OS installation or windows enrollment, it will then use only msstore repository. I have MS case opened because of this. I will keep your posted.

Answer 4

I am considering an option to include winget.exe with together with every package, next to the PS1 script.

Actually this behavior varies, some Windows 10 fails as well, and some Windows 11 which uses Windows Terminal already, actually manages to run winget, but that is very rare.