UCheck - Update your software in 2 clicks

Could you send me a PM ? I'll send you an upload link for DMP file.

 

No black friday for Adlice Software ?

 

Sorry, probably not. I'm deep in the code and don't really have time for marketing...
Maybe we'll do an offline promotion later, when everything will be working Ok.

 

Hi Tigzy,

Notepad++ 8.6 update wasn't detected (I am using the portable version, but the shortcut is pinned in the taskbar. I am not sure if Ucheck scan the shortcuts like SUMo did).
CCleaner 6.18.10838 Portable update was missed as well.
Also, FreeFileSync 13.2 (installed not portable) was missed too.
Didn't notice other issues.
Best regards!

 

I think someone said above this version was reverted by CCleaner team.

It should be detected ? https://twitter.com/UCheckBot/status/1727802981020467367

 

I've refreshed the BETA version (link above) to fix the issue with uTorrent exclusions. Anyone that had the issue please let me know

 

I don't know, but the links to 6.18 are still working, and they are downloading 10838 and not 10824.

https://download.ccleaner.com/ccsetup618.exe
https://download.ccleaner.com/portable/ccsetup618.zip

As for Notepad++, I don't know why it wasn't detected on my PC then. I was using 8.5.8 and version 8.6 wasn't detected at all.

 

Hi @Tigzy , @B-boy/StyLe/ :

The buggy CCleaner v6.18.10824 (rel. 15-Nov-2023) was pulled but a new v6.18.10838 (rel. 23-Nov-2023) was posted yesterday at https://www.ccleaner.com/ccleaner/builds. Release notes are available at https://www.ccleaner.com/ccleaner/release-notes.

