Use the WinGet tool to install and manage applications
WinGet is a command line tool enabling users to discover, install, upgrade, remove and configure applications on Windows 10, Windows 11, and Windows Server 2025 computers. This tool is the client interface to the Windows Package Manager service.
Install WinGet
WinGet the Windows Package Manager is available on Windows 11, modern versions of Windows 10, and Windows Server 2025 as a part of the App Installer. The App Installer is a System Component delivered and updated by the Microsoft store on Windows Desktop versions, and via Updates on Windows Server 2025.
Note
The WinGet command line tool is only supported on Windows 10 1709 (build 16299) or later at this time. WinGet will not be available until you have logged into Windows as a user for the first time, triggering Microsoft Store to register the 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]
WinGet is included in the Windows App Installer. To try the latest Windows Package Manager features, you can install a preview build one of the following ways:
Download the latest WinGet preview version. Read the Release notes for WinGet preview to learn about any new features. Installing this package will give you the preview version of the WinGet client, but it will not enable automatic updates of new preview versions from the Microsoft Store.
Use a Microsoft Account (MSA), work, school or Azure Active Directory (AAD) account to sign up for the Windows Insider Dev Channel. The Windows Insider Dev Channel includes automatic updates of new preview versions from the Microsoft Store.
Use a Microsoft Account (MSA) to sign up for the Windows Package Manager Insiders Program. Once your Microsoft Account (MSA) has been added (a few days after you receive e-mail notification) you will receive automatic updates of new preview versions 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 = '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."
To install the PowerShell module in machine scope, you can use the -Scope AllUsers parameter with the Install-Module cmdlet. If you would like a preview version of WinGet, you can add -IncludePrerelease parameter with the Repair-WinGetPackageManager cmdlet. To see the available parameters for the Repair-WinGetPackageManager cmdlet, you can run Get-Help Repair-WinGetPackageManager -Full.
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.
Administrator considerations
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.
Use WinGet
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:
winget --help.
Some users have reported issues with the client not being on their PATH.
Commands
The current preview of the WinGet tool supports the following commands.
| Command | Description |
|---|---|
| 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. |
| settings | Open settings. |
| features | Shows the status of experimental features. |
| export | Exports a list of the installed packages. |
| import | Installs all the packages in a file. |
| pin | Manage package pins. |
| configure | Configures the system into a desired state. |
| download | Downloads the specified application's installer. |
Options
The WinGet tool supports the following options.
| Option | Description |
|---|---|
| -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)
- ZIP
- INNO
- NULLSOFT
- MSI
- WIX
- APPX
- MSIX
- BURN
- PORTABLE
Scripting WinGet
You can use the following syntax to install multiple applications in a single command.
USAGE: winget install <query1> <query2> ...
Example
winget install Microsoft.WindowsTerminal Microsoft.PowerToys Microsoft.VisualStudioCode
Note
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.
Missing tools
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.
Troubleshooting
The WinGet-cli repo maintains a list of common issues and common errors, along with recommendations on how to resolve:
Windows developer