"CCleaner could not be updated.", manual check for updates fails..

[Melchior]

it seems as though it does not like my license key.. which is good till next June 24th 2023...

CCleaner requests I purchase or enter a key.

fix please.?

[nukecad]

This issue was known about and supposed to have been fixed.

Download the Slim installer from the builds page and double click  the downloaded file to install the update, (don't uninstall the old one just do it over the top) that worked for me about 2 hours ago.

https://www.ccleaner.com/ccleaner/builds

[Melchior]

I use the Pro version.. so the slim installer might not be the best fit..
I do keep the CCleaner pro download link bookmarked... so I grabbed that already..

 

 

and btw when ever I go to do a driver update check...

it re-enables the System Restore feature even though I Don't want it enabled on my NVMe system/boot drive..

so I don't bother suing that feature anymore...

[nukecad]

No problem with it being Pro, mine is also a Pro licence.

Just install over the top and the licence is picked up.

I always use the Slim installer rather than updating through CCleaner itself. (Unless I'm testing the updater, see the next post).

If you should happen to uninstall the old one then just install the Free version and re-register it.

[nukecad]

Just for information in case anyone else sees this particular error:

I did some testing, rolling back to 6.04, checking for updates and updating to 6.05, rolling back again, checking again, and so on.
Eventually after 6 tries I did manage to replicate this error, but only that once and not again since.

When I did get the error simply closing CCleaner, then re-opening it and checking for updates again was all that was needed to get the update as normal.

[nukecad]

16 hours ago, Melchior said:

and btw when ever I go to do a driver update check...

it re-enables the System Restore feature even though I Don't want it enabled on my NVMe system/boot drive..

so I don't bother suing that feature anymore...

I remember you reported back in August that it was turning on System Restore everytime that you launched CCleaner.

That was fixed in v6.04 so that it no longer turns on everytime - but it still turns on if you do use the Driver Updater.
It's intended as a precaution so that you can do a restore if updating a driver has adverse effects.
https://www.ccleaner.com/knowledge/ccleaner-v6-04-10044
 

Quote

Fixed CCleaner re-enabling Windows System Restore on every launch;
going forward, System Restore will only be activated if enabled via Driver Updater

 

[Melchior]

8 hours ago, nukecad said:

Just for information in case anyone else sees this particular error:

I did some testing, rolling back to 6.04, checking for updates and updating to 6.05, rolling back again, checking again, and so on.
Eventually after 6 tries I did manage to replicate this error, but only that once and not again since.

When I did get the error simply closing CCleaner, then re-opening it and checking for updates again was all that was needed to get the update as normal.

ok I will keep that in mind. next time it happens if it does..

 

8 hours ago, nukecad said:

I remember you reported back in August that it was turning on System Restore everytime that you launched CCleaner.

That was fixed in v6.04 so that it no longer turns on everytime - but it still turns on if you do use the Driver Updater.
It's intended as a precaution so that you can do a restore if updating a driver has adverse effects.
https://www.ccleaner.com/knowledge/ccleaner-v6-04-10044
 

 

I still don't like it being on... I can start in safemode if I have an issue to roll back a change..

I don't want it turning on System Restore every time I check for driver updates...

its eating up my write cycles of my Samsung EVO 970 NVMe SSD 1TB

[nukecad]

12 hours ago, Melchior said:

its eating up my write cycles of my Samsung EVO 970 NVMe SSD 1TB

I understand your concern, and it's always your choice how you use your kit.

However having System Restore turned on with a SSD isn't such a problem as old articles (and even some modern ones) found on the net might have you believe.

It wasn't really much of a problem back then, more a worry/uncertainty like you always get with any new technology.
Modern SSDs like your Samsung also have vastly more write cycles than early SSDs did.

Your particular Samsung 970 EVO has a 1,200 TBW (Terabytes Written) endurance. (1,228,800 GB).
https://semiconductor.samsung.com/consumer-storage/internal-ssd/970evo/

To put that into context:
I just created a new Restore Point, the Control Panel tells me it's taken up 0.2 GB of disc space on my SSD.
At that size it would take you 6,144,000 RP's to reach the write endurance for the Samsung 970 EVO.
Or if you prefer 1 restore point a day for the next 16,832 years.
Or 841 RPs every day for the next 20 years.

Looks less of an issue when you put it like that doesn't it?
It certainly doesn't bother me having Restore Points turned on.
(Just to note that the previous RP I had was from Patch Tuesday, 15 days ago. So it's not like it's even writing one daily, it only did one today because i told it to).

Again it's always your choice, but sometimes it's interesting to double check what you may read on the net.

[hazelnut]

A point to note if that if you use 3rd party imaging tools (e.g. Macrium Reflect) some may feel System Restore is not needed, but only if you use another means of restoring your machine.

 

[Melchior]

2 hours ago, hazelnut said:

A point to note if that if you use 3rd party imaging tools (e.g. Macrium Reflect) some may feel System Restore is not needed, but only if you use another means of restoring your machine.

 

I don't bother with third party imaging tools..

I rely on good luck... lol..

so I won't be using CCleaner's driver updater goign forward because of this issue I mentioned with System restore always being re-enabled...

even when I disable it...  and will keep the version on my laptop at v6.02 before Piriform stared doing this on us...