Windows Package Manager 1.30.80-preview Adds Store Telemetry and Finishes Build Modernization
Microsoft dropped Windows Package Manager v1.30.80-preview on July 29, 2026. It is the third preview inside the v1.30 development cycle, and it arrives with a single headline addition: optional telemetry for Microsoft Store catalog installs that route through the winget CLI. The rest of the release is either engineering debt being paid off or regression patches that have been stable since the previous drop.
The real activity sits in PR #6352. When a command like winget install XPFFH613W8V6LV successfully pulls an app from the msstore package source, WinGet now emits a dedicated ETW event to the Microsoft-Windows-Store provider. The payload carries the Store product ID, the install caller, and a constant catalog name. Microsoft built the whole thing to respect your existing telemetry opt-out settings. It does not log executable paths, usernames, or command-line arguments.
The build pipeline gets cleaned up
For what it is worth, this closes an observability gap that has existed since WinGet gained Store catalog support. Internal teams can finally track how many installs actually route through the CLI versus the Store app itself, without entangling that data with the existing WinGet telemetry pipeline. Quiet drop. Definitely not user-facing, though the architectural choices here should make future debugging smoother if you ever dig through the logs.
The test suite got a full upgrade to NUnit v4. Developers swapped the old classic assertions for NUnit 4 constraint checks, cleaned up delegate-based overloads, and modernized DSCv3 settings tests to use built-in key constraints. CppWinRT coroutine handling got standardized at the same time. The team removed the injected /await flag and switched to /await:strict, which forces proper co_return usage and converts std::future calls to IAsync* types. It is the kind of plumbing work that never makes release notes, but it keeps the C++ codebase from drifting further from modern standards.
The two regression bugs that caused crashes with --disable-interactivity and broke elevation validation are still fixed. They landed in v1.30.50-preview and never came back. A dependabot update bumped js-yaml from 4.1.1 to 4.3.0 for the WinGetLogViewer tool. That update caps YAML merge processing to block denial-of-service attacks through deeply nested files, which is a reasonable security win for a log parser. There is also a new contributor on this one. @shmuelie landed their first pull request with the Store telemetry event, which suggests the open source pipeline is still pulling in outside help.
The v1.30 release notes originally said "Nothing yet" under New Features. So when this telemetry event surfaced a week later, it felt more like an incremental improvement than a headline release. That is fine for a preview build. Microsoft has moved to a three-preview sprint pattern for this milestone, which points to an accelerated push before the stable release ships. Keep in mind that this is a pre-release channel, so stability is not guaranteed even though the bug fixes have been holding steady for two previews.
Head here to grab the installer if you want to test the new telemetry flags locally. The next preview will likely refine what is already here.
