A tiny bug, but a very odd one. In the latest CCleaner for macOS (v. 1.18.30), it identifies the OS version as 10.16. But I'm running Big Sur, version 11.0.1. How could it get this wrong?
Not a big deal, and no response expected, but maybe someone at Piriform will notice it.
<div class="ipsQuote_contents ipsClearfix" data-gramm="false">
<p>
In the latest CCleaner for macOS (v. 1.18.30), it identifies the OS version as 10.16. But I'm running Big Sur, version 11.0.1. How could it get this wrong?
</p>
</div>
Big Sur was expected to be called Mac OS X 10.16 (and beta versions were identified as such) but Apple decided at a late stage to call it Mac OS 11.0.1 instead, apparently catching a lot of people by surprise.
But there may be more to it than that:
It seems that it was such a late decision on Apples part that some internal labels <em>in Big Sur itself</em> still call it OS X 10.16, so CCleaner may be picking one of those labels up.
<div class="ipsQuote_contents ipsClearfix" data-gramm="false">
<p>
Apple announced macOS 11 Big Sur at WWDC 2020, and while there are some lingering system labels for macOS 10.16, that OS technically does not exist.
</p>
</div>
<div class="ipsQuote_contents ipsClearfix" data-gramm="false">
<p>
Big Sur was expected to be called Mac OS X 10.16 (and beta versions were identified as such) but Apple decided at a late stage to call it Mac OS 11.0.1 instead, apparently catching a lot of people by surprise.
</p>
</div>
By way of official comment I can confirm that this is exactly what happened to us. We released a BigSur compatible version in advance of the BigSur release and then Apple changed the version numbering at the last minute. This is on a list of minor tweaks to be made in a release in the new year.
We had noted a number of customers experiencing issues with starting up CCleaner 1.18.30 under BigSur 11.0.1 - but these were not replicable in testing, and reports that we have had back from customers have been that the BugSur 11.1 update has been resolving these. This would suggest that there may have been MacOS bugs rather than CCleaner bugs at play here, but we're keeping a close eye on the situation.