Use the winget tool to install and manage applications
The winget command line tool enables users to discover, install, upgrade, remove and configure applications on Windows 10 and Windows 11 computers. This tool is the client interface to the Windows Package Manager service.
Windows Package Manager winget command-line tool is available on Windows 11 and modern versions of Windows 10 as a part of the App Installer.
You can get App Installer from the Microsoft Store. If it's already installed, make sure it is updated with the latest version.
The winget command line tool is only supported on Windows 10 1709 (build 16299) or later at this time. The winget tool will not be available until you have logged into Windows as a user for the first time, triggering Microsoft Store to register Windows Package Manager as part of an asynchronous process. If you have recently logged in as a user for the first time and find that winget is not yet available, you can open PowerShell and enter the following command to request this winget registration:
Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.
Install winget preview version [Developers Only]
Windows App Installer includes the production version of the winget tool. To try the latest Windows Package Manager features, you can install the latest preview build of the winget command line tool in one of the following ways:
Use a Microsoft Account (MSA), work, school or Azure Active Directory (AAD) account to sign up for the Windows Insider Dev Channel.
Use a Microsoft Account (MSA) to sign up for the Windows Package Manager Insiders Program.
Install the Windows Desktop App Installer package located on the Releases page for the winget repository. Installing this package will give you the WinGet client, but it will not enable automatic updates from the Microsoft Store.
Install winget on Windows Sandbox
Windows Sandbox provides a lightweight desktop environment to safely run applications in isolation. Software installed inside the Windows Sandbox environment remains "sandboxed" and runs separately from the host machine. Windows Sandbox does not include winget, nor the Microsoft Store app, so you will need to download the latest winget package from the winget releases page on GitHub.
To install the stable release of winget on Windows Sandbox, follow these steps from a Windows PowerShell command prompt:
$ProgressPreference='Silent' Invoke-WebRequest -Uri https://github.com/microsoft/winget-cli/releases/download/v1.3.2691/Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle -OutFile .\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle Invoke-WebRequest -Uri https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx -OutFile Microsoft.VCLibs.x64.14.00.Desktop.appx Add-AppxPackage Microsoft.VCLibs.x64.14.00.Desktop.appx Add-AppxPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle
If you would like a preview or different version of the Package Manager, go to https://github.com/microsoft/winget-cli/releases. Copy the URL of the version you would prefer and update the above Uri.
For more information on Windows Sandbox, including how to install a sandbox and what to expect from it's usage, see the Windows Sandbox docs.
Installer behavior can be different depending on whether you are running winget with administrator privileges.
When running winget without administrator privileges, some applications may require elevation to install. When the installer runs, Windows will prompt you to elevate. If you choose not to elevate, the application will fail to install.
When running winget in an Administrator Command Prompt, you will not see elevation prompts if the application requires it. Always use caution when running your command prompt as an administrator, and only install applications you trust.
After App Installer is installed, you can run winget by typing 'winget' from a Command Prompt.
One of the most common usage scenarios is to search for and install a favorite tool.
To search for a tool, type
winget search <appname>.
After you have confirmed that the tool you want is available, you can install the tool by typing
winget install <appname>. The winget tool will launch the installer and install the application on your PC.
In addition to install and search, winget provides a number of other commands that enable you to show details on applications, change sources, and validate packages. To get a complete list of commands, type:
Some users have reported issues with the client not being on their PATH.
The current preview of the winget tool supports the following commands.
|info||Displays metadata about the system (version numbers, architecture, log location, etc). Helpful for troubleshooting.|
|install||Installs the specified application.|
|show||Displays details for the specified application.|
|source||Adds, removes, and updates the Windows Package Manager repositories accessed by the winget tool.|
|search||Searches for an application.|
|list||Display installed packages.|
|upgrade||Upgrades the given package.|
|uninstall||Uninstalls the given package.|
|hash||Generates the SHA256 hash for the installer.|
|validate||Validates a manifest file for submission to the Windows Package Manager repository.|
|features||Shows the status of experimental features.|
|export||Exports a list of the installed packages.|
|import||Installs all the packages in a file.|
The winget tool supports the following options.
|-v, --version||Returns the current version of winget.|
|--info||Provides you with all detailed information on winget, including the links to the license, privacy statement, and configured group policies.|
|-?, --help||Shows additional help for winget.|
Supported installer formats
The winget tool supports the following types of installers:
- EXE (with Silent and SilentWithProgress flags)
You can author batch scripts and PowerShell scripts to install multiple applications.
@echo off Echo Install Powertoys and Terminal REM Powertoys winget install Microsoft.Powertoys if %ERRORLEVEL% EQU 0 Echo Powertoys installed successfully. REM Terminal winget install Microsoft.WindowsTerminal if %ERRORLEVEL% EQU 0 Echo Terminal installed successfully. %ERRORLEVEL%
When scripted, winget will launch the applications in the specified order. When an installer returns success or failure, winget will launch the next installer. If an installer launches another process, it is possible that it will return to winget prematurely. This will cause winget to install the next installer before the previous installer has completed.
Debugging and troubleshooting
winget provides logging to help diagnose issues. For troubleshooting and details on logging, see Debugging and troubleshooting.
If the community repository does not include your tool or application, please submit a package to our repository. By adding your favorite tool, it will be available to you and everyone else.
Customize winget settings
You can configure the winget command line experience by modifying the settings.json file. For more information, see https://aka.ms/winget-settings. Note that the settings are still in an experimental state and not yet finalized for the preview version of the tool.
Open source details
The winget tool is open source software available on GitHub in the repo https://github.com/microsoft/winget-cli/. The source for building the client is located in the src folder.
The source for winget is contained in a Visual Studio 2019 C++ solution. To build the solution correctly, install the latest Visual Studio with the C++ workload.
We encourage you to contribute to the winget source on GitHub. You must first agree to and sign the Microsoft CLA.
The winget-cli repo maintains a list of common issues and common errors, along with recommendations on how to resolve:
Submit and view feedback for