Windows Package Manager 1.30.50-preview drops, but save your upgrade button for later
Microsoft just pushed the first preview build for Windows Package Manager v1.30 to the winget-cli repository, and if you're running standard WinGet, you'll notice absolutely nothing has changed. The 1.30.50-preview release, published July 17, 2026, is explicitly labeled as a stabilization phase. There are no new features. Just bug fixes, infrastructure tweaks, and one critical crash patch for automation pipelines.
WinGet sits at a predictable point in its release cycle. The v1.29 stable line hit its latest point release (1.29.280) back on June 24, bringing Source Priority, MCP upgrade support, and default installer type handling. The v1.30 branch officially opened with this preview build, but as the release notes bluntly state: "Nothing yet." That is intentional. The team is using this preview window to burn down regression tickets and validate build tooling before committing to the next feature set.
Who Should Actually Upgrade
The only reason to care right now is a high-severity fix that breaks CI/CD workflows. If you run winget install --disable-interactivity alongside the experimental Resume feature, older preview builds would throw a 0x8000ffff (E_UNEXPECTED) crash. The root cause is straightforward. Checkpoint logic saves command-line arguments, but the code lacked a switch case for Execution::Args::Type::DisableInteractivity. Pull request #6302 patches that gap. Automation engineers relying on non-interactive installs will finally get checkpoint validation without the segfault.
The rest of the 17 commits cover medium-severity validation bugs and build system compatibility. A case-sensitive boolean conversion bug that broke elevated processes reading alias files got fixed in PR #6307. The build pipeline also gets a patch for Visual Studio 2026 18.5.3's cpprest SDK, alongside a CleanVcpkg MSBuild target so Clean Solution actually wipes local artifacts. The team also touched line ending normalization across the repo, though they quickly undid the changes on external signed PowerShell modules after the patches broke signature validation.
Keep in mind that this is a preview build with a 1,797-file touch spread across eight contributors. For the vast majority of users, sticking with stable WinGet 1.29.280 is still the right call. Preview releases are built for testers and integration pipelines, not production deployments. If your workflows don't use --disable-interactivity with Resume, you are just introducing unnecessary variables.
Grabbing the Build
The v1.30 line will stay feature-light until the stabilization window closes. Future previews will gradually introduce new capabilities and experimental flags. If you want to test this build anyway, you will need to point your source configuration at the preview channel manually.
Head to the GitHub releases page to grab the release, or update your WinGet source to pull the preview feed. The full commit diff and PR list are linked on the repository's release page.
