Hello everyone,

Today I wanted to discuss why we have the Winget Pre-Install component in our application deployments and how it resolves a critical issue with Winget.

The Winget Pre-Install is a fundamental prerequisite that prevents application issues when installing apps with Pckgr. Let’s dive into the reasons behind its integration and how it serves as the backbone of seamless installations with Pckgr.

The Critical Role of Winget Pre-Install

Imagine deploying an application on a freshly built Windows device only to find that it immediately fails. This is a real challenge faced when dealing with legacy versions of Winget on fresh Windows 10 and 11 installations. These versions, unfortunately, lack the capability to connect to the Microsoft CDN source, rendering them unable to install applications from the Winget repository.

The need for the Pre-Install surfaced when customers reported that brand new Windows 11 devices running 23H2 were unable to successfully install applications. When we manually checked the Winget version on one of these devices it was returned as “v1.2.10691”, after checking on GitHub we confirmed this version was released back in February 2022! See Windows Package manager 1.2.10271 · microsoft/winget-cli · Discussion #1895 (github.com)

To bridge this gap, we introduced the Winget Pre-Install—a preliminary check that ensures Winget is not just present but updated to its most current version. This step is crucial for a multitude of reasons:

• Compatibility Assurance: By ensuring that Winget is up to date, we align every deployment with the latest standards and technologies, paving the way for a smooth installation process that leverages Winget’s full potential.
• Prevention of Deployment Disruptions: The Winget Pre-Install acts as a safeguard, eliminating the risk of failed installations due to outdated Winget versions. This preemptive measure ensures that Autopilot and initial installations proceed without interruption. If the Winget Pre-Install detection fails, it means that Winget was unable to update or install and further investigation is required.
• Streamlining of the Deployment Process: For IT professionals, the importance of efficiency and reliability cannot be overstated. The Winget Pre-Install automates the Winget update process and can be completed during the Windows Autopilot Enrollment status phase.

Step-by-Step: How Winget Pre-Install Works

Let’s break down the Winget Pre-Install process to understand its impact better:

1. Initial Check: Upon initiating a deployment, the Winget Pre-Install evaluates the current Winget version on the target system.
2. Update Execution: If an outdated version is detected, the Pre-Install automatically updates Winget to the latest version, ensuring compatibility with the deployment process.
3. Seamless Deployment: With Winget updated, Pckgr proceeds with the application installation, leveraging Winget’s capabilities to ensure a smooth and efficient process.

Controlling the Winget Update

As Microsoft updates Winget, the Pckgr team proactively installs these new versions to test upcoming features and verify compatibility with Pckgr deployments. After completing tests, we update the Winget Pre-Install detection script. This enables Pckgr customers to deploy the latest update whenever they choose from with the Pckgr Portal.

In Closing

Thanks to the feedback and support of our customers, we were able to develop the Winget Pre-Install to fix application installs on a brand-new Windows device.

By ensuring Winget is always up to date, we not only facilitate smoother installations but also enhance the overall deployment experience for administrators and end-users alike.

We hope to see Microsoft introduce a built-in method for ensuring that Winget is updated during the Windows provisioning process or during Autopilot.

Until next time, happy deploying!