CODEWITHSUNDEEP
windows-10winget
PressTonns
PressTonns

Reputation: 41

winget is not a cmdlet name

After a fresh install of Windows 10 with the latest updates i get the error that winget.exe is not a cmdlet.

The PATH variable is set to the correct directory. However the "winget.exe" is not in that directory with other WindowsApps. The Package Installer is installed and even shows up in the "uninstall apps" settings.

I think that it either put the winget.exe in a different directory or else i dont know.

On my other laptop winget works and is in the Path of the exact environment variable.

Upvotes: 4

Views: 20299

Answers (3)

Gold Isaac
Gold Isaac

Reputation: 81

I kept getting these same errors until I followed the steps in How to fix “The term ‘winget’ is not recognized as a name of a cmdlet, function, script file, or executable program.” in Windows? and pasted this code with admin privilege on powershell Install-Module -Name Microsoft.WinGet.Client

Upvotes: 8

Zapperz0398
Zapperz0398

Reputation: 17

This is probably because you do not have it installed on your system yet. You can find it in the Microsoft store here

Just install it, and probably restart your shell for it to take effect

If you want, you can check out the official Microsoft website on WinGet here

Upvotes: 0

Demitrius Nelon
Demitrius Nelon

Reputation: 1248

On Windows 10, it's likely the Microsoft Store hasn't yet updated the App Installer to the latest version right after the OS has installed on first login. If you update the Apps in the Microsoft Store, that should resolve this issue.

Alternatively, instructions are available at Microsoft Learn for downloading the MSIX packages and registering them for users on the system.

It's also possible to install and use the Microsoft.WinGet.Client PowerShell module which contains a "Repair-WinGetPackageManager" cmdlet.

Upvotes: 4

Related Questions