Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Windows Server » How to Install Winget on Windows Server

How to Install Winget on Windows Server

Posted on 22/08/202418/03/2025 Matthew By Matthew No Comments on How to Install Winget on Windows Server
How to Install Winget on Windows Server
How to Install Winget on Windows Server

Winget, also known as the Windows Package Manager, is a powerful tool that simplifies the installation, updating, and management of software packages on Windows systems. This guide will walk you through the process of getting Winget up and running on a Windows Server, specifically focusing on versions like Windows Server 2022 and 2019. Please see Install and Manage Applications with Winget, How to keep Apps up to date on Windows devices, how to install Windows Package Manager (Winget CLI), and Windows App Package: How to Bundle MSIX packages.

Note: Windows installs WinGet by default on Windows Server 2025, providing a command-line package manager tool for installing applications on Windows devices.

Although Windows 10 and 11 officially support Winget, installing it on a Windows Server environment can be more complex due to dependency issues.

What is Winget?

Winget is an open-source package manager developed by Microsoft, designed specifically for Windows 10 and 11. It allows users to install, update, uninstall, and configure applications from the command line, making software management on Windows as seamless as it is on Linux.

Core Features of Winget:

Below are some Winget Core features.

  • Open-Source: The code for Winget is available on GitHub, providing transparency and encouraging community contributions.
  • Command-Line Interface: No more navigating through the Microsoft Store or third-party websites. With Winget, you can manage software directly from PowerShell or the command prompt.
  • Automation-Friendly: You can easily script Winget, making it ideal for system administrators and DevOps teams to automate software management tasks.
  • Supports Multiple Package Types: Winget handles not only EXE files but also MSI and MSIX packages.

Prerequisites

Before you start, ensure that you meet the following prerequisites:

  • Windows Server Version: Make sure you’re not using Windows Server Core, as Winget isn’t supported there.
  • Dependencies: You’ll need to install Microsoft.UI.Xaml.2.7.x and Microsoft.VCLibs.x64.
  • Administrator Access: Ensure you have admin rights on the server.

You may be interested in these articles: How to install, upgrade and uninstall Chocolatey, how to install, upgrade and uninstall software with Chocolatey, and how to install applications with Winget CLI on Windows.

Step 1: Install Microsoft UI XAML & VCLibs

Since Winget isn’t natively included with Windows Server, you’ll need to manually install its dependencies, starting with Microsoft UI XAML and Microsoft VCLibs.

Installing Microsoft.UI.Xaml

Visit the NuGet webpage for Microsoft UI XAML 2.7 and download the package.

Download Microsoft UI xaml package
Download Microsoft UI xaml package

After downloading, rename the file extension from .nupkg to .zip.

Rename the file to zip file
Rename the file to zip file

Extract the contents of the zip file.

Extract file
Extract file

Open PowerShell as administrator and navigate to the folder path where you extracted the files using the cmdlet below.

cd C:\Users\downloads\microsoft.ui.xaml.2.7.3

Run the following command to install the package:

Add-AppxPackage -Path .\tools\AppX\x64\Release\Microsoft.UI.Xaml.2.7.appx
Install Microsoft UI Xaml package
Install Microsoft UI Xaml package

Install Visual C++ Runtime Library (VCLibs 14)

Visit the Microsoft website and download the appropriate version of Microsoft.VCLibs.x64, based on your system architecture.

Open PowerShell in the directory where the VCLibs file is saved, and run the following command to install the package:

Add-AppxPackage -Path .\Microsoft.VCLibs.x64.appx
Install Microsoft VCLibs package
Install Microsoft VCLibs package

Step 2: Install Microsoft Desktop App Installer and Winget

With the dependencies installed, you can now proceed to install the Winget tool itself.

Go to the GitHub releases page for Winget and download the Microsoft.DesktopAppInstaller.msixbundle file along with its corresponding license file.

Download windows package manager bundle and license file
Download windows package manager bundle and license file

Open PowerShell in the directory where you saved the Winget package, and run the following command to install Winget:

Add-AppxPackage .\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle

Run the following command to apply the license file:

Add-AppxProvisionedPackage -Online -Package .\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle -LicensePath .\24146eb205d040e69ef2d92d7034d97f_License1.xml
Install windows package manager bundle and license file
Install windows package manager bundle and license file

Step 3: Verify the Installation

After completing the installation, it’s important to verify that Winget is properly installed and functioning.

Open a new PowerShell window as an administrator. Type winget and press Enter.

Winget command
Winget command

If installed correctly, you should see a list of Winget commands.

Conclusion

While Winget isn’t included with Windows Server out of the box, this guide shows that installing it manually is a relatively straightforward process. Once set up, Winget provides a powerful, Linux-like package management experience on Windows Server, making software installation, updates, and management more efficient and less time-consuming.

This tool is an excellent addition to any Windows Server environment, particularly for those who value automation and streamlined workflows.

I hope you found this article useful on “How to Install Winget on Windows Server.” Please feel free to leave a comment below.

5/5 - (1 vote)

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Windows Server Tags:Windows 10, Windows 11

Post navigation

Previous Post: How to create Bitbucket Repository
Next Post: Query and display Windows information via WMI Explorer

Related Posts

  • hero windowsadmincenter
    Failed to create a scheduled task: Cannot perform the operation because the runspace pool is not in the open state Windows Server
  • RDP Certificate Issues
    Connecting to the RDP host: Fix the Certificate could not be verified back to the root certificate Mac
  • Microsoft BitLocker Administration and Monitoring
    How to deploy MBAM for BitLocker Administration Windows Server
  • 2022 1
    Install Windows Server 2022 on VirtualBox Network | Monitoring
  • MDT Workbench Crashes when opening WinPE tab Properties
    Fix MDT Workbench Crashes when opening WinPE tab Properties Windows
  • image 41
    INACCESSIBLE BOOT DEVICE: Fix Your PC ran into a problem and needs to restart Windows

More Related Articles

hero windowsadmincenter Failed to create a scheduled task: Cannot perform the operation because the runspace pool is not in the open state Windows Server
RDP Certificate Issues Connecting to the RDP host: Fix the Certificate could not be verified back to the root certificate Mac
Microsoft BitLocker Administration and Monitoring How to deploy MBAM for BitLocker Administration Windows Server
2022 1 Install Windows Server 2022 on VirtualBox Network | Monitoring
MDT Workbench Crashes when opening WinPE tab Properties Fix MDT Workbench Crashes when opening WinPE tab Properties Windows
image 41 INACCESSIBLE BOOT DEVICE: Fix Your PC ran into a problem and needs to restart Windows

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • ClamAV
    How to install and manage ClamAV and ClamTK on Ubuntu Linux Anti-Virus Solution
  • gfhj
    Debugging: How to debug a PowerShell script Windows
  • ycx
    How to use SysInternals Live Tools Windows Server
  • screenshot 2020 04 17 at 17.09.01
    How to configure a remote Windows Server to Support Ansible Windows Server
  • Azure Storage 1
    Azure CLI: How To Upload Batch Files to Azure Storage Account AWS/Azure/OpenShift
  • Microsoft Windows Windows 1
    How to specify a persistent default printer via the Windows Registry and PowerShell Windows
  • Auto Update Upgrade issues
    Fix Microsoft Office Showing “Upgrade Required” in AutoUpdate JIRA|Confluence|Apps
  • WindowsCoreSecurity
    How to enable Smart App Control on Windows 11 Security | Vulnerability Scans and Assessment

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,804 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

AWS Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.