Upgrading a Winget Application to the Private Repository
As of May 2025, Pckgr is transitioning away from the Winget Repository for application hosting, granting all users access to applications hosted in our Premium Private Repository.
If you joined Pckgr prior to May 2025, you can upgrade your applications from the Winget version to the Private Repository version, as Pckgr has transitioned to a fully Private Repository library. Pckgr will cease support for Winget-hosted related issues as of 2026, so upgrading to the Private Repository versions of all applications is best practice.
This guide explains how to upgrade applications to Pckgr’s Private Repository. You can upgrade both deployed applications and those awaiting deployment, but the behavior differs depending on the application’s status.
As the Private Repository does not rely on Winget for functionality, once all deployed applications are from Pckgr's Private Repository, the Winget Pre-install application will no longer be required on devices and can be removed from Pckgr and Intune.
Key Differences in Upgrading
Application Status
Behavior During Upgrade
Deployed Applications
The new private version is automatically redeployed to Intune. The old deployment is removed, and all group assignments are copied over.
Awaiting Deployment Applications
The application is upgraded to the private version, but it will remain “Awaiting Deployment.” Manual deployment is still required.
Steps to Upgrade an Application to the Private Repository
1. Identify the Application for Upgrade
Navigate to the App Library in the Pckgr Dashboard.
Select the application you want to upgrade (app must be available in the Private Repository).
2. Initiate the Upgrade
Click on the Upgrade button next to the application.
A pop-up will appear prompting you to select a version from the Private Repository.
Choose the desired version from the available options (this will vary between applications).
Example: In the images above, the user selected TeamViewer (x64 MSI).
3. Confirm Upgrade
After selecting the desired version, select Confirm.
4. Configure the Deployment (Awaiting Deployment Status Only)
For upgraded applications, you can configure the following options before deployment:
Custom Install String (Optional)
Update Only: Deploy updates only if the application is already installed.
Remove Version from Display Name
Auto Update: Enable to keep the app updated automatically.
Delay Updates: Specify a delay (in days) for updates to roll out.
Advanced Installer: Add advanced install options (e.g., defer updates or close apps).
5. Deployment Behavior
Deployed Applications:
The new private version replaces the existing deployment.
Pckgr automatically removes the old version from Intune.
All previous assignments (group deployments) are copied over seamlessly.
Awaiting Deployment Applications:
The app is upgraded to the Private Repository, but it remains Awaiting Deployment.
You will still need to click Deploy to Intune manually.
What to do if there is no Upgrade option
There are two scenarios that could result in there being no option for upgrading:
No 'Upgrade button' available:
This means there is currently no Private Repository version of this application available. The reason may be due to discontinuation of this application from the vendor, or security risks. Feel free to reach out to our team via the Support channels on your Dashboard if you require clarification on the upgrade status of an application.
No application available in the Upgrade drop-down selector:
There can be a slight delay between the two libraries in terms of application updates. When an application has been updated in one library, there may be a short period of time before that same application has been updated to the same version in the second library. This will cause there to be no options for selecting an application to upgrade to, due to the temporary mismatch between version numbers. This will rectify with time, we advise you wait an hour and try again - your application options should become available.
Users can always simply remove their Winget version from Pckgr and Intune using the delete function, and deploy the Private version of the application from the library. This will achieve the same result as the Upgrade button.
Common questions
Do I need to keep the Winget Pre-install application in my library and tenant?
No. Once all of your applications have been upgraded or moved to their Private version, there is no longer a need for Winget Pre-install, as the Private versions have no dependencies. It is safe for you to remove it.
Why do some of my tenants have Winget Pre-install and others do not?
Since mid-2025, any new tenant that is onboarded with Pckgr, only has access to our Private Repository applications, as Pckgr moves to this Enterprise Standard of application management, and therefore there is no need for Winget Pre-install. Tenants onboarded prior to mid-2025 would automatically deploy Winget Pre-install as a dependency for the Winget apps, and therefore this application will be present until it is removed by the user. Once all Winget applications have been upgraded to their Private version, Winget Pre-install can be removed.
Why can't I add Winget Pre-install to my library for deployment?
This application is no longer required for the functioning of applications managed by Pckgr.
Last updated