You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a release candidate of Windows Package Manager v1.29. If you find any bugs or problems, please help us out by filing an issue.
Note: This version is not fully localized yet. Localized strings will be included in a future build before stable release.
New in v1.29
New Feature: Source Priority
Note
Experimental under sourcePriority; defaulted to disabled.
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 server's 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."
Authenticated GitHub API requests in PowerShell module
The PowerShell module now automatically uses GH_TOKEN or GITHUB_TOKEN environment variables to authenticate GitHub API requests. This significantly increases the GitHub API rate limit, preventing failures in CI/CD pipelines. Use -Verbose to see which token is being used.
Default priority of installer types
Installer type selection no longer depends on the order defined on the manifest. Instead, preference is given in this order:
MSIX
MSI / Wix / Burn
Nullsoft / Inno / EXE
Portable
When a user configures installer type requirements or preferences, the order in which they are listed is now respected during installer selection.
Improved list output when redirected
winget list (and similar table commands) no longer truncates output when stdout is redirected to a file or variable — column widths are now computed from the full result set.
Spinner and progress bar output are suppressed when no console is attached, keeping redirected output clean.
Log file naming strategy
Added a user setting (logging.fileNameStrategy) for controlling the default naming strategy for installer log files. Supported values are manifest (default), timestamp, guid, and shortguid. Only applies to logs generated by installers if the installer itself supports the logging switch / parameter.
Setting
Description
manifest
Uses the name of the manifest and a timestamp. Has the same behavior as WinGet 1.28
timestamp
The log name is just a timestamp
guid
The log name is a GUID
shortguid
The log name is the first 8 characters of a GUID
Sortable list output
winget list now supports sorting results via --sort <field> (repeatable for multi-field sorting), --ascending/--descending direction flags, and a persistent output.sortOrder setting. Available sort fields: name, id, version, source, available, relevance. By default, results are sorted alphabetically by name when no query is present; use --sort relevance to preserve the previous source-determined ordering.
Bug Fixes
winget export now works when the destination path is a hidden file
Fixed the useLatest property in the DSC v3 Microsoft.WinGet/Package resource schema to emit a boolean default (false) instead of the incorrect string "false".
SignFile in WinGetSourceCreator now supports an optional RFC 3161 timestamp server via the new TimestampServer property on the Signature model. When set, signtool.exe is called with /tr <url> /td sha256, embedding a countersignature timestamp so that signed packages remain valid after the signing certificate expires.
File and directory paths passed to signtool.exe and makeappx.exe are now quoted, fixing failures when paths contain spaces.
DSC export now correctly exports WinGet Admin Settings
winget validate now performs case-insensitive comparison for file extensions where applicable
winget source reset now properly resets default sources instead of removing them
DSC v3 Microsoft.WinGet/Package resource now honors the installMode property to use silent or interactive installer switches as specified
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
This is a release candidate of Windows Package Manager v1.29. If you find any bugs or problems, please help us out by filing an issue.
Note: This version is not fully localized yet. Localized strings will be included in a future build before stable release.
New in v1.29
New Feature: Source Priority
Note
Experimental under
sourcePriority; defaulted to disabled.With this feature, one can assign a numerical priority to sources when added or later through the
source editcommand. 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:
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 fordisambiguation 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 thematch 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 exportnow captures the--overrideand--customarguments that were used when a package was originally installed and saves them into the export file. When subsequently runningwinget import, those values are automatically re-applied during installation —--overridereplaces all installer arguments and--customappends 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-progresscommand-line flag that disables all progress reporting (progress bars and spinners). This flag is universally available on all commands and takes precedence over thevisual.progressBarsetting. Useful for automation scenarios or when running WinGet in environments where progress output is undesirable.MCP
upgradesupportThe WinGet MCP server's existing tools have been extended with new parameters to support upgrade scenarios:
find-winget-packagesnow accepts anupgradeableparameter (default:false). When set totrue, it lists only installed packages that have available upgrades — equivalent towinget upgrade. Thequeryparameter 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-packagenow accepts anupgradeOnlyparameter (default:false). When set totrue, it only upgrades an already-installed package and returns a clear error if the package is not installed (pointing toinstall-winget-packagewithoutupgradeOnlyinstead). AI agents can use this to answer requests like "Update WinGetCreate" or, in combination withfind-winget-packageswithupgradeable=true, "Update all my apps."Authenticated GitHub API requests in PowerShell module
The PowerShell module now automatically uses
GH_TOKENorGITHUB_TOKENenvironment variables to authenticate GitHub API requests. This significantly increases the GitHub API rate limit, preventing failures in CI/CD pipelines. Use-Verboseto see which token is being used.Default priority of installer types
Installer type selection no longer depends on the order defined on the manifest. Instead, preference is given in this order:
When a user configures installer type requirements or preferences, the order in which they are listed is now respected during installer selection.
Improved
listoutput when redirectedwinget list(and similar table commands) no longer truncates output when stdout is redirected to a file or variable — column widths are now computed from the full result set.Log file naming strategy
Added a user setting (
logging.fileNameStrategy) for controlling the default naming strategy for installer log files. Supported values aremanifest(default),timestamp,guid, andshortguid. Only applies to logs generated by installers if the installer itself supports the logging switch / parameter.Sortable
listoutputwinget listnow supports sorting results via--sort <field>(repeatable for multi-field sorting),--ascending/--descendingdirection flags, and a persistentoutput.sortOrdersetting. Available sort fields:name,id,version,source,available,relevance. By default, results are sorted alphabetically by name when no query is present; use--sort relevanceto preserve the previous source-determined ordering.Bug Fixes
winget exportnow works when the destination path is a hidden fileuseLatestproperty in the DSC v3Microsoft.WinGet/Packageresource schema to emit a boolean default (false) instead of the incorrect string"false".SignFileinWinGetSourceCreatornow supports an optional RFC 3161 timestamp server via the newTimestampServerproperty on theSignaturemodel. When set,signtool.exeis called with/tr <url> /td sha256, embedding a countersignature timestamp so that signed packages remain valid after the signing certificate expires.signtool.exeandmakeappx.exeare now quoted, fixing failures when paths contain spaces.winget validatenow performs case-insensitive comparison for file extensions where applicablewinget source resetnow properly resets default sources instead of removing themMicrosoft.WinGet/Packageresource now honors theinstallModeproperty to use silent or interactive installer switches as specifiedWhat's Changed
downloadBehavioranddefaultDownloadDirectory#5296, Update README.md for adding PowerShell cmdlet samples #5921, winget-settings.schema.json #5108, Update Troubleshooting issue "Executing winget doesn't display help" #4372, Following dscv3 help link goes to Bing Home Page #5867) by @GrantMeStrength in docs: fix multiple documentation issues (#5296, #5921, #5108, #4372, #5867) #6110by @Madhusudhan-MSFT in Implement sort logic for winget list output #6191
configure export --allfor recent DSC changes by @JohnMcPMS in Updateconfigure export --allfor recent DSC changes #6222New Contributors
Full Changelog: v1.28.240...v1.29.240
This discussion was created from the release Windows Package Manager 1.29.240.
Beta Was this translation helpful? Give feedback.
All reactions