Installing the Windows Package Manager (Winget) via PowerShell is the most efficient way to manage software on Windows 10 and 11. While Winget typically comes pre-installed via the App Installer, it can sometimes be missing, outdated, or corrupted.
This guide provides the updated, step-by-step process to manually install or repair Winget using PowerShell. Prerequisites
Before starting, ensure your system meets these requirements: OS: Windows 10 (version 1809 or later) or Windows 11. Permissions: You must run PowerShell as an Administrator.
Internet: An active connection to download the necessary packages from GitHub. Step 1: Open PowerShell as Administrator
To make changes to system packages, you need elevated privileges. Press the Windows Key. Type PowerShell.
Right-click Windows PowerShell and select Run as Administrator. Step 2: Check for Existing Installation
First, verify if Winget is already installed or if it just needs an update. Type the following command:winget --version If a version number appears: You already have it.
If you see "The term 'winget' is not recognized": Proceed with the installation steps below. Step 3: Install Winget via PowerShell
Since Winget is distributed as part of the Microsoft App Installer, we will download the latest bundle directly from the official Microsoft GitHub repository. 1. Download the Latest Release
Copy and paste this script into your PowerShell window to fetch the latest installer: powershell
$repo = "microsoft/winget-cli" $url = "https://github.com" $asset = Invoke-RestMethod -Uri $url | Select-Object -ExpandProperty assets | Where-Object $_.name -like "*.msixbundle" $downloadUrl = $asset.browser_download_url Invoke-WebRequest -Uri $downloadUrl -OutFile "$env:TEMP\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle" Use code with caution. 2. Install the Package
Once the download is complete, run the installation command: powershell
Add-AppxPackage -Path "$env:TEMP\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle" Use code with caution. Step 4: Install Dependencies (If Needed)
Winget requires specific UI frameworks to function. If the installation fails with a "missing dependency" error, run these commands to install the VCLibs: powershell
$vclibsUrl = "https://aka.ms" Invoke-WebRequest -Uri $vclibsUrl -OutFile "$env:TEMP\VCLibs.appx" Add-AppxPackage -Path "$env:TEMP\VCLibs.appx" Use code with caution. Step 5: Verify the Installation Restart your PowerShell session and type:winget --version You should now see the current version (e.g., v1.7.10861).
💡 Quick Start Tip: Try searching for an app immediately by typing winget search vlc. Troubleshooting Common Issues 404 Not Found
If the script fails to download, the GitHub API might be rate-limited or the naming convention has changed. You can manually download the .msixbundle from the official Winget GitHub Releases page. Execution Policy Error
If PowerShell blocks the script, run this command and try again:Set-ExecutionPolicy RemoteSigned -Scope Process App Installer Not Updating
If the Store version is stuck, you may need to reset the App Installer via:Get-AppxPackage Microsoft.DesktopAppInstaller | Reset-AppxPackage Why Use Winget? Automation: Install dozens of apps with one command.
Updates: Run winget upgrade --all to update every app on your PC at once.
Cleanliness: No more hunting for .exe or .msi files on sketchy websites.
If you'd like to know more about using Winget, tell me if you're interested in: Bulk installation scripts for new PC setups. Exporting your current app list to a backup file. Uninstalling stubborn bloatware using Winget commands.
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, you need to ensure the App Installer package is present and updated. While modern Windows 10 and 11 systems usually have it pre-installed, it sometimes needs a manual "kick" or update via the command line. 🛠️ Prerequisites OS: Windows 10 (version 1809 or later) or Windows 11. Permissions: Run PowerShell as Administrator. 🚀 Installation Steps 1. Check for Existing Installation First, see if winget is already active on your system. powershell winget --version Use code with caution. Copied to clipboard If a version number appears: You are good to go!
If "CommandNotFoundException" appears: Proceed to the steps below. 2. Download the Latest Installer
The easiest way to install winget is to pull the .msixbundle directly from the official GitHub repository. powershell
$url = "https://github.com" $dest = "$env:TEMP\winget.msixbundle" Invoke-WebRequest -Uri $url -OutFile $dest Use code with caution. Copied to clipboard 3. Install the Package Run this command to register the package with Windows. powershell Add-AppxPackage -Path $dest Use code with caution. Copied to clipboard 4. Verify the Install Restart your PowerShell window and run: powershell winget --info Use code with caution. Copied to clipboard 💡 Troubleshooting Common Issues
Dependency Error: If the installation fails due to missing UI frameworks, you can install the VCLibs dependency: powershell Add-AppxPackage -Uri "https://aka.ms" Use code with caution. Copied to clipboard
App Store Fix: Sometimes the simplest fix is to update "App Installer" via the Microsoft Store app directly.
Environment Variables: If winget isn't recognized after installation, try restarting your PC to refresh the system path. 📝 Essential Commands to Start Once installed, try these to see the power of the tool: Search for an app: winget search Install an app: winget install Update all apps: winget upgrade --all
New-Item -Path "$env:TEMP\winget-install" -ItemType Directory -Force
Set-Location "$env:TEMP\winget-install"
Windows Package Manager (winget) is Microsoft’s official command-line tool that allows you to discover, install, upgrade, and configure applications on Windows 10 and Windows 11. While it now ships by default with modern Windows versions (starting from Windows 10 version 1809 and Windows 11), many users—especially those running older builds, Windows Server, or lightweight Windows images—still find that winget is missing or severely outdated.
If you have ever typed winget –version into PowerShell only to see 'winget' is not recognized, you need to install or update it manually.
This guide covers everything you need to know about installing and updating Winget using PowerShell—specifically focusing on current, updated methods as of 2025.
Add-AppxPackage -Path "vclibs.appx"
Installing the Windows Package Manager (Winget) via PowerShell is the most efficient way to manage software on Windows 10 and 11. While Winget typically comes pre-installed via the App Installer, it can sometimes be missing, outdated, or corrupted.
This guide provides the updated, step-by-step process to manually install or repair Winget using PowerShell. Prerequisites
Before starting, ensure your system meets these requirements: OS: Windows 10 (version 1809 or later) or Windows 11. Permissions: You must run PowerShell as an Administrator.
Internet: An active connection to download the necessary packages from GitHub. Step 1: Open PowerShell as Administrator
To make changes to system packages, you need elevated privileges. Press the Windows Key. Type PowerShell.
Right-click Windows PowerShell and select Run as Administrator. Step 2: Check for Existing Installation
First, verify if Winget is already installed or if it just needs an update. Type the following command:winget --version If a version number appears: You already have it.
If you see "The term 'winget' is not recognized": Proceed with the installation steps below. Step 3: Install Winget via PowerShell
Since Winget is distributed as part of the Microsoft App Installer, we will download the latest bundle directly from the official Microsoft GitHub repository. 1. Download the Latest Release
Copy and paste this script into your PowerShell window to fetch the latest installer: powershell
$repo = "microsoft/winget-cli" $url = "https://github.com" $asset = Invoke-RestMethod -Uri $url | Select-Object -ExpandProperty assets | Where-Object $_.name -like "*.msixbundle" $downloadUrl = $asset.browser_download_url Invoke-WebRequest -Uri $downloadUrl -OutFile "$env:TEMP\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle" Use code with caution. 2. Install the Package
Once the download is complete, run the installation command: powershell
Add-AppxPackage -Path "$env:TEMP\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle" Use code with caution. Step 4: Install Dependencies (If Needed)
Winget requires specific UI frameworks to function. If the installation fails with a "missing dependency" error, run these commands to install the VCLibs: powershell install winget using powershell updated
$vclibsUrl = "https://aka.ms" Invoke-WebRequest -Uri $vclibsUrl -OutFile "$env:TEMP\VCLibs.appx" Add-AppxPackage -Path "$env:TEMP\VCLibs.appx" Use code with caution. Step 5: Verify the Installation Restart your PowerShell session and type:winget --version You should now see the current version (e.g., v1.7.10861).
💡 Quick Start Tip: Try searching for an app immediately by typing winget search vlc. Troubleshooting Common Issues 404 Not Found
If the script fails to download, the GitHub API might be rate-limited or the naming convention has changed. You can manually download the .msixbundle from the official Winget GitHub Releases page. Execution Policy Error
If PowerShell blocks the script, run this command and try again:Set-ExecutionPolicy RemoteSigned -Scope Process App Installer Not Updating
If the Store version is stuck, you may need to reset the App Installer via:Get-AppxPackage Microsoft.DesktopAppInstaller | Reset-AppxPackage Why Use Winget? Automation: Install dozens of apps with one command.
Updates: Run winget upgrade --all to update every app on your PC at once.
Cleanliness: No more hunting for .exe or .msi files on sketchy websites.
If you'd like to know more about using Winget, tell me if you're interested in: Bulk installation scripts for new PC setups. Exporting your current app list to a backup file. Uninstalling stubborn bloatware using Winget commands.
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 Step 2: Create a temp folder New-Item -Path
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. How to Install and Update Winget Using PowerShell
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, you need to ensure the App Installer package is present and updated. While modern Windows 10 and 11 systems usually have it pre-installed, it sometimes needs a manual "kick" or update via the command line. 🛠️ Prerequisites OS: Windows 10 (version 1809 or later) or Windows 11. Permissions: Run PowerShell as Administrator. 🚀 Installation Steps 1. Check for Existing Installation First, see if winget is already active on your system. powershell winget --version Use code with caution. Copied to clipboard If a version number appears: You are good to go!
If "CommandNotFoundException" appears: Proceed to the steps below. 2. Download the Latest Installer
The easiest way to install winget is to pull the .msixbundle directly from the official GitHub repository. powershell
$url = "https://github.com" $dest = "$env:TEMP\winget.msixbundle" Invoke-WebRequest -Uri $url -OutFile $dest Use code with caution. Copied to clipboard 3. Install the Package Run this command to register the package with Windows. powershell Add-AppxPackage -Path $dest Use code with caution. Copied to clipboard 4. Verify the Install Restart your PowerShell window and run: powershell winget --info Use code with caution. Copied to clipboard 💡 Troubleshooting Common Issues
Dependency Error: If the installation fails due to missing UI frameworks, you can install the VCLibs dependency: powershell Add-AppxPackage -Uri "https://aka.ms" Use code with caution. Copied to clipboard
App Store Fix: Sometimes the simplest fix is to update "App Installer" via the Microsoft Store app directly.
Environment Variables: If winget isn't recognized after installation, try restarting your PC to refresh the system path. 📝 Essential Commands to Start Once installed, try these to see the power of the tool: Search for an app: winget search Install an app: winget install Update all apps: winget upgrade --all
New-Item -Path "$env:TEMP\winget-install" -ItemType Directory -Force
Set-Location "$env:TEMP\winget-install"
Windows Package Manager (winget) is Microsoft’s official command-line tool that allows you to discover, install, upgrade, and configure applications on Windows 10 and Windows 11. While it now ships by default with modern Windows versions (starting from Windows 10 version 1809 and Windows 11), many users—especially those running older builds, Windows Server, or lightweight Windows images—still find that winget is missing or severely outdated.
If you have ever typed winget –version into PowerShell only to see 'winget' is not recognized, you need to install or update it manually.
This guide covers everything you need to know about installing and updating Winget using PowerShell—specifically focusing on current, updated methods as of 2025.
Add-AppxPackage -Path "vclibs.appx"