Windows Package Manager 1.29.280 RC Adds Manual Source Prioritization and Tighter Automation Controls
Windows Package Manager v1.29.280 hit the pre-release channel earlier today, shipping an experimental source priority system that finally lets you dictate how winget ranks results across configured repositories. Microsoft is asking developers and power users to test it before the stable push drops next month.
For years, the tool has shuffled search results in a way that feels more like a rolling dice than a deterministic list. The new experimental sourcePriority flag changes that. You can now assign numerical weights to your configured repositories, and higher numbers actually push those sources to the top. If only one high-priority source returns a clean match, winget stops bugging you with the dreaded "multiple packages were found" prompt. Keep in mind that this feature sits behind an experimental toggle and defaults to disabled, so nothing changes unless you explicitly turn it on.
It’s a rather practical update for anyone managing mixed deployment environments, though the experimental tag means you’ll want to tread carefully in production. Microsoft is trying to patch years of search-result chaos. The store feed used to hijack relevance scoring just by virtue of existing. Now it actually has to compete with community and local repositories.
Beyond the command line tweaks
The export and import commands got a quiet but highly necessary upgrade. winget export now saves your custom --override and --custom installer arguments straight into the output file. Importing it back on a fresh machine or in a deployment script reinstalls everything with those exact switches intact. If you’ve ever manually retried a silent installation after a fresh OS build, you know exactly why this matters. Necessary.
Piping winget output through automation finally gets some breathing room thanks to the new --no-progress flag. That command-line switch completely silences the spinning progress bars that tend to break log parsers. You can also sort winget list output now. Use --sort with fields like name, version, or source, and flip the direction with --ascending or --descending. The tool even remembers your preferred ordering in the user settings if you don’t feel like typing it every time.
Microsoft is pushing the WinGet MCP server harder for AI agent workflows. The new upgradeable and upgradeOnly parameters let automated systems filter for outdated packages or force update-only operations without guessing. Meanwhile, the PowerShell module now reads GH_TOKEN and GITHUB_TOKEN environment variables automatically. CI/CD runners won’t trip over GitHub’s rate limits as often, which saves a lot of head-scratching when deployments stall.
Under the hood and the nitty-gritty
Installer selection got a hard-coded hierarchy too. MSIX takes precedence, followed by MSI and Wix bundles, then Nullsoft or Inno installers, and finally portable executables. User preferences still override this, but the default stack is much more predictable. You can also tweak log file naming now via logging.fileNameStrategy. Switch to timestamps, GUIDs, or the new shortguid format if manifest names are clashing with your audit trails.
Redirected winget list output actually renders full columns instead of truncating mid-sentence. Spinner output gets stripped automatically when there’s no console attached, keeping plain text dumps clean. DSC v3 resources now correctly handle boolean defaults, honor installMode for silent installs, and quote file paths properly so spaces don’t break signtool.exe. There’s also a fix for a crash that would randomly kill the --disable-interactivity flag when the Resume experimental feature was running.
This is still a release candidate, so treat it like a beta. Head here to download the v1.29.280 binaries from the official Windows Package Manager repository below. File an issue if something breaks in your pipeline, and Microsoft will be tracking feedback before the stable v1.29 push.
Release Windows Package Manager 1.29.280
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.
Release Windows Package Manager 1.29.280 · microsoft/winget-cli
