|work| — Install Winget Using Powershell Updated

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

$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. Step 1: Check if Winget Is Already Installed

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.

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 If you see a version number (e

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


Step 1: Check if Winget Is Already Installed

Open PowerShell as Administrator and run:

winget --version

To check for an outdated version, compare your version with the latest Winget release on GitHub. As of early 2025, the stable version is v1.8.x or higher.


Troubleshooting Common Errors

Verify installation

winget --version
winget search git