In practical effect it's just a confusing message that occasionally shows and the update gets done anyway. Which might explain why it seems to be low down on the to-be-fixed list and hasn't been done yet? So there is no need to run the update again, it has already been done. This particular updating crash doesn't really matter because CC has been updated despite one of the parallel running installers crashing. Well that explains why the version of CCleaner that auto launches during the update process is already on the latest version. It would be interesting to know if that is the case like I suspect. If you see the error again next time you update then instead of trying to update again open CCleaner and check if it has already been updated. That's because it's caused by 2 installer instances running at once, and only one of them crashes, so the other should still complete the update. I've not managed to test it properly because you can't deliberately reproduce the write error, but I think that even when you get the error you will find that CCleaner has been updated anyway. The file writing clash and so the error only happend ocasionally on Win 10, I'm just wondering if it is more likely with Win 11? There again I don't normally use the built in update function, instead I download a new installer from the builds page and use that.īack in March 2021, in that thread that Redwolfe_98 linked, I took a look at just what was going on: Yes, I've not seen it myself for a while so though that it had been fixed.

Ccleaner pro free glitch