Install Winget Using Powershell Updated Fix

To install and update (Windows Package Manager) using PowerShell, use the official Microsoft.WinGet.Client

. This is the most reliable method for modern systems, including Windows 10, 11, and Windows Sandbox Microsoft Learn 🛠️ Quick Installation (The "Modern" Way) Run these commands in an Administrative PowerShell Install the WinGet Client module: powershell

Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery Use code with caution. Copied to clipboard Bootstrap/Repair the WinGet executable: powershell Repair-WinGetPackageManager -AllUsers Use code with caution. Copied to clipboard Verify the installation: powershell winget --version Use code with caution. Copied to clipboard 📦 Alternative Manual Method (Direct Download)

If the module method fails or you are on a restricted system, you can manually download and install the package bundle directly from Microsoft's servers Stack Overflow powershell # Download the latest bundle Invoke-WebRequest -Uri "https://aka.ms/getwinget" "winget.msixbundle" # Install the package Add-AppxPackage winget.msixbundle # Clean up Remove-Item winget.msixbundle Use code with caution. Copied to clipboard 🔄 How to Update WinGet WinGet typically updates itself via the Microsoft Store

(as the "App Installer"). However, you can force an update through PowerShell Update All Apps (Including WinGet): powershell winget upgrade --all Use code with caution. Copied to clipboard Update via PowerShell Module: If you used the Microsoft.WinGet.Client

module, simply run the repair command again to pull the latest stable version: powershell Repair-WinGetPackageManager Use code with caution. Copied to clipboard ⚠️ Common Troubleshooting Missing Dependencies: On older systems or Windows Server, WinGet requires Microsoft UI Xaml Microsoft Learn Repair-WinGetPackageManager cmdlet usually handles these automatically Path Issues:

isn't recognized after installation, restart your PowerShell session or your computer to refresh environment variables PowerShell Gallery Execution Policy: If you can't run scripts, set the policy temporarily: powershell Set-ExecutionPolicy RemoteSigned -Scope Use code with caution. Copied to clipboard Export a list of your current apps to a "winget import" file. Set up a scheduled task to keep all your software updated daily. Configure settings like progress bar styles or experimental features.

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. install winget using powershell updated

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") To install and update (Windows Package Manager) using

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

The modern way to install winget (Windows Package Manager) via PowerShell is by using the Microsoft Store release ID. This method is faster and more reliable than the older GitHub release script methods.

Here is the updated guide.

Common errors & fixes

| Error | Fix | |-------|-----| | Add-AppxPackage fails | Enable Developer Mode: Settings > Update & Security > For developers | | 0x80073D05 | Install all missing dependencies (VCLibs, UI.Xaml) | | winget not recognized | Log off / restart, or add %LOCALAPPDATA%\Microsoft\WindowsApps to PATH | | Windows LTSC | Install App Installer from Store using wsreset -i or manually via .appx |

---

Method 3: Using the official PowerShell script (community maintained)

# One-liner to get winget on Windows 10/11
irm https://raw.githubusercontent.com/rom MMV/winget-install/master/install-winget.ps1 | iex

⚠️ Always inspect remote scripts before piping to iex.

---

Step 5: What If Winget Is Installed But Not Working?

Some users report that winget commands hang or fail even after installation. This usually relates to Windows’ execution policy or corrupted sources.

Reset the Winget sources:

winget source reset --force

Check your PowerShell execution policy:

Get-ExecutionPolicy

If it’s Restricted, run:

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

Then retry Winget commands.

Repair the App Installer package using PowerShell:

Get-AppxPackage Microsoft.DesktopAppInstaller | Repair-AppxPackage

---

Error: 0x80073DFA or 0x80073CF6 (Installation Failed)

Cause: Appx dependencies or store cache issues. Fix: Reset the Microsoft Store cache and try installing via the Store again:

wsreset.exe -i

---

Method A: Install via App Installer (Recommended)

Winget is part of the App Installer package from the Microsoft Store. You can download and install it directly using PowerShell.

# Add the Microsoft Store source if missing (rarely needed)
Add-WindowsPackage -Online -PackagePath "Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle" -ErrorAction SilentlyContinue

But a cleaner way is to use a script that fetches the latest bundle from Microsoft’s CDN:

# Run as Administrator
$githubUrl = "https://api.github.com/repos/microsoft/winget-cli/releases/latest"
$release = Invoke-RestMethod -Uri $githubUrl
$asset = $release.assets | Where-Object  $_.name -like "*.msixbundle" 
$downloadUrl = $asset.browser_download_url
$output = "$env:TEMP\winget.msixbundle"
Invoke-WebRequest -Uri $downloadUrl -OutFile $output
Add-AppxPackage -Path $output

After running these commands, close and reopen PowerShell as Administrator, then test with winget --version.