Jump to content
CCleaner Community Forums


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About PSM17H

  • Rank
  1. CCleaner 5.52 Update fails

    Hazlenut: Are you sure you are not a witch? That suggestion cured it - thank you!
  2. For a number of weeks, I have been prompted to update CCleaner (5.51.6939 - 64bit) to the latest version (5.52.6967) but each time that I attempt to update, it fails in the 'setup' stage and displays a dialogue box "Error opening file for writing: >Path to the location of the .exe file<" followed by 3 options to either: Abort / Retry / Ignore. (Screenshot attached) I have, over this period, tried each of the A/R/I options - none of which were successful. Via this forum I have seen a couple of 'suggestions' which very loosely were close to my error and I have tried them, one being to disable Malwarebytes Premium (never had to do this before) and the latest being to download CCleaner 'Slim'. Both, as I say, were attempted and both resulted in the same outcome. I am a long time user and advocate of CCleaner but this is now getting tiresome, I have more important work to getting on with rather than trying time after time to get this irritating update applied. Any suggestions/resolution would be appreciated!
  3. Ccleaner will not install

    First time user of the forum, but long time user of CCleaner. (Since before the name was shortened!) I am on Windows 10 (Creators) x64 with the latest updates (OS 15063.540) CCleaner v5.32.6129 Used the "Update available" button and this has resulted in a fail like everyone else. The installation was at the "Extract: CCleaner.exe" stage. I have tried the "Ignore" option like #Genez, mine too stated it had installed succesfully, but when opened I was offered the option to update to 5.33 again. So hitting "Ignore" DOESN'T cure the issue - at least not for me! I suppose the question is .... is 5.32 PREVENTING installation of the new update - or is 5.33 FAILING to update? Clearly one for the techies at Piriform - I will happily continue using 5.32 until "33" gets sorted - because the one thing I didn't want to do is uninstall a version that DOES still work! Looking forward to a fix soon!