2 hours ago
Topic:
Github SPS Updater - Updates & Add apps
GianlucaAdministrator Posts: 1407
|
Dear ronen1n,
I think there is a misunderstanding here.
SyMenu and the plugin have different goals.
SyMenu updates are intentionally based on human validation and publication. An SPS becomes available to all users only after an editor decides to publish it. This design has several advantages: quality control, source verification, licensing checks, VirusTotal verification, package structure validation, and support for any download source, not only GitHub.
The plugin follows a different approach. Its goal is to detect and apply updates much faster by relying on automation.
Both approaches are valid, but they naturally produce different results. If the plugin chooses to update SPS definitions that belong to the SyMenu or NirSoft suites before the corresponding official definitions are published, temporary version mismatches are expected, and a loop of continuous updates and downgrades may occur until the SyMenu definitions match those generated by the plugin. In some cases, this may never happen.
How should those mismatches be handled? Not by SyMenu, because it has to follow its own logic and workflow. Not by the plugin either, because it has to follow its own logic and goals. IMO, the only way to solve this is to prevent the two logics from overlapping. And to prevent this kind of doubt, should I stop maintaining GitHub-based SPS files in the official suites because the plugin now exists? I don't think so. The plugin is still relatively new, not every user relies on it, and it still needs time to prove its robustness, reliability, and long term accuracy. Moreover, I still don't understand how a new GitHub SPS managed by the plugin should reach users for the first time. If it is distributed through the official suites, we are back to the overlap problem. If it is not distributed through the official suites, how does it initially reach the users? Well this is entirely obscure for me.
Custom suites are a different story because there is no official editor workflow behind them, which is why I see much more value in the plugin operating there.
What happens if you are not satisfied with the release pace of a SyMenu suite application? For example, for Thunderbird Portable I chose to follow the ESR releases rather than every available version. If Thunderbird Portable were available on GitHub, you could choose whether to manage it within its original suite or manage it through the plugin. The latter approach suggests placing it in a custom suite. This is how I would operate, but every user is free to work the way they prefer. If you want to suggest a workaround that enables a different scenario, you are free to do so.
Remember when I was talking to you about the architectural choices you took for the plugin? This is one of the friction points I had in mind when we previously discussed the plugin scope. The plugin can certainly choose different directions from what I suggested, but in that case these kinds of conflicts are expected and should probably be addressed at the plugin level rather than at the SyMenu level.
A big element of confusion comes from this sentence: ronen1n wrote:
you say it's simple to limit the plugin a lot to just update github apps and apps that not in symenu or not in nirsoft but also want new apps to get into symenu list so what's the point? Creating new SPS for the official suite, submit them, and enriching the SyMenu echosystem can be a nice thing the plugin can bring on the table.
But please don't confuse the role the plugin could have for an end-user and the role it can have for an editor.
If you are an editor and decides to go with the plugin to create/update your GitHub SPS for the official suite, please be my guest. You have to grant the same high level quality I expect from any editor and take responsability of your SPS. So you can use the plugin to get help with updates and use it to load the new/updated SPS to the cloud. But from there on, I don't care how you worked, your work has to meet the same quality standards as any other SPS published through SyMenu. The SyMenu community deserves the highest level of validation we can reasonably provide.
On the other hand you have the users. Why should an average user perceive the plugin as more useful than the standard automatic updates? In most cases, there is no compelling reason. The users want a trustable system that takes care of their program automatically. Most users are more interested in stability and reliability than in receiving updates a few days earlier. An advanced user may find it useful to add software that is not yet available in the suites, and the plugin enables exactly this kind of customization but why a normal user would have to mix the official suite with custom SPS? I don't see the reason.
There's a third scenario, where an editor want to use the plugin to create a custom, publicy-available, suite (sl23 is working on a suite like this). The editor probably can choose to use the plugin to create the SPS and suggest their users to use the plugin to get the updates. So they publish the starting definitions, the users download it, and from then on the plugin takes the lead.
And probably there's many other use case possible. But again, these are the kinds of design considerations that inevitably emerge once a tool starts being used in different ways by different users, and, above all, this kind of discussion is not suitable for this forum (I imagine nobody except the two of us read all this long post). To be fair, these are exactly the kinds of questions I hoped we would address during the design phase. They don't necessarily invalidate the plugin, but they become increasingly important as the plugin starts being adopted by a wider audience.
edited by Gianluca on 16/11/2026
|
|
|
9 hours ago
Topic:
Github SPS Updater - Updates & Add apps
ronen1nPosts: 32
|
ok but with that logic we need to block updates or creating new app in from the plugin that already in the symenu because if we create sps and update app faster than symenu or you're not the uploader for this app so you need to wait, the problem still exists it will show downgrades not sure what's wrong with it updating the symenu that the local files are more updated then the symenu update if symenu can't do it? maybe and we use the plugin just locally without updating symenu server for new apps that way the app will be in each user who wants it but not on symenu so it won't need to get fixed to not show downgrades you say it's simple to limit the plugin a lot to just update github apps and apps that not in symenu or not in nirsoft but also want new apps to get into symenu list so what's the point? even if its only github and i upload it to symenu list ill need this fix didnt see issues with this plugin fix yet give me better solution and show me real problem with what that is done now
|
|
|
11 hours ago
Topic:
Github SPS Updater - Updates & Add apps
GianlucaAdministrator Posts: 1407
|
I completely disagree. The solution is simple: the plugin must not touch the SPS managed by SyMenu and NirSoft. Those are already controlled, verified, and updated by the SyMenu engine itself.
Custom suites, on the other hand, are meant to be managed externally by the plugin. Letting the plugin operate freely inside the SyMenu and NirSoft folders will only cause issues.
I have to ask: why should the plugin manage SPS that are already being managed? What is the reason? I really can't see it.
|
|
|
20 hours ago
Topic:
Github SPS Updater - Updates & Add apps
ronen1nPosts: 32
|
The downgrade is a limit i have as extension that wants updates from symenu but still wants updates by my own fast rules I think the solution is to update the Audacity app faster on symenu but if you wait few seconds for the plugin to finish the update check it will probably remove this downgrade from symenu update manager Other solution is to implement some of those auto updates in symenu but maybe it will be when its more user friendly and bullet proof (Gian correct me if I'm wrong)
One more try to solve your problem, check this:
### v2.0.6 Changelog
* **Window & Focus:** Restored independent window mode (SyMenu is never locked); fixed SyMenu's menu unexpectedly popping up on close. * **4-Tier Icon Fallback:** Auto-fetches missing icons (EXE/MSI icon → archive `.ico`/`.png` like Ghidra/ZAP → GitHub avatar → manual Browse). * **MSI Support:** Added file inspection and icon extraction for `.msi` packages. * **Smarter Version Matching:** Auxiliary tags (like `models-v1`) no longer cause 404 errors; date/weekly builds (like ZAP's `w2026-11-11`) are parsed accurately. * **Stable Release Priority:** High-frequency weekly repos (e.g. ZAProxy) properly track stable releases via `/releases/latest` instead of auto-enabling pre-releases.
SyMenuGitHubUpdater-2.0.6 | F2H
|
|
|
22 hours ago
Topic:
Github SPS Updater - Updates & Add apps
sl23Posts: 328
|
ok, tested the new version, it keeps Symenu open while the plugin window is open, but the SyMenu does now hide once I close the plugin window, but I have to click SyMenu then away so it loses focus, or it remains onscreen. Getting there!
I also emailed Gian about this, I wasn't sure if it was a SyMenu or plugin issue, but I have now confirmed it is a plugin issue. When the GithubUpdater is NOT installed SyMenu shows its updates in the SPS Manager as normally would. But installing the plugin then gives gives updates NOT available to SyMenu's SPS Manager. For example, Audacity is happy without the plugin installed at v3.7.9. But install the plugin and I get offered v4.0.2. Which is great on the surface, but the SPS Manager and plugin are then fighting over who is right about the current version, so I then open the SPS Manager and find that now the update is telling that a "new" version is available, but it is a downgrade to v3.7.9!!!
There needs to be a central way to make update checking work, if the plugin is installed, then SyMenu itself should not do the checking, or something like that. But this conflict is confusing for users, that is a definite!
Keep going though, you're doing a great job, just a few wrinkles to sort out!
|
|
|
1 days ago
Topic:
Github SPS Updater - Updates & Add apps
ronen1nPosts: 32
|
- Changelog 2.0.5:
- Fixed SyMenu staying stuck on-screen: The plugin window now opens modally through SyMenu's native dialog handler instead of a separate thread, properly restoring focus on close.
- Added native MSI installer inspection: Analyzing an MSI package now automatically detects its installed executable path and extracts its application icon.
https://f2h.io/m2n8g0a5ei1g
I didn't see any problem with separate window handler and it was actually more comfortable so tell me if its better now or change it back
edited by ronen1n on 14/11/2026
|
|
|
2 days ago
Topic:
Github SPS Updater - Updates & Add apps
sl23Posts: 328
|
ok, downloaded, same thing, no problem with any other plugin than the github updater one.
|
|
|
3 days ago
Topic:
Github SPS Updater - Updates & Add apps
GianlucaAdministrator Posts: 1407
|
sl23 wrote:
I no longer have that plugin and that link seems to be dead? Says topic not found! Sorry, the link has been corrupted by the final dot. This is the right one: https://www.ugmfree.it/forum/messages.aspx?TopicID=85 Please try it so we can get some feedback.
|
|
|
3 days ago
Topic:
Github SPS Updater - Updates & Add apps
sl23Posts: 328
|
I tried the floating icon, same issue. Also, my Audio Suite plugin doesnt cause this issue when I select it. In fact no other menu selection does this, only that updater plugin. I no longer have that plugin and that link seems to be dead? Says topic not found!
|
|
|
3 days ago
Topic:
Github SPS Updater - Updates & Add apps
GianlucaAdministrator Posts: 1407
|
Thanks but I didn’t need your configuration details: I only wanted to know whether you had enabled any special options (context menu pin, show in taskbar, gestures, or anything else I’ve added over time). But it seems your setup is boring and standard, like mine 
To be clear, the expected behaviour is: - With the context menu open, select the GitHub SPS Updater plugin (by keyboard or mouse). - As soon as you click the item, the context menu hides and the plugin form appears.
If you see something different, please try this test: - If you haven’t already, download the SyMenu Open Folder plugin from here https://www.ugmfree.it/forum/messages.aspx?TopicID=85. - Launch it using exactly the same procedure described above. - Tell me whether the context menu still stays open, or whether it hides correctly this time.
|
|
|
3 days ago
Topic:
Github SPS Updater - Updates & Add apps
sl23Posts: 328
|
Gianluca wrote:
sl23 wrote:
Sorry, no idea what the issue is, but the focus thing is still not fixed for me. I open the plugin, close it and SyMenu remains onscreen. The only way to hide it is to open something from it, or click the notification icon.
Regarding this bug, the expected behaviour is that the menu closes itself as soon as the plugin's first window opens, not when it closes. BTW, it's a strange issue because I can't reproduce it. The menu behaves correctly on my system whether I open the plugin using the keyboard or the mouse. @sl23: - How is your menu configured? - How do you open it? - Where does it appear on screen? - Do you have any third party tools running that might interfere with window focus or window management? How is it configured? What do you mean, do you want my settings file? I open it via notification icon.
Menu appears bottom right on opening. Not as far as I know, no, there are no 3rd party tools that would interfere with this. I've sent you a gif of the issue Gian.
edited by sl23 on 12/11/2026
|
|
|
3 days ago
Topic:
Github SPS Updater - Updates & Add apps
ronen1nPosts: 32
|
Gianluca wrote:
A great addition for the next version would be an About entry in the Tools menu or at least an indication of the plugin version in the settings, as it is currently impossible to determine which version is running unless you inspect the dll file through the Windows file properties dialog. Another issue: I noticed that the plugin remembers the last applied filter, but the filter text box remains empty. As a result, I end up with a filtered grid without knowing which filter is currently active. As a related improvement, a visual indicator showing that one or more filters are active could also be useful.
please check the new changes:
GitHub SPS updater 2.0.4 New - The plugin version is shown in the window title and in Settings. - Tools > About shows the version, the plugin/settings/log locations, and a link to this topic. Changed - The search text is no longer restored when the window opens. View, "Installed only", sorting and window size are still remembered. - When a view or a search hides apps, the filter bar shows "Showing n of m · Clear filters"; one click shows everything again. https://f2h.io/feb8kdd5vsjx
edited by ronen1n on 12/11/2026
|
|
|
3 days ago
Topic:
Github SPS Updater - Updates & Add apps
GianlucaAdministrator Posts: 1407
|
A great addition for the next version would be an About entry in the Tools menu or at least an indication of the plugin version in the settings, as it is currently impossible to determine which version is running unless you inspect the dll file through the Windows file properties dialog. Another issue: I noticed that the plugin remembers the last applied filter, but the filter text box remains empty. As a result, I end up with a filtered grid without knowing which filter is currently active. As a related improvement, a visual indicator showing that one or more filters are active could also be useful.
|
|
|
3 days ago
Topic:
Github SPS Updater - Updates & Add apps
ronen1nPosts: 32
|
v2.0.3: Fixed PortableApps _online.paf.exe updates (such as Trellix Stinger Portable and Google Chrome Portable) by unpacking them silently in place via 7z.exe and installer.ini with checksum verification, instead of triggering PortableApps errors or interactive installer popups. https://f2h.io/ka6ovpmzfec5
|
|
|
3 days ago
Topic:
Github SPS Updater - Updates & Add apps
GianlucaAdministrator Posts: 1407
|
sl23 wrote:
Sorry, no idea what the issue is, but the focus thing is still not fixed for me. I open the plugin, close it and SyMenu remains onscreen. The only way to hide it is to open something from it, or click the notification icon.
Regarding this bug, the expected behaviour is that the menu closes itself as soon as the plugin's first window opens, not when it closes. BTW, it's a strange issue because I can't reproduce it. The menu behaves correctly on my system whether I open the plugin using the keyboard or the mouse. @sl23: - How is your menu configured? - How do you open it? - Where does it appear on screen? - Do you have any third party tools running that might interfere with window focus or window management?
|
|
|
4 days ago
Topic:
Github SPS Updater - Updates & Add apps
sl23Posts: 328
|
Sorry, no idea what the issue is, but the focus thing is still not fixed for me. I open the plugin, close it and SyMenu remains onscreen. The only way to hide it is to open something from it, or click the notification icon.
|
|
|
4 days ago
Topic:
Github SPS Updater - Updates & Add apps
ronen1nPosts: 32
|
What's New in v2.0.2
Fixes from Community Feedback- Fixed SyMenu Stay-On-Screen Focus Bug: Closing plugin windows now hands focus cleanly to the next window instead of re-activating SyMenu and keeping its menu stuck open on screen (applies to both GitHub SPS Updater and Portable Edge, 32-bit and 64-bit SyMenu).
- Fixed GitHub Publisher Resolution:
- Direct GitHub release-asset links (e.g. .../releases/download/...) now resolve through the GitHub repository path instead of falling back to github.com root (preventing false update alerts on subsequent checks).
- Existing definitions are only merged when matching the same repository and no longer overwrite the GitHub publisher name/website with third-party sites.
- Readable Vertical Main EXE Tooltip: Detected executables in the Add App dialog now list one per line instead of all on a single line.
- Improved Dark Theme Disabled Buttons: Disabled buttons now use muted grey text on a flatter dark background for clear readability.
- Remembered Window State & Grid Settings: Filters (Show, Installed only, search text), grid sort column/direction, window size/position, and details panel state now persist between sessions and across checks.
- Clearer New Suite Input (PortableApps): Updated label and tooltip to indicate you can pick an existing suite or type a new suite name.
- Encrypted UGMFree Credentials: Stored UGMFree passwords are now encrypted with Windows DPAPI per user (existing plain-text passwords migrate automatically on next Settings save).
Overlays & Updater Improvements- New Overlays Manager (Tools → Overlays Manager…): Central dashboard showing all configured/built-in overlays, their status (in place, waiting, needs re-apply, available (disabled)), a Check & Apply Overlays button, and Enable / Disable / Edit / Remove controls.
- Built-in Overlays Are Now Opt-In for New Users: Shipped built-in rules (Dark7zip for 7-Zip x64 and x64dbg Plugin Manager) start disabled (available (disabled)) so nothing modifies existing apps until you click Enable. Existing users who already had them applied stay enabled automatically.
- "Overlays only" Filter & Post-Update Hook: Filter the main grid to overlay-enabled apps and automatically re-apply overlays after updates finish.
- Simpler Overlay Setup: Added Browse Files… to pick assets straight from GitHub releases plus one-click presets in the overlay rule editor.
- JetBrains Standalone Support & Auto-Healing Icons: Added support for IntelliJ Community, PyCharm Community, and Gateway .windowsZip packages, plus automatic repair of generic placeholder icons in .sps files.
- Online PortableApps & Official Suite Handling: Online PortableApps (*_online.paf.exe) now stamp properly as exe with /S /D={0} so SyMenu updates them natively; official-suite apps stay hidden when official-suite patching is turned off.
edited by ronen1n on 11/11/2026
|
|
|
4 days ago
Topic:
Github SPS Updater - Updates & Add apps
sl23Posts: 328
|
Thanks for the really quick response!
Unfortunately, it still doesnt fix the "SyMenu stayed stuck on-screen and stopped auto-hiding on losing focus" issue. Portable Apps and Settings now display correctly. PortableApps into new suite, I would make this clearer, I thought you missed it until I read your Changelog in the OP. Perhaps a tooltip to say type a name for new suite sort of thing.
Otherwise, looks good to me! Great work. When I get time, I will do a thorough test of installing etc. Thanks so much for this!
|
|
|
5 days ago
Topic:
Github SPS Updater - Updates & Add apps
GianlucaAdministrator Posts: 1407
|
Hi ronen1n,
Some small issues from my side too:- When you release, you should remove your JSON files from the ZIP package because they are automatically recreated on first execution.
- One of the most important tooltips (the Main EXE tooltip shown after GitHub package resolution) should be formatted as a vertical list. At the moment, the detected executables are displayed on a single line, which makes them difficult to read.
- There seems to be something strange with the GitHub publisher website auto resolution.
Try with https://github.com/ahatem/QTranslate/releases/download/v1.5.0/QTranslate-1.5.0-windows-x64.zip. In my case the first time it resolved to majorgeeks.com (???). Second attempt it resolved correctly to github.com/ahatem/QTranslate. - Again regarding publisher resolution: in some cases (which I can't reproduce at the moment) it seems to resolve to github.com itself (web site root). This causes a false positive update detection during the next check.
- Disabled buttons are not easily readable when using the black theme. A gray font color or a different button background may help with the visibility and understanding of the disabled state.
- This is not an issue but a feature request: I would really appreciate it if the main form filters and grid sorting settings were persisted between sessions.
Overall, great progress.
|
|
|
5 days ago
Topic:
Github SPS Updater - Updates & Add apps
ronen1nPosts: 32
|
Thanks for the review Download updated to Version 2.0.1 with the fixes you wanted if you could check and report
|
|
|