How to Install WinGet Using PowerShell (2026 Update)  WinGet (Windows Package Manager) is now a core system component for Windows 10 (version 1809+), Windows 11, and Windows Server 2025. While it usually comes pre-installed via the App Installer from the Microsoft Store, you may need to install or repair it using PowerShell if it is missing or corrupted.  Method 1: The Fast Microsoft Repair (Recommended) 

This is the modern, programmatic way to bootstrap WinGet using Microsoft's official PowerShell module. It automatically handles dependencies like VCLibs and XAML.  Launch PowerShell as Administrator. Run the following commands: powershell

# Install the required NuGet provider Install-PackageProvider -Name NuGet -Force | Out-Null # Install the WinGet client module from PowerShell Gallery Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery | Out-Null # Bootstrap the WinGet client Repair-WinGetPackageManager -AllUsers Use code with caution. Copied to clipboard

Note: Adding -IncludePrerelease to the final command will install the preview version instead.  Method 2: Manual MSIX Installation via PowerShell 

If the automated module fails or you are in an offline environment, you can manually pull the latest bundle from the WinGet GitHub Releases.  Download the latest .msixbundle: powershell

$url = "https://aka.ms/getwinget" Invoke-WebRequest -Uri $url -OutFile "winget.msixbundle" Use code with caution. Copied to clipboard Install the package: powershell Add-AppxPackage -Path ".\winget.msixbundle" Use code with caution. Copied to clipboard Clean up: powershell Remove-Item ".\winget.msixbundle" Use code with caution. Copied to clipboard   Method 3: One-Line Community Installer 

For a quick setup that handles all prerequisites (VC++ Redistributables and UI Xaml) in one go, you can use popular community scripts like the winget-install script.  Run this command to install immediately: powershell

Invoke-WebRequest https://raw.githubusercontent.com/asheroto/winget-installer/master/winget-install.ps1 -UseBasicParsing | iex Use code with caution. Copied to clipboard   Verifying the Installation 

Once the process is complete, restart your terminal and type the following to confirm:  powershell winget --version Use code with caution. Copied to clipboard

If you see a version number (e.g., v1.9.xxxx), the installation was successful. 

Use WinGet to install and manage applications | Microsoft Learn

Installing WinGet (Windows Package Manager) via PowerShell is the most efficient way to skip the Microsoft Store and automate your setup.

While modern Windows versions usually include it, you can force-install or repair it with these updated methods. 1. The Quick "One-Liner" (GitHub Release)

This script fetches the latest version directly from Microsoft’s GitHub and installs it. Open PowerShell as Administrator and run: powershell

