This is a preview build of WinGet for those interested in trying out upcoming features and fixes. While it has had some use and should be free of major issues, it may have bugs or usability problems. If you find any, please help us out by filing an issue.

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.

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.

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.

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

What's Changed

• Report skipped upgrades when install technology differs (upgrade --all) by @AMDphreak in #6096


• [AI Generated] Ensure correct DSC export of admin settings by @Trenly in #6109


• Update default for useLatest by @Trenly in #6114


• Add Update commands for MCP by @Trenly in #6117


• Preserve overrides with export and import by @Trenly in #6118


• Quote winget server path before calling CreateProcess by @yao-msft in #6122


• Update to spell check v26 by @Trenly in #6128


• Add issue types to issue templates by @denelon in #6139


• Improve MOTW error handling in download flow by @Trenly in #6127


• Allow exporting to hidden files by @Trenly in #5795


• Add thread globals for downloader thread by @Trenly in #6141


• Dynamically select drive for test by @Trenly in #6129


• Change how Truncation works by @Trenly in #6142


• Admin setting and group policy for configuration processor path argument by @JohnMcPMS in #6119


• Add comments to loc strings by @florelis in #6150


• Move XML ref ahead by @JohnMcPMS in #6154


• Add policy for notifying authors of Localization Restriction by @Trenly in #6156


• Dont log failures to get font title info by @dkbennett in #6163


• [ListCommand] Fix --source filter not restricting list output to specified source by @Madhusudhan-MSFT in #6159


• Improved manifest validations for MSI and Windows Feature names by @JohnMcPMS in #6170

New Contributors

• @AMDphreak made their first contribution in #6096

Full Changelog: v1.29.140-preview...v1.29.160-preview