Introduction
Upgrades applications on a device using winget. You can upgrade everything winget knows about at once, or target specific packages. Either way, you can exclude packages that shouldn't be touched.
Upgrade Winget Package
Open an automation and add a new action step.
Under App management, select Upgrade winget package.
Choose an Upgrade type (details below).
Add any package IDs to Excluded package(s) if there are apps that should be skipped.
Click Save.
ℹ️ NOTE: If Level's winget isn't installed on a device when this action runs, Level installs it automatically before proceeding.
Upgrade All Available Packages
Updates every winget-managed application on the device that has an available upgrade.
The Package(s) field is unused in this mode — leave it empty.
Use Excluded package(s) to skip specific apps. Enter package IDs separated by
Tabor a comma.
💡 TIP: Exclusions are useful for apps where you want to control version upgrades manually — for example, line-of-business software with compatibility requirements or version pinning.
Upgrade Specific Package(s)
Updates only the packages you specify.
Enter the package IDs you want to upgrade in the Package(s) field (required).
Optionally add IDs to Excluded package(s) to carve out exceptions.
ℹ️ NOTE: The Package(s) field is required when using Upgrade specific package(s). The action can't be saved without at least one ID in this mode.
Finding Package IDs
Winget uses a Publisher.AppName format. Find IDs at winstall.app or run winget list on a device to see installed packages and their IDs.
⚠️ WARNING: Package IDs are case-sensitive. A mistyped ID will cause the upgrade to fail silently for that package.
Conditions
Restrict when this action runs based on device attributes or the outcome of a previous action. Expand the Conditions section to add conditions.
See Action Conditions for the full reference on condition types, operators, and values.
Additional Options
Expand Additional options for settings including action name, failure behavior, output variables, and retries.
See Actions Overview for the full reference on additional options available on every action.
FAQ
What's the difference between this and Level's Updates feature? Level's Updates feature handles OS-level and Microsoft patches via Windows Update. This action handles winget-managed third-party applications. Use both to cover OS patches and app updates.
What happens if a package is already on the latest version? Winget skips it. The action completes without error.
Do I need to add an Install Winget step first? No. If Level's winget isn't on the device yet, this action installs it automatically before running.
Should I use "Upgrade all" or "Upgrade specific"? "Upgrade all" is convenient for general maintenance automations. "Upgrade specific" gives tighter control over which apps get updated and when — useful when some apps have version dependencies or testing requirements.
Who can configure this action? Any technician with permission to create or edit automations in the relevant group.