PuTTY semi-bug store-version-unknown

This is a mirror. Follow this link to find the primary PuTTY web site.

Home | FAQ | Feedback | Licence | Updates | Mirrors | Keys | Links | Team
Download: Stable · Pre-release · Snapshot | Docs | Privacy | Changes | Wishlist

summary: PuTTY's Windows Store entry has "unknown version" according to Intune and Winget
class: semi-bug: This might or might not be a bug, depending on your precise definition of what a bug is.
difficulty: taxing: Needs external things we don't have (standards, users etc)
priority: high: This should be fixed in the next release.
present-in: 0.82

We've had a couple of reports that when automated installer tools try to install PuTTY from its entry in the Windows Store, they aren't able to determine its version number.

One of the tools in question is "Intune", presumably this one. Intune reports a GUI error message reading "The selected app does not have a valid latest package version."

We've had a similar problem reported from "winget", presumably this one. A CLI command like "winget search putty" finds our real Store entry (with id XPFNZKSKLBP7RJ), but reports a version field of "Unknown", in a display looking something like this (probably including other search hits too):

Name    Id              Version      Match     Source
------------------------------------------------------
PuTTY   XPFNZKSKLBP7RJ  Unknown                msstore

We'd like to fix this, but we don't know how. When we fill in the web form that submits a new version of PuTTY into the Store, we haven't found any field of the form where you enter a version number. So if the Store knows the version numbers of some packages but not PuTTY, we don't know what we're supposed to do to fix that.

Therefore, I've classified this as "semi-bug", because it's not clear whether there's anything we can do to fix it (the problem might also be in the Store itself, or in the tools that access it), and also as "taxing" because it's not just a question of us doing work – we also need information we don't have.

SGT's best guess, based on skimming the source code of "winget" on Github, is that it might have something to do with PuTTY's Store entry being based on the MSI installer system, instead of MSIX (which is more standard for Store entries). In "winget" there's a piece of code that extracts a version number from a metadata field in a MSIX file, but no corresponding code for MSI. And MSI integration with the Store is newer than MSIX. So one possibility (as far as we know) is that version number detection just doesn't work for MSI apps.

But if anybody knows better, or can tell us what we have to do to make PuTTY's Store entry have useful version metadata, we'd like to hear from you!


If you want to comment on this web site, see the Feedback page.
Audit trail for this semi-bug.
(last revision of this bug record was at 2025-01-16 12:54:30 +0000)