I unzipped a copy of the new CCleaner Free Portable v6.18.10838 (ccsetup618.zip) on my removable USB stick inside E:\Portable\CCleaner 6_18 and confirmed that the latest UCheck Portable BETA v5.0.6.0 (offered 23-Nov-2023 in post # 1149) detects the 32-bit and 64-bit CCleaner Portable executables as long I have added the path E:\Portable to History & Settings | Custom Locations in my UCheck settings.



The new CCleaner Free Portable v6.18.10838 comes bundled with two new executables named wa_3rd_party_host_32.exe and wa_3rd_party_host_64.exe (program name OESIS V4 SDK). I haven't investigated yet but early feedback in the TheOwner's 23-Nov-2023 thread What is wa_3rd_party_host_64.exe in CCleaner folder? suggests these new executables might be associated with the "improved" Software Updater mentioned in the release notes.

Before users update to the latest CCleaner Portable v6.18.10838 I suggest they read APMichael's 24-Nov-2023 CCleaner v6.18 Portable crashes immediately , especially if they plan to unzip CCleaner Portable on a clean Windows installation. I'm going to monitor that thread for a few days and keep using the previous CCleaner Free Portable v6.17.10746 for now until I'm sure there aren't any serious bugs still lurking in v6.18.10838.
------------
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3693 * Firefox v120.0.0 * Microsoft Defender v4.18.23100.2009-1.1.23100.2009 * Malwarebytes Premium v4.6.6.294-1.0.2189 * Macrium Reflect Free v8.0.7690 * UCheck Free Portable BETA v5.0.5.0 (17-Nov-2023) * QuickInstaller Preview v0.2.8728.19402 * CCleaner Free Portable v6.17.10746

 

Hi @lmacri,

I am using the latest stable version of UCheck 5.0.5.0 and not the beta, so I can't speak for it, but the stable one definitely missed the update for me.
The filepath is as follows - E:\Downloads\CCleaner 6.18.10838 Portable, but I will check the settings you suggested (regarding the Custom Locations).

As for bugs, I didn't notice any bugs or crashes so far on Win 10 22H2. I always migrate my ccleaner.ini in the new unzipped folder and block the access to the internet in the firewall.

All the best!

 

If it's the BETA available in post #1149, I redownloaded, copied to my UCheck folder and still getting utorrent every time...

 

Observations 5.0.6.0 - beta2.

Supported:
Waterfox identified on other version number then they use on their site/release scheme G6.0.6 v.s. 115.4.1


Community:
Office 16.0.17116.20002 is an insider dev release for MS365


Python 3.13 is still alpha stage according to documentation.


NVIDIA Studio version is latest 546.01, Game ready is 546.17, this will probably be hard to differentiate though.

 

Hi Tigzy,

Only to let you know that some of the game launchers like Uplay, Epic Games Launcher, Steam, Battle.net and Rockstar Games Launcher updates wasn't detected but they auto-updated.

Best regards.

 

I am using PowerShell below as an example of one apparent problem with how UCheck is identifying some updates to community programs. While UCheck works well to identify updates to compatible programs, its current performace with respect to community programs leaves something to be desired.

I (and others) have been receiving erroneous notifications from UCheck to update to PowerShell 7.4.101.0 since late Oct, although it was a Preview (beta) channel release and was not one of the two Stable channel releases during that period, 7.3.9.500, 26 Oct 2023 or its successor 7.4.0.500, 16 Nov 2023.

On 14 Nov 2023, Curson supplied me with the following distribution of PowerShell versions from the UCheck DB to compare with data I had captured from the SUMo DB just before it closed down. (UCheck does not currently provide a capability for users to query its DB like SUMo did.)

5.7.0.18831 - 1800 Hits
7.4.101.0 - 423 Hits
7.4.0.101 - 335 Hits

The Stable channel release of PowerShell 7 on 14 Nov 2023 was 7.3.9.500, 26 Oct 2023, which I (and presumably most PowerShell 7 users) had installed on their machines. However, that version is not even in the UCheck data supplied. The 7.4.0.101 that is listed is a release candidate 7.4.0-rc.1, 24 Oct 2023 from the PowerShell 7 Preview channel and I assume that 7.4.101.0 is also the same release with the version numbers in different order. The 5.7.0.18831 version number corresponds to Azure PowerShell release of April 2015 (?). On 16 Nov 2023, when the PowerShell 7 Stable channel moved to the new 7.4.0.500 release, which is displayed as version 7.4.0.0. I installed that version but continued to get notifications to update to 7.4.101.0, although it was the Preview release candidate (rc.1) for 7.4.0.500.

No documentation of the algorithms used by UCheck to identify updates is available and there has been little discussion of this fundamental topic on this forum. However, it would appear that:

(1) UCheck is NOT maintaining a distribution of the versions of the program reported by users like SUMo did since the latest stable channel release which most users would be expected to be on is not in the above data. (I don't know what "hit" means in the data supplied - users? The provided counts seem implausible for count of users on these versions. The version numbers appear to be for prospective updates rather than actual versions in use.)

(2) I assume that UCheck identifies a new release as an update to the Stable channel when its count crosses an update threshold (5% of users?). However, the algorithm appears to ignore the likelihood that most users will not want to update to that new release if it is a beta and will remain on the current and older stable version. UCheck needs to be able to quickly retract such updates (preferably automatically) if the majority of users do not move to the "update" and needs to maintain cognizance of the distribution of versions among users, particularly the count of the latest stable version, not just prospective updates.

(3) If a beta version exceeds the update threshold and has a higher version number than other versions, it appears to be able to capture the "Latest" version indefinitely until a version with a numerically higher version number is eventually released. This would explain the repeated false positives for the same update that I am seeing for some community programs like PowerShell.

See the following references for background:

UCheck Forum post 3836, False Detection of Updates to PowerShell
https://forum.adlice.com/index.php?topic=3836.0
Post #763, page 31 of this thread
https://www.wilderssecurity.com/thr...tware-in-2-clicks.404593/page-31#post-3170002

 

Hi @RonnyT :

I am currently using the latest UCheck Free Portable BETA v5.0.6.0 offered 23-Nov-2023 in post # 1149 which I run from a removable USB stick with Administrator rights.

I use a retail edition of Microsoft Office Home and Business 2019 Click-to-Run (Current Channel) and noticed the same problem where UCheck would incorrectly recommend an update to a Preview build (see the Preview Current Channel release history for Insider beta testers <here>) even though I was using the latest stable release. For example, this image was captured 25-Nov-2023 when I was using the (then current) stable Version 2310 / Build 16924.20150 (rel. 14-Nov-2023) but UCheck was incorrectly recommending an update to Preview Version 2311 / Build 17029.20038 (rel. to Insiders on 20-Nov-2023).



As of today the release history <here> for my Microsoft Office Home and Business 2019 C2R shows a new stable Version 2311 / Build 17029.20068 (rel. 29-Nov-2023) was released yesterday. I have not received this latest update yet and am still on Version 2310 / Build 16924.20150 (rel. 14-Nov-2023), but when I ran UCheck today to see if it would recommend stable Version 2311 / Build 17029.20068 I discovered that my MS Office C2R is no longer classified as a "Community" app and is now "Unsupported". I don't know if this is a permanent change to resolve the detection of Insider Preview builds for MS Office C2R or just a temporary change while Tigzy is tweaking the UCheck code.


------------
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3693 * Firefox v120.0.0 * Microsoft Defender v4.18.23100.2009-1.1.23100.2009 * Malwarebytes Premium v4.6.6.294-1.0.2189 * Macrium Reflect Free v8.0.7690 * UCheck Free Portable BETA v5.0.6.0 (23-Nov-2023) * QuickInstaller Preview v0.2.8732.28005 * Microsoft Office Home and Business 2019 Version 2310 / Build 16924.20150 C2R

 

https://i.imgur.com/r1YvEyg.jpg

The same problem exists with Microsoft Project and Microsoft Visio, both Microsoft 365 tools.

And with Microsoft Teams it doesn't get it right with the latest stable version.

All the best

 

I contributed to a year license, hopefully to improve.
I see so many of my programs not detected.
Now I have to use Quick Installer also, both are pretty sad compared too... you know.

 

Sometimes when I receive an update of an installed program the update states 32bits and my installed software is actually 64bits. What can cause the total bits to be different and what do I need to do to correct this so the information will be correct next time? I suppose it doesn't matter as I install updates myself but I would like for it to be correct. Thanks in advance.

 

WHEN NEW VERSION ?

 

WHEN READY.

 

OK thank you

 

Hi,
Is there a possibility to keep view settings in the Portable Apps ?
This is the default:



And I like to keep it:



Cheers.

 

Hi all

Here are the Changelogs for you all

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

Mops21

 

Microsoft Edge has 3 branches:

edge
Edge Dev
Edge Canary

Ucheck is detecting the Edge Dev version as higher than Edge and this is not correct.

However, ucheck if it has successfully detected the new version of Edge Canary.

Greetings and thanks


https://i.imgur.com/FUo3ODh.jpg

 

Does that mean that UCheck Portable users who have been beta-testing UCheck BETA v5.0.6.0 (UCheck64.exe, offered 23-Nov-2023 in post # 1149) should delete that executable and download the stable UCheck Portable v5.0.6.0 (e.g., UCheck_portable64.exe, rel.04-Dec-2023) that was posted today at https://www.adlice.com/ucheck/#alt_download?

Again, it would be less confusing for beta testers if each BETA and stable release had a unique version number.
------------
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3693 * Firefox v120.0.1 * Microsoft Defender v4.18.23100.2009-1.1.23100.2009 * Malwarebytes Premium v4.6.6.294-1.0.2201 * Macrium Reflect Free v8.0.7690 * UCheck Free Portable BETA v5.0.6.0 (23-Nov-2023) * QuickInstaller Preview v0.2.8734.36059