Brief summary of issue:

PTB show latest updates to be none newer than the following:

• 4.19.1.ptb-2025-02-11-a859877f
• 4.19.1.ptb-2025-02-10-9d5112ba
• etc.

Steps to reproduce the issue:

1. Reproduction is getting harder with other PTB issues lingering like Windows PTBs installer broken - missing core files after installation #7687
2. Obtain an old PTB installer from before February 2025
3. Click the "update" button and compare the latest versions listed to the above
4. Obtain one of the more current PTB installers from Mudlet website (but not the most current)
5. Click the "update" button to review if the most current PTB update is promoted or not

Error output

Both step 3 and 5 should yield the same results, i.e. the most current PTB updates should be listet, but they are not.

Extra information, such as the Mudlet version, operating system and ideas for how to solve:

Additional input from @atari2600tim in Discord:

From 2025-06-26

We currently can not run the updates on Windows because of known errors extracting the files starting in January, probably need to switch to a different Squirrel fork or something that will extract the files properly. So forget actually updating for the purposes of rest of what I'm writing here.

With PTB 2024-12-15 64-bit, the check for updates shows it knows about an update to 2025-02-06-e416.

With PTB 2025-06-06 and 2025-04-07 it says that there is no update available.

So, I think we have a new problem (not in the update on client, but in the publishing to server step... but went unnoticed because of that), where the dblsqd thing that registers new builds on the server after building the PTB exe files is no longer updating that. Shortly after that last successful one, there is Windows 32 bit builds getting disabled. Maybe the registering of new builds for both 64 and 32 was part of that step without realizing.

From 2025-07-28

The publishing update script I expect the process built 64 and 32 bit and notified server of both in one step that got disabled when the 32 bit builds got disabled, likely fixable by rearranging some script part
Anyway, I got those bits and pieces of info and theories all from symptoms and not from tracing through code yet since learning about those parts will be slower for me having never messed with installer builder and whatnot.
Past installers if you want to see difference between dates:
They have expired from the download server by now after 14 days, but I have saved both the 32 and 64 bit versions of the [Mudlet] installer onto my OneDrive folder at https://1drv.ms/u/s!ArGNlRv79YEvgawMZCzTDSrFGiamzA?e=T0BcOQ