Install Winget Using Powershell Updated Jun 2026

Now that Winget is installed and configured, you can start using it to manage software on your system. Here are a few basic examples:

| Method | Command | Best For | |--------|---------|----------| | PowerShell Gallery | Install-Script winget-install -Force followed by winget-install | Most users, enterprise environments | | Single-Line Command | irm asheroto.com/wingend | iex | Quick testing, automation | | Local Script | Download and run .\\winget-install.ps1 | Security-conscious users, air-gapped preparation | | Microsoft Store | Update "App Installer" from Store | Standard Windows 10/11 users | | Offline MSIX | Download .msixbundle → Add-AppxPackage | LTSC, Server, no Store access |

start ms-windows-store://pdp/?productid=9NBLGGH4NNS1

Once Winget is installed, you may want to configure it to suit your needs. Here are a few basic configuration options: install winget using powershell updated

# Define the URL for the latest stable WinGet bundle $url = "https://aka.ms" $dest = "$env:TEMP\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle" # Download the package Invoke-WebRequest -Uri $url -OutFile $dest # Install the package package for the current user Add-AppxPackage -Path $dest Use code with caution. Verify the Installation

Install-Script winget-install -Force

winget --debug

Repair-WinGetPackageManager -AllUsers

This updated guide provides definitive, step-by-step methods to install or repair Winget using PowerShell. Prerequisites and Requirements

Windows Server (2019, 2022, and 2025) does not natively support the Microsoft Store infrastructure, which often breaks standard WinGet installers. To make WinGet function on Windows Server via PowerShell, you must manually install the required VCLibs and UI XAML dependencies first. Now that Winget is installed and configured, you

: Close all PowerShell windows and reopen them. If the error persists, test the direct path explicitly: & "$env:LOCALAPPDATA\Microsoft\WindowsApps\winget.exe" --version . If this works, you need to manually append %USERPROFILE%\AppData\Local\Microsoft\WindowsApps to your system Environment Variables.

If you want to install it in machine scope (available to all users on the system), use:

If successful, the console will output the current version number (e.g., v1.9.xxxx ). : Close all PowerShell windows and reopen them