I'd like to suggest something a bit different - to keep updating latest apps version to winget db. Many people use winget and install/updates apps through it. It's very convinient as it allows for non-interactive installation and updates. I've done it a long time ago for Nexus and Xtreme, but it was 25.7 version. Now users can't install nor upgrade it because installation zip file leads to the same URI, hance showing "Installer hash does not match" error:

Keeping apps up-to-date in winget db gives the impression of greater attention to the user experience by the devs, and it's extremely simple to do.

In case of UI being outdated, this is a bit ridiculous thing to say IMO, as preferences window looks very good and I wouldn't change anything about it, but if I can be extremely picky about UI, then I'd pick context menus. I've tried to make them myself to match Windows 10 and 11 looks, but it was too overwhelming for me, so I really look forward for full theming guide.

A long time ago, eh? What planet are you on? 25.7 was less than 3 months ago.

Got any evidence for 'many people using winget...'? The majority of ordinary Windows users likely have never even heard of winget, I shouldn't be surprised.

Nexus Ultimate, let alone Nexus free, does not allow for menu theming, incidentally.

Many does not mean majority, but still a lot of people who are more technical/it professionals are using winget and are praising it for making apps management much more convenient. It doesn't need to be used by majority of people for it to be a good idea, especially if it's so easy to do. For developers of an application of such caliber and long-standing presence, this decision should be a no-brainer.

Of course 'many' does not mean or imply a majority, that's just stating the obvious! In the context however, it would indicate a significant number. And the number of more technically proficient people and IT people who, in the first place, use Winstep apps is not likely to be a significant number. Hence, winget is not really of great interest and would rather occupy a lot of time for relatively little return for Winstep software.

This latter point can be seen in the context of a lot of apps. I have, over time, downloaded a fair number of utils and stuff like web browsers with winget, only to find that they were past their best before date!

I've split the topic because I've read about Winget before and this exact issue whenever a new version is released, so I want to know more.

This said, I am not familiar with it at all, so I will have to read more about it before I can chime on this.

Ok, so I never submitted Winstep applications to Winget. This means someone else has been doing it for me (apparently a community submission by @akamienski who issued multiple update requests this year?).

Classic winget gotcha: the URL in the manifest must point to an immutable file whose SHA-256 never changes. If nexus.zip is a rolling file, every new release will break the old manifest’s hash check (which is what is happening).

I'm still not sure how version control works on Winget, but instead of submitting a link to zip files that get changed with every update (e.g. http://www.winstep/nexus.zip), whomever is entering this submissions should point to the old version repository instead:

https://winstep.net/releases.asp

So, rather than submitting a manifest that points to

http://www.winstep/nexus.zip

they should point it to

https://winstep.net/versions/v25.9/nexus.zip

The former is a rolling file but the latter remains immutable. Likewise for Ultimate and Xtreme.

Sounds complicated, and I have to confess it doesn't make much sense to me. Same file name but just a different path? Weird.

But then, that's winget - weird (wannabe) copy of the Linux cli 'apt get' (Ubuntu) util.

Anyway, probably explains why so many apps only have an old version.

Yep it was me.



That's how winget knows that the file (hash) was changed, and it assumes that either it's a different version or it may include something, that may be a security risk, hence doesn't allow to download it. That's why it's not recommended to update the file in the same path with different version if devs decide to use winget.



Thanks for letting me know, will keep that in mind for future requests. Winget does not have version control (besides hash check), it's on devs responsibility to submit new app version through their request form on winget-pkgs GitHub, which takes a minute to fill.