Install Winget Using Powershell Hot ~upd~ Jun 2026

If the command returns a version number, Winget is already available on your system. If you receive an error message indicating 'winget' is not recognized as a command, proceed with the installation methods below.

Once installed, you can manage your entire software library with simple commands: winget search Install an app: winget install Update everything: winget upgrade --all

Method 1: The "Hot" Way - Using PowerShell Script (Recommended)

$apps = @( # Development Tools @Name = "Visual Studio Code"; Id = "Microsoft.VisualStudioCode"; Type = "winget", @Name = "Git"; Id = "Git.Git"; Type = "winget", @Name = "GitHub Desktop"; Id = "GitHub.GitHubDesktop"; Type = "winget", @Name = "Node.js"; Id = "OpenJS.NodeJS"; Type = "winget", @Name = "Python 3.12"; Id = "Python.Python.3.12"; Type = "winget", @Name = "Docker Desktop"; Id = "Docker.DockerDesktop"; Type = "winget", install winget using powershell hot

# Download Invoke-WebRequest -Uri $downloadUrl -OutFile $msixPath

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

This command tells PowerShell to look for the "App Installer" (which contains winget) by its family name. If it is not installed or is outdated, it triggers a background update/install from the Microsoft Store. If the command returns a version number, Winget

If you need maximum control over the installation process, such as in air-gapped environments or when you want to install a specific version, the manual approach is ideal.

: You are missing the required Visual C++ or UI Xaml dependencies.

"apps": [ "id": "Microsoft.VisualStudioCode", "version": "latest" , "id": "Git.Git", "version": "latest" , "id": "Google.Chrome", "version": "latest" ] : You are missing the required Visual C++

Invoke-WebRequest -Uri $downloadUrl -OutFile $output Add-AppxPackage -Path $output

$downloadUrl = $asset.browser_download_url $msixPath = Join-Path $tempDir $asset.name

To verify installation, open a new PowerShell window and run winget --version . You can test functionality by searching for an application.

Windows Server editions do not include the Microsoft Store infrastructure by default. Because Winget relies on AppX framework dependencies, installing it on Windows Server requires downloading and registering specific prerequisite packages first. Step 1: Download Required Dependencies