Install Winget Using Powershell Hot [updated] May 2026
To install using PowerShell, you can use the official Microsoft module or a community-driven script. This is especially useful for Windows Server or "clean" installations where the Microsoft Store might be missing. Microsoft Learn
Method 1: Use the Microsoft WinGet Client Module (Recommended)
This is the most reliable way to bootstrap WinGet on modern versions of Windows. Microsoft Learn Open PowerShell as Administrator. Install the WinGet Client module: powershell
Install-PackageProvider -Name NuGet -Force Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery Use code with caution. Copied to clipboard Run the repair/bootstrap command: powershell Repair-WinGetPackageManager -AllUsers Use code with caution. Copied to clipboard -IncludePrerelease if you need the latest preview version. Microsoft Learn Method 2: Register via App Installer (Fast Fix)
If WinGet is already on your system but not responding, you can force its registration with this one-liner: Microsoft Learn powershell
Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe Use code with caution. Copied to clipboard Method 3: The "Hot" Community Script (Automated)
If you are on a system without any prerequisites (like VCLibs or Xaml), this community-maintained script from handles the entire dependency chain. Download and run the installer script: powershell Install-Script -Name winget-install winget-install Use code with caution. Copied to clipboard
This script automatically fetches the latest stable version of WinGet, installs necessary VCLibs, and updates your User PATH. Verification After installation, restart your terminal and type: powershell winget --version Use code with caution. Copied to clipboard If successful, it will return the version number (e.g., v1.9.25150 Microsoft Learn all your favorite apps at once?
Use WinGet to install and manage applications | Microsoft Learn 24-Mar-2026 —
Here is the "Hot" method—using PowerShell to install winget directly via the Microsoft Store.
Method 2: The One-Liner Execution (For Scripting Gods)
If you need to deploy Winget across 100 PCs yesterday, use this aggressive one-liner. This script checks your OS architecture, downloads the correct bundle, and installs it silently via PowerShell.
Copy and paste this entire block into PowerShell (Admin):
$progressPreference = 'silentlyContinue'; Write-Host "Downloading Winget..." -ForegroundColor Cyan; Invoke-WebRequest -Uri "https://aka.ms/getwinget" -OutFile "$env:TEMP\Microsoft.DesktopAppInstaller.msixbundle"; Add-AppxPackage -Path "$env:TEMP\Microsoft.DesktopAppInstaller.msixbundle"; Write-Host "Installation Complete!" -ForegroundColor Green
What this does:
Invoke-WebRequestdownloads the bundle instantly.Add-AppxPackageinstalls it without any GUI popups.
Note: If you get a "No applicable app packages" error, you need to install the VCLibs dependencies first (see troubleshooting below).
Troubleshooting (if winget not found after install)
- Restart PowerShell (Admin)
- Log off and on (refreshes PATH)
- Add to PATH manually (rarely needed):
$env:Path += ";$env:LOCALAPPDATA\Microsoft\WindowsApps"
Conclusion: Stop Clicking, Start Scripting
Knowing how to install winget using PowerShell hot is a superpower. It turns a tedious manual download into a 30-second script.
- Method 1 (
Repair-WinGetPackageManager) is your bread and butter. - Method 2 (The One-Liner) is for mass deployment.
- Method 3 (Provisioning) is for broken systems.
Now that you have Winget installed, your Windows machine is no longer a second-class citizen in the world of package management. Go forth and install everything from winget install Microsoft.PowerShell to winget install Valve.Steam without ever opening a browser again.
Next Step: Automate this script to run on every new PC setup via your $PROFILE or a startup script. Happy scripting.
Keywords used: install winget using powershell, install winget using powershell hot, winget powershell, windows package manager install, fast winget install.
How to Install Winget Using PowerShell: The Ultimate Guide The Windows Package Manager, or Winget, is a game-changer for anyone who wants to manage software like a pro. Instead of hunting down .exe files on sketchy websites, you can install, update, and configure apps with a single command. If you are looking to get this running quickly, PowerShell is your best friend.
Here is everything you need to know to install Winget using PowerShell and get your environment up to speed. Why Use Winget?
Before we dive into the commands, it is worth understanding why this tool is essential: Bulk Installation: Install dozens of apps with one script. Security: Source apps directly from official repositories.
Automation: Keep all your software updated with a single line of code. install winget using powershell hot
Cleanliness: Avoid bloatware and "next-next-finish" installers. Step 1: Check if Winget is Already Installed
Modern versions of Windows 10 and 11 usually come with Winget pre-installed via the "App Installer" package. Open PowerShell and type: winget --version
If you see a version number, you are good to go. If you get an error saying the term is not recognized, proceed to the installation steps below. Step 2: Install Winget via PowerShell (The Quick Way)
The most reliable way to install Winget manually is by downloading the .msixbundle directly from the official GitHub repository. You can do this entirely within PowerShell. Open PowerShell as Administrator. Run the following command to download the latest installer:
Invoke-WebRequest -Uri https://github.com -OutFile .\WingetInstaller.msixbundle Install the package using the Add-AppxPackage command: Add-AppxPackage .\WingetInstaller.msixbundle Step 3: Verify and Troubleshoot
Once the installation finishes, try running winget again. If it still doesn't work, you may need to install the necessary dependencies, specifically the Microsoft UI Xaml framework.
You can often fix "missing dependency" errors by updating the Microsoft Store. Run this command to force a check for updates:
Get-CimInstance -Namespace root/Microsoft/Windows/Appx -ClassName SoftwareInventory | Where-Object Name -eq "Microsoft.DesktopAppInstaller" Pro Tips for Using Winget
Now that you have it installed, here are the first commands you should run: Search for an app: winget search Install an app: winget install Update all your apps: winget upgrade --all List installed software: winget list
🚀 Key Point: Always run PowerShell as an Administrator when installing software to avoid permission prompts. Conclusion
Installing Winget via PowerShell is a straightforward process that unlocks a more efficient way to manage your Windows machine. By bypassing manual downloads, you save time and ensure your system stays updated with the latest, most secure versions of your favorite tools. If you'd like to take your setup even further:
List of essential developer tools to install via Winget (e.g., VS Code, Git) How to create a setup script for new PCs Managing private repositories with Winget
Installing using PowerShell is often referred to as the "hot" method because it allows for rapid, scriptable deployment without needing the Microsoft Store GUI. This is particularly useful for setting up fresh Windows installations or managing remote machines. Overview of PowerShell Installation Methods
While WinGet is typically part of the "App Installer" package, it can be manually bootstrapped or repaired via PowerShell if it's missing or broken. The "Scripted" Method (PSGallery)
The most direct way to install WinGet via PowerShell is by using specialized scripts available in the PowerShell Gallery. Install-Script -Name winget-install PowerShell Gallery : After installing the script, running winget-install
automates the download of the latest version and its dependencies The "Repair" Method (Official)
For modern Windows systems where the framework exists but the tool is unreachable, Microsoft provides a dedicated cmdlet. Repair-WinGetPackageManager -AllUsers Andrew S Taylor : This is often used in Windows Sandbox
or environments where the Microsoft Store hasn't yet registered the tool Microsoft Learn The "Manual Direct" Method (MSIXBundle)
If scripts are blocked, you can manually fetch the bundle directly from Microsoft's servers.
Invoke-WebRequest -Uri https://aka.ms/getwinget -OutFile winget.msixbundle then install it with Add-AppxPackage winget.msixbundle Stack Overflow Performance & Reliability Review
: These PowerShell methods are significantly faster than opening the Microsoft Store and searching for "App Installer" Versatility Add-AppxPackage method is highly effective for remote deployments via PowerShell sessions where a GUI is unavailable Dependency Management : Standard PowerShell commands (like Add-AppxPackage ) may fail silently if dependencies like are missing Microsoft Learn . Using the winget-install Repair-WinGetPackageManager To install using PowerShell, you can use the
is generally "hotter" (more effective) because they handle these prerequisites automatically Microsoft Learn Critical Requirements
Use WinGet to install and manage applications | Microsoft Learn
Install WinGet Using PowerShell: The Ultimate "Hot" Guide Installing the Windows Package Manager (WinGet) via PowerShell is the most efficient way to manage software on Windows 10, 11, and Windows Server. While WinGet is often pre-installed on modern builds, environment issues or "broken" installations often require a fresh, automated setup via the command line. 1. Verify Current Installation
Before installing, check if WinGet is already active on your system. Open PowerShell as an Administrator and run: powershell winget --version Use code with caution.
If you see a version number (e.g., v1.7.10861), it is already installed. If you receive an error stating the term is "not recognized," proceed with the methods below. 2. Method 1: The Modern PowerShell Module (Recommended)
Microsoft now provides a dedicated PowerShell module that can bootstrap the client. This is the cleanest method for most users. Open PowerShell as Administrator. Install the Client Module: powershell
Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery Use code with caution.
Repair/Bootstrap WinGet: This command triggers the download and registration of the WinGet package manager for all users. powershell Repair-WinGetPackageManager -AllUsers Use code with caution. 3. Method 2: Manual Installation via AppxPackage
If the module fails, you can manually fetch the .msixbundle and its dependencies (VCLibs and UI Xaml) directly through PowerShell. Download and Install the Bundle: powershell
$url = "https://aka.ms/getwinget" Invoke-WebRequest -Uri $url -OutFile "winget.msixbundle" Add-AppxPackage -Path ".\winget.msixbundle" Use code with caution.
Handle Dependencies: WinGet often requires the Microsoft UI Xaml and VC++ Desktop Framework packages. Without these, the installation may fail silently. You can automate this process using community-verified scripts like the winget-installer on GitHub. 4. Method 3: One-Liner Community Script
For a "hot" and fast installation, you can use a verified community script that handles architecture detection and dependency installation automatically. powershell # Trusted community script from Use code with caution. powershell GitHub (GerardoG) Invoke-WebRequest Use code with caution. powershell
To install WinGet (the Windows Package Manager) using PowerShell, you can use the official Microsoft client module or direct download scripts. While WinGet is typically pre-installed on Windows 10 (1809+) and Windows 11, it sometimes needs to be "bootstrapped" manually if it's missing. Option 1: The Fast PowerShell Module Method (Recommended)
This is the most reliable way as it automatically handles all dependencies like Microsoft UI Xaml and VCLibs.
Open PowerShell as Administrator: Press Win + X and select Terminal (Admin) or PowerShell (Admin). Run the following commands: powershell
# Install the package provider and WinGet client module Install-PackageProvider -Name NuGet -Force | Out-Null Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery | Out-Null # Use the repair cmdlet to bootstrap/install the WinGet client Repair-WinGetPackageManager -AllUsers Use code with caution. Copied to clipboard Option 2: The Direct Download Script
If you prefer a direct script to pull the installer bundle from Microsoft's servers, use this one-liner: powershell
Invoke-WebRequest -Uri https://aka.ms/getwinget -OutFile winget.msixbundle Add-AppxPackage winget.msixbundle Remove-Item winget.msixbundle Use code with caution. Copied to clipboard Option 3: Official GitHub "Hot" Install
For the latest release, you can use PowerShell to fetch the direct link from the official Microsoft GitHub repository, download the .msixbundle file, and install it directly. How to Verify It Worked
To verify installation, open a new PowerShell window and run winget --version. You can test functionality by searching for an application.
To install WinGet (Windows Package Manager) using PowerShell, you can use the official Repair-WinGetPackageManager cmdlet or a manual installation script if the App Installer is missing. 🛠️ Method 1: The Modern Official Way (Recommended) What this does:
This is the fastest method to ensure WinGet is bootstrapped correctly along with its dependencies. powershell
# 1. Install the PowerShell module Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery # 2. Bootstrap/Repair WinGet Repair-WinGetPackageManager -AllUsers Use code with caution. Copied to clipboard
Verification: Close and reopen your terminal, then type winget --version. 💻 Method 2: Manual PowerShell Script
If you can't access the Microsoft Store, use this script to pull the latest .msixbundle directly from the official GitHub releases. powershell # Get the latest download URL from Use code with caution. Copied to clipboard powershell GitHub Use code with caution. Copied to clipboard powershell
$API_URL = "https://api.github.com/repos/microsoft/winget-cli/releases/latest" $DOWNLOAD_URL = $(Invoke-RestMethod $API_URL).assets.browser_download_url | Where-Object $_.EndsWith(".msixbundle") # Download and Install Invoke-WebRequest -URI $DOWNLOAD_URL -OutFile winget.msixbundle -UseBasicParsing Add-AppxPackage winget.msixbundle # Clean up Remove-Item winget.msixbundle Use code with caution. Copied to clipboard 🚀 Why use WinGet?
Once installed, you can manage your entire software library with simple commands: Search for apps: winget search Install an app: winget install Update everything: winget upgrade --all
For more detailed troubleshooting, refer to the Microsoft WinGet Guide.
Use WinGet to install and manage applications | Microsoft Learn
Quick Winget Usage After Install
winget search chrome
winget install Google.Chrome
winget upgrade --all
Hot Tip: On most modern Windows 10/11, winget is already present but hidden. Just run winget in Admin PowerShell — if not found, use Method 2 above for the fastest automated fix.
To install WinGet via PowerShell, you can use a one-line command to download the installer directly from Microsoft and execute it. This is particularly useful if the Microsoft Store is unavailable or if you need to automate the setup on multiple machines. Quick One-Line Installation
Run PowerShell as Administrator and paste the following command to download and install the latest WinGet bundle: powershell
$url = "https://aka.ms/getwinget"; $out = "winget.msixbundle"; Invoke-WebRequest -Uri $url -OutFile $out; Add-AppxPackage $out; Remove-Item $out Use code with caution. Copied to clipboard Advanced Method: Official PowerShell Module
For more robust environments (like Windows Sandbox or Server), you can use the official Microsoft.WinGet.Client module to bootstrap the installation: Install the Module: powershell
Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery Use code with caution. Copied to clipboard
Repair/Bootstrap WinGet:This command automatically handles dependencies like VCLibs and Xaml: powershell Repair-WinGetPackageManager -AllUsers Use code with caution. Copied to clipboard Verify Installation
After running either method, restart your terminal and type: powershell winget --version Use code with caution. Copied to clipboard Why use PowerShell for WinGet?
Automation: Perfect for deployment scripts and fresh Windows installs.
No Store Required: Bypasses the need for a Microsoft account or the Store app.
Dependency Management: Modern scripts automatically fetch required libraries like Microsoft.UI.Xaml.
For a visual walkthrough of these installation methods, check out this guide: 07:21 Installing Winget on Windows 10: A Comprehensive Guide Kevin Kaminski YouTube• Aug 10, 2023
Use WinGet to install and manage applications | Microsoft Learn
Here’s a concise review of the phrase "install winget using powershell hot" — likely a search query or command attempt.
Method 3: Install via PackageManagement (Fallback)
# Install Microsoft's VCLibs dependencies first
Add-AppxPackage -Path "https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx"