A couple suggestions for improvements

[chjohans]

I'm a long time SUMo user, and I just "Migrated" to UCheck and paid for a premium license to support the development.

Some things I noticed immediately, that in my opinion could be improved:

1) The Dashboard showed 4 pending updates. I went to the updates tab and updated *one* of the programs. When I go back to the Dashboard the updated program is not reflected, it still shows that 4 updates are available. A new scan is a very slow method of updating that number, it would be much better if this was done as (automatically - like 4 minus 1) as soon as the update was installed.

2) I did a scan and then figured that I had to restart UCheck with administrator privileges to do a bulk update. But when I restarted it "forgot" the last scan. Again, running a new scan is time-consuming and should be totally unnecessary, it would be better if you could preserve the last scan result upon restart with administrator privileges. Just like SUMo used to do, it would *always* load the last scan result when it was started, but run a new scan if configured to do so (see below).

3) Please include an option to run a scan automatically when UCheck is started. Now we either have to do it manually, or wait for the scheduled scan (if any) to do it for us. This should *not* happen if UCheck is restarted in "administrator mode" (see above).

Thanks for considering these enhancements!

[chjohans]

Under 1), the same thing should apply if I do an "Exclude Software" for one of the available updates. The counter (available updates) should reflect that, which it does not in the current version. This is, actually, pretty simple.

[chjohans]

Any chance that this will get some attention?

Yes, no, maybe?

[Curson]

Hi chjohans,

1) and 2) will not be considered.
3) was implemented in latest beta release.

Regards.

[chjohans]

Thanks for 1 of 3.   Can beta releases be downloaded somewhere?

I still think the other two suggestions make sense, SUMo and a few other "software updater" programs I've used work that way so it's not something I made up.

If UCheck used a few seconds to run a scan none of those would have been important, but it does not and probably never will, so it becomes a real nuisance to have to re-run scans when you shouldn't have to. Especially for a tool I use daily.

But I hear you.

[Curson]

Hi chjohans,

I will ask Tigzy about it again.

Regards.

[TheQuestionmark]

I have also interest to use and test Beta Versions.

[Curson]

Hi TheQuestionmark,

Here is the latest beta release :
https://download.adlice.com/UCheck/Beta/UCheck64.exe

Regards.

[TheQuestionmark]

Thanks, that's great. I want to suggest a Download Location for Betas and an Option to use Beta-Updates.

I want also say, that it is great, that you maintain and publish the changelogs for releases. Perhaps you can extend this also for Betas? So it's easier to see, what was changed and we can have a special eye on it to report issues.

https://www.adlice.com/docs/ucheck/release-notes/changelog/

[dking02]

UCheck beta testing is currently focused on rapidly adding the ability to identify SW updates from version info supplied by the UCheck community (i.e., users) and to enable monitoring of updates to portable software, both of which were available in the KC Softwares SUMo product which went EOL (end-of-life) at the end of October. The following existing thread on Wilder's Security Forums was repurposed for beta test discussions beginning at post #19, 14 Sep 2023 on page 1 of the thread and has rapidly grown to over 1100 posts and over 45 pages over the past two months.

UCheck - Update your software in 2 clicks (Wilder's Security Forums)
https://www.wilderssecurity.com/threads/ucheck-update-your-software-in-2-clicks.404593/page-47

The announcement for the latest beta (v5.0.6.0-BETA, 23 Nov 2023) was provided by Tigzy in post #1149 on page 46 of this thread at the following link:
https://www.wilderssecurity.com/threads/ucheck-update-your-software-in-2-clicks.404593/page-46#post-3173477

You need to follow the thread to keep up with announcements of new betas and changes in content. There is no formal changelog for betas and since the beta version number is reused, a later beta can only be readily distinguished from a prior version by the date of the digital signature in the portable .exe that was downloaded.

[chjohans]

Back to what this thread was about, thanks for 1) but please again consider both 2) and 3).

In my opinion, it's never good when the main developer also decides or has the last say when it comes to functionality. He or she "has the code in his/her head" and decisions will often be based on what is easy or not to implement. Been there, done that, so speaking from experience here. Not saying that's the case here, just saying!

[Curson]

Hi everyone,

Sorry for the late reply.

chjohans, could you please add your suggestion to https://github.com/AdliceSoftware/UCheck/issues ?
It will be easier for us to track features requests this way.

dking02, I hope to use our GitHub repositiory to accululate and consolide changes in UCheck.

Regards.