Skip to content

Install Windows Package Manager (winget) using Intune

Microsoft released a preview of the Windows Package Manager. I’m not going into detail about the product itself, because there are a lot of (better) alternatives for this already in the market. Today, we focus on how to get this tool installed on your endpoints, so you can use it for your software distribution. In this approach I use the APPX package. Normally I would use the Business Store for this, that version does not (yet) contain the winget feature.

For this setup, we need a couple of things:

Let’s start with de dependency files. These are not easy to find. Until I stumbled upon this post. You can download the files separately using this website:

Search for the packages selecting PackageFamilyName as the search type. Look for both Microsoft.VCLibs.140.00.UWPDesktop_8wekyb3d8bbwe and Microsoft.VCLibs.140.00_8wekyb3d8bbwe to download the files.

You’ll end up with a bunch of APPX files. We need these files in the next steps.

Install the LOB application

Launch the Microsoft Endpoint Manager admin center and go to Apps->All Apps and create a new app. Pick the Line of Business app.

Next, select the Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.appxbundle that you downloaded earlier. Browse for the dependency files, so there are added to the installation.

Follow the wizard to assign the application to your users or devices.

You can monitor the installation using the device install status page

You may need to install the Desktop Bridge VC++ v14 Redistributable Package. This should only be necessary on older builds of Windows if you get an error about missing framework packages.

Get started with winget

Now the tool is installed on your endpoint you can install packages using PowerShell or command line. To show that it’s working I installed VLC player on my demo machine.

To learn more about this new tool, check the following URL’s:

1 thought on “Install Windows Package Manager (winget) using Intune”

Leave a Reply

Your email address will not be published. Required fields are marked *