The Winget command line lets users manage existing applications and install new ones from a command-line interface in Windows 10 and 11. However, this command line can sometimes not work and show the error message “Winget is not recognized.”

This error usually appears due to reasons like outdated packet manager, missing path environment variable, or disabled Windows packet manager client. Furthermore, you will also get this error on older Windows 10 as the Winget packet manager is not installed by default.

The Winget package manager comes as a part of the App Installer software on Windows. If you’re running an outdated version of the App Installer, you may get the “Winget is not recognized” error. So, you can try updating the App Installer to fix this issue.

microsoft-store

If you may’t update App Installer from the Microsoft Store, you can manually do so by downloading it from theGithub repository. To download the update, select the latest version name on the top, and download the update file from the assets section at the bottom.

After the setup file downloads, simply run it to update or install Microsoft Winget on your computer.

Enable Windows Package Manager Client

An app execution alias is the declared name for a specific app that can be used to run it from a command line interface. The term Winget is the app execution alias for the Windows packet manager client.

search-app-installer-in-microsoft-store

So, if the Windows package manager client is disabled in the app execution alias, the term Winget will not be associated with the Winget package manager. This will result in the error “Winget is not recognized.” Here’s how you may enable it back.

Manually Enter the Path Environment Variable

Whenever you run the Winget command line, it will locate thewinget.exefile using the path environment variable. If your path environment variable hasn’t been created or accidentally deleted, the Winget command won’t be able to locatewinget.exe, and it will result in this error.

So, let’s see how you may manuallycreate the path environment variableand fix this error.

update-app-installer

advanced-app-settings

windows-settings-app-execution-alias

toggle-on-windows-package-manager-client

systempropertiesadvanced

environment-variables