The latest Windows Package Manager 1.29 preview introduces a source priority system that lets users control search ranking and automatically resolve duplicate package conflicts. Export commands now capture custom installer arguments, streamlining software migrations and automated deployments across different machines. Automation workflows gain cleaner redirected output, a progress suppression flag, and improved GitHub API authentication to prevent rate limit failures in CI/CD pipelines. Several backend fixes also patch path quoting errors, DSC schema bugs, and certificate timestamping issues that commonly break silent installations.

Windows Package Manager 1.29 Preview Adds Source Priority and Cleaner Export Features

The latest preview build of Windows Package Manager brings a few practical tweaks that actually matter for power users who manage software across multiple machines. This release focuses on better control over package sources, cleaner automation flags, and smarter handling of installer arguments during system migrations. Anyone running scripts or juggling custom app setups will find these updates worth testing before the stable branch catches up.

Windows Package Manager Export Now Remembers Custom Install Flags

Migrating software setups between computers has always been a manual headache when custom installation switches get lost along the way. The updated export command now captures override and custom arguments directly into the backup file. Running an import later reapplies those exact parameters without requiring anyone to rewrite batch scripts or remember which silent flags were used originally. This change saves time during system rebuilds and keeps deployment pipelines consistent across different hardware profiles.

Source Priority Changes How Results Get Ranked

The new source priority feature lets administrators assign a numerical value to each configured package repository. Higher numbers push those sources to the front of search results and automatically resolve conflicts when multiple feeds return overlapping packages. This means users no longer have to manually pick between identical entries from different catalogs. Sysadmins frequently waste entire mornings manually resolving duplicate package conflicts after importing third party repositories, which makes this priority ranking a necessary addition. The setting sits behind an experimental flag called sourcePriority, which stays disabled by default until Microsoft decides it is ready for broader testing. REST based feeds like the Microsoft Store integration also get a match criteria update that stops them from unfairly dominating search rankings just because they use a different backend protocol.

Automation Gets Cleaner Output and Better API Limits

Scripts that pipe package lists into files or variables finally stop getting truncated mid output. The updated list command calculates column widths based on the full result set instead of guessing at runtime. A new no progress flag also strips out all spinners and status bars, which keeps terminal logs clean for continuous integration workflows. The PowerShell module now reads GitHub authentication tokens from environment variables to bypass strict rate limits during automated builds. AI agent tools tied to the MCP server also gain upgrade specific parameters that let them scan for outdated software or force updates without triggering installation prompts on fresh packages. The MCP integration feels a bit premature since most AI assistants still struggle with basic package resolution, but it gives automation frameworks a necessary foothold for future development.

Bug Fixes and Signing Improvements Round Out The Build

Several underlying issues get patched in this preview release, including a fix for export commands failing when the destination path contains hidden file attributes. The DSC schema now correctly handles boolean defaults instead of spitting out broken string values that break configuration managers. Package signing tools also support optional timestamp servers to keep digital signatures valid after certificates expire, and file paths with spaces finally get properly quoted before reaching signtool or makeappx. These backend adjustments prevent silent failures during large scale deployments and keep automated workflows from breaking over minor path formatting errors.

Release Windows Package Manager 1.29.170-preview

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.

Release Windows Package Manager 1.29.170-preview · microsoft/winget-cli

Testing preview builds always carries a small risk of unexpected behavior, so keeping a system restore point handy makes sense before running the update command on production machines. The changes here lean toward practical workflow improvements rather than flashy new interfaces, which usually means Microsoft is actually listening to what administrators complain about during daily use. Keep an eye on the official repository for stable release notes when this preview matures into a general availability build.