$url = (Invoke-RestMethod https://api.github.com/repos/microsoft/winget-cli/releases/latest).assets.browser_download_url | Where-Object $_.EndsWith(".msixbundle") Invoke-WebRequest -Uri $url -OutFile "winget.msixbundle" Add-AppxPackage -Path "winget.msixbundle" Remove-Item "winget.msixbundle" Use code with caution. Copied to clipboard 2. The Official "Repair" Method

If you have the Microsoft.WinGet.Client module, you can use the official "bootstrap" command to install or fix WinGet for all users: powershell

Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery Repair-WinGetPackageManager -AllUsers Use code with caution. Copied to clipboard 3. The "Missing Dependencies" Fix

On older Windows 10 builds, WinGet might fail because it needs specific UI frameworks. Use this if the standard install doesn't work: powershell

# 1. Install VC++ Runtime Invoke-WebRequest -Uri https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx -OutFile VCLibs.appx Add-AppxPackage VCLibs.appx # 2. Install UI Xaml 2.8 (Required for newer WinGet) Add-AppxPackage -Path https://cdn.winget.microsoft.com/cache/source.msix Use code with caution. Copied to clipboard Quick Verification Once installed, verify it by typing: powershell winget --version Use code with caution. Copied to clipboard

If you get an error that the command isn't recognized, you might need to enable its App execution alias in Settings > Apps > App execution aliases. Helpful "Interesting" Commands

Now that you have it, here is what makes WinGet "interesting":

Update Everything: winget upgrade --all — Updates all your installed apps at once.

Export Your Setup: winget export -o myapps.json — Saves a list of all your apps to a file.

Import on a New PC: winget import -i myapps.json — Reinstalls all those apps on a fresh Windows install automatically.

Use WinGet to install and manage applications | Microsoft Learn

WinGet (Windows Package Manager) has become an essential tool for developers and IT professionals, but it isn't always active by default—especially on older Windows 10 versions, Windows Server, or fresh installations.

This guide provides the most up-to-date PowerShell methods to install WinGet in 2026, ranging from quick one-liners to robust manual installations for restricted environments. Method 1: The One-Line Script (Recommended for Most Users)

If you want the fastest, automated way to install WinGet and all its required dependencies (like VCLibs and UI Xaml), you can use a community-verified script. The asheroto/winget-install script is widely used because it detects your system architecture and fetches the latest version automatically. To run it, open PowerShell as Administrator and paste: powershell

# Installs WinGet immediately using a trusted community script irm asheroto.com/winget | iex Use code with caution.

Note: Using -Force (e.g., irm asheroto.com/winget | iex -Arguments "-Force") will reinstall WinGet even if it's already present, which is helpful for repairing broken installations. Method 2: Official "Repair-WinGet" Method

Microsoft now provides a dedicated PowerShell module, Microsoft.WinGet.Client, which includes a Repair-WinGetPackageManager cmdlet. This is the official way to "bootstrap" WinGet on a system where it is missing or corrupted. Install the WinGet Client module: powershell

Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery Use code with caution. Bootstrap WinGet: powershell

# Use -AllUsers for system-wide installation Repair-WinGetPackageManager -AllUsers Use code with caution. Method 3: Manual Installation (Best for Servers/Sandbox)

In restricted environments like Windows Server 2025 or Windows Sandbox, the Microsoft Store isn't available to handle background updates. You must manually install the dependencies before the WinGet bundle.

Step 1: Download PrerequisitesYou need the following packages from the official WinGet GitHub releases:

MSIX Bundle: Look for the latest file ending in .msixbundle.

License File: The .xml license file associated with the release.

Dependencies: Microsoft.VCLibs and Microsoft.UI.Xaml (usually found in the release notes or as separate .appx downloads).

Step 2: Install via PowerShellOnce downloaded, run these commands in order: powershell

# 1. Install Dependencies Add-AppxPackage -Path "C:\Path\To\Microsoft.VCLibs.x64.14.00.Desktop.appx" Add-AppxPackage -Path "C:\Path\To\Microsoft.UI.Xaml.2.8.appx" # 2. Install the WinGet Bundle Add-AppxPackage -Path "C:\Path\To\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle" # 3. Register the License (Required for full functionality) Add-AppxProvisionedPackage -Online -PackagePath "C:\Path\To\Microsoft.DesktopAppInstaller.msixbundle" -LicensePath "C:\Path\To\License.xml" Use code with caution. Method 4: Quick Force-Update (Already have "App Installer")

If you have the "App Installer" but the winget command still isn't working, it may just need to be registered for your user profile. Run this to register the existing package: powershell

Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe Use code with caution. Post-Installation Checklist

After installation, verify that WinGet is correctly set up by opening a new PowerShell window and running: powershell # Checks the installed version winget -v Use code with caution.

If it returns a version number (e.g., v1.9.xxxx), your installation was successful. You can now use PDQ's guide to keep your packages updated or Microsoft's documentation to explore advanced commands like winget upgrade --all.

Use WinGet to install and manage applications | Microsoft Learn

To install WinGet (Windows Package Manager) using PowerShell, the most reliable and updated method involves using the official Microsoft WinGet Client module. This approach is particularly useful for environments like Windows Sandbox, Windows Server, or fresh installations where the Microsoft Store might not be easily accessible. Prerequisites

Operating System: Windows 10 (version 1809 or higher) or Windows 11. Permissions: You must run PowerShell as an Administrator. Installation Steps

Launch PowerShell as AdministratorRight-click the Start button and select Terminal (Admin) or Windows PowerShell (Admin).

Install the WinGet Client ModuleRun the following commands to download the necessary package provider and the WinGet client module from the PowerShell Gallery: powershell

# Set progress preference to speed up installation $progressPreference = 'silentlyContinue' # Install NuGet provider if not present Install-PackageProvider -Name NuGet -Force | Out-Null # Install the official Microsoft WinGet Client module Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery | Out-Null Use code with caution. Copied to clipboard

Bootstrap WinGetUse the built-in repair cmdlet to automatically download and install the latest stable version of WinGet and its dependencies: powershell Repair-WinGetPackageManager -AllUsers Use code with caution. Copied to clipboard

Verify InstallationConfirm WinGet is working by checking its version or running a simple search: powershell winget --version winget search powershell Use code with caution. Copied to clipboard Alternative: Direct One-Line Script

Use WinGet to install and manage applications | Microsoft Learn

Installing App Installer (which includes ) via PowerShell is the most reliable way to set up package management on Windows 10 and 11, especially on systems without Microsoft Store access. 1. Check for Existing Installation Before starting, verify if is already on your system. Open PowerShell and run: powershell winget --version Use code with caution. Copied to clipboard

If you see a version number, you're all set. If you get an "ObjectNotFound" error, proceed with the steps below. 2. Download the Latest Release You need the .msixbundle file and its required dependencies from the official Microsoft Winget GitHub repository

Run the following script to download the latest stable version directly to your Downloads folder: powershell

$url = (Invoke-RestMethod https://github.com).assets | Where-Object $_.name -like "*.msixbundle"

| Select-Object -ExpandProperty browser_download_url Invoke-WebRequest -Uri $url -OutFile

"$env:USERPROFILE\Downloads\Microsoft.DesktopAppInstaller.msixbundle" Use code with caution. Copied to clipboard 3. Install Dependencies

requires specific VCLibs and Framework packages to run. If these are missing, the installation will fail. Run this block to ensure they are present: powershell # Download VCLibs Invoke-WebRequest -Uri "https://aka.ms" "$env:USERPROFILE\Downloads\VCLibs.appx" # Install VCLibs Add-AppxPackage -Path "$env:USERPROFILE\Downloads\VCLibs.appx" Use code with caution. Copied to clipboard 4. Run the Installation Now, install the main package you downloaded in Step 2: powershell Add-AppxPackage -Path

"$env:USERPROFILE\Downloads\Microsoft.DesktopAppInstaller.msixbundle" Use code with caution. Copied to clipboard 5. Verify the Setup

Restart your PowerShell session to refresh the environment variables. Test the installation by searching for a common app: powershell winget search powertoys Use code with caution. Copied to clipboard Troubleshooting Tips Execution Policy

: If the scripts won't run, set your policy to bypass for the session: Set-ExecutionPolicy Bypass -Scope Process Admin Rights : Always run PowerShell as an Administrator to ensure the Add-AppxPackage command has the necessary permissions. Store Update : If you have access to the Microsoft Store, simply running

Get-AppxPackage -AllUsers -Name "Microsoft.DesktopAppInstaller" | Update-AppxPackage is a faster alternative for existing installs. into a single clickable

Step 2: Install via PowerShell Command

Microsoft allows you to trigger the Microsoft Store install via a protocol command. Run the following command:

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

This command opens the Microsoft Store page for the "App Installer." Click Get or Install.

Step 2: Download the Microsoft.DesktopAppInstaller bundle

$download = "https://github.com/microsoft/winget-cli/releases/download/$tag/Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle" $output = "$env:TEMP\winget.msixbundle" Invoke-WebRequest -Uri $download -OutFile $output

Step 3: Sync Environment Variables

Once installed, close your current PowerShell window and open a new one. WinGet adds itself to your System PATH, but existing PowerShell windows won't see the change until restarted.