SOLVED: Failed To Get Installed Software From Definitions (Software Updater)

I just got this message as well, pro edition.

ccleanerproerror.png

This seems to be a common problem reported by many this week.

The software update feature seems to have been released too early, without comprehensive testing.

I have no doubt that Piriform (and Filehippo) are looking into it.

Looks like a server outage issue has arisen over the weekend - should only impact the software updater. Appropriate folks are being poked.

This problem is also occurring for me. It seemed to happen after the latest Widows 10 updates I installed on 10 July. KB4506991 and KB4507453.

I tried reverting to a copy of CC557 that I still had but the problem is appearing there too. I suspect something in the Win 10 update has invalidated part of the CC code.

Ray

4 hours ago, Dave CCleaner said:
<div class="ipsQuote_contents">
	<p>
		Looks like a server outage issue has arisen over the weekend - should only impact the software updater. Appropriate folks are being poked.
	</p>
</div>

Thanks for letting us know about the outage. That would certainly go a long way to explaining why it hasn't been able to get installed software and appropriate updates!

12 hours ago, TheEdCase said:
<div class="ipsQuote_contents ipsClearfix">
	<p>
		I suspect something in the Win 10 update has invalidated part of the CC code.
	</p>
</div>

No. As per the above it was purely a server-side issue and not related to Windows or the client version of the software. This has now been resolved as of 0900 UK time, and Software Updater should now be functioning normally. No other CCleaner functions were impacted.

Update: Note that this error message would have been seen by paid and trial users, as well as free users navigating to the Software Updater screen

Update: Merged the 4 threads on this topic.

1 hour ago, Dave CCleaner said:
<div class="ipsQuote_contents">
	<p>
		No. As per the above it was a server-side issue. <strong>This has now been resolved</strong> and Software Updater should now be functioning normally.
	</p>
</div>

Wonderful. I've just tried it and, while it isn't recognising the need for any updates (which is what I expected), there's no error message. I think I can safely say that the issue has been resolved so far as I'm concerned. Thanks to those working on the server for their hard work, and to you for informing us.