How to Install Winget on Windows Server

Windows Package Manager (Winget) is a game changer for system admins and power users who want to automate app installations on Windows. But if you’re running Windows Server, you might notice Winget isn’t there by default. Here’s how to get it working on your server—no fluff, just the steps.

What is Winget?

Winget is Microsoft’s command-line tool for installing and managing software. It works on Windows 10, 11, and, with a little work, on most recent Windows Server versions.

Why Isn’t Winget Pre-installed on Windows Server?

Microsoft doesn’t bundle Winget with Windows Server by default. The main reason is that Winget relies on the App Installer package, which is tied to the Microsoft Store—also missing from Windows Server. But with a manual approach, you can get it working.

Requirements

• Windows Server 2019, 2022 or later (Desktop Experience recommended)
• Internet connection
• Administrator privileges

Step 1: Enable the Microsoft Store (Optional, but recommended)

If your environment allows, enabling the Microsoft Store makes things easier. However, most servers run without it, so we’ll cover the manual route.

Step 2: Download the App Installer Package

1. Go to the official Microsoft Store listing for App Installer.
2. You can’t install directly from the Store on Windows Server, so copy the App Installer link.
3. Use a tool like store.rg-adguard.net:
   • Paste the App Installer URL.
   • Select “Retail.”
   • Download the latest .msixbundle file for App Installer.

Step 3: Install Dependencies

Before installing App Installer, make sure these dependencies are present:

• VC_Libs.x64
• Microsoft.UI.Xaml

You’ll see these in the results on the adguard.net page. Download the latest x64 versions.

Step 4: Install the Dependencies and App Installer

1. Open PowerShell as Administrator.
2. Install each package using:
   Add-AppxPackage -Path "C:\Path\To\File.msixbundle"
   Replace with the path to each downloaded file.
3. Start with the VC_Libs package, then Microsoft.UI.Xaml, and finally App Installer.

Step 5: Test Winget

After installing App Installer, open a new PowerShell window and run:

winget --version

You should see the installed version number. If not, reboot the server and try again.

Common Issues

• Error about missing dependencies: Double-check you installed all required packages in order.
• Winget not recognized: Log off or reboot after installation.
• No Microsoft Store: That’s normal. As long as you install App Installer manually, you don’t need the Store.

Final Thoughts

Winget makes life easier when managing Windows Server environments. With a few manual steps, you can unlock automated software installs and updates—no Store required.

If you run into trouble, check the official Microsoft Docs for the latest compatibility notes.

Need more automation tips for Windows Server? Drop your questions in the comments.

Mark Vincent

Tech enthusiast and content creator passionate about making technology simple for everyone. I share practical tips, guides, and reviews on the latest in computers, software, and gadgets. Let’s explore the digital world together!