Windows Package Manager 1.29.290$$$$$$New in v1.29$$$New Feature: Source Priority$$$With this feature; one can assign a numerical priority to sources when added or later through the source edit$$$command. Sources with higher priority are sorted first in the list of sources; which results in them getting put first$$$in the results if other things are equal.$$$$$$Tip$$$$$$Search result ordering in winget is currently based on these values in this order:$$$$$$Match quality (how well a valid field matches the search request)$$$Match field (which field was matched against the search request)$$$Source order (was always relevant; but with priority you can more easily affect this)$$$Beyond the ability to slightly affect the result ordering; commands that primarily target available packages$$$(largely install) will now prefer to use a single result from a source with higher priority rather than prompting for$$$disambiguation from the user. Said another way; if multiple sources return results but only one of those sources has$$$the highest priority value (and it returned only one result) then that package will be used rather than giving a$$$multiple packages were found error. This has been applied to both winget CLI and PowerShell module commands.$$$$$$REST result match criteria update$$$Along with the source priority change; the results from REST sources (like msstore) now attempt to correctly set the$$$match criteria that factor into the result ordering. This will prevent them from being sorted to the top automatically.$$$$$$Minor Features$$$Preserve installer arguments across export and import$$$winget export now captures the --override and --custom arguments that were used when a package was originally installed and saves them into the export file. When subsequently running winget import; those values are automatically re-applied during installation — --override replaces all installer arguments and --custom appends extra switches — so packages can be reinstalled with the same customizations without any manual intervention. Both fields are optional and independent of each other; packages without stored installer arguments are unaffected.$$$$$$--no-progress flag$$$Added a new --no-progress command-line flag that disables all progress reporting (progress bars and spinners). This flag is universally available on all commands and takes precedence over the visual.progressBar setting. Useful for automation scenarios or when running WinGet in environments where progress output is undesirable.$$$$$$MCP upgrade support$$$The WinGet MCP servers existing tools have been extended with new parameters to support upgrade scenarios:$$$$$$find-winget-packages now accepts an upgradeable parameter (default: false). When set to true; it lists only installed packages that have available upgrades — equivalent to winget upgrade. The query parameter becomes optional in this mode; allowing it to filter results or be omitted to list all upgradeable packages. AI agents can use this to answer requests like What apps can I update with WinGet?$$$install-winget-package now accepts an upgradeOnly parameter (default: false). When set to true; it only upgrades an already-installed package and returns a clear error if the package is not installed (pointing to install-winget-package without upgradeOnly instead). AI agents can use this to answer requests like Update WinGetCreate or; in combination with find-winget-packages with upgradeable=true; Update all my apps.$$$$$$For more refer -https://github.com/microsoft/winget-cli/releases/tag/v1.29.290