Jump to content
Piriform Community Forums

Stephen Piriform

  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Stephen Piriform

  • Rank

Profile Information

  • Gender

Recent Profile Visitors

2,311 profile views
  1. Changes in v5.45 and your feedback

    We've actually been in contact with the Windows team about this. They explained that when a Windows update occurs (e.g. Spring Update), various files are held in the Windows.old folder and an automatic migration process is started. This includes items like graphics drivers, which are remain there until Windows can programmatically re-map the paths and migrate them to the correct place outside of the Windows.old folder. In this particular case, cleaning the folder of the graphics drivers would completely break rendering for some users (their screens would turn black). The average CCleaner user does not know how to reinstall a graphics driver when their screen is black, and even a more technical user would find it a PITA. The technology in Windows for cleaning up the Windows.old folder has moved on significantly since the Windows.old rule was first included in CCleaner. This included a regular process for cleaning the folder with the added benefit of 1st-party knowledge of what exactly is in there. Based on this understanding and the fact that (in spite of the fact that the rule is disabled by default in CC and also preceded by a clear warning to the uninitiated) in a minority of cases it had the potential to do significantly more harm than good, we came to the conclusion that there was no longer a strong need for CCleaner to clean here, especially if it could not do so safely.
  2. CCleaner not allowed in your location?

    Don't worry, there's nothing wrong with your connection. This is an edge case that returns the incorrect value. We've fixed it internally so feel free to grab 5.44 until we're able to publish the fix. https://www.ccleaner.com/go/get_ccfree
  3. Changes in v5.45 and your feedback

    Thank you all for your continued feedback (positive and negative, it all helps). I wanted to give a quick progress update on what we're doing. We’re currently working on separating out cleaning functionality from analytics reporting and offering more user control options which will be remembered when CCleaner is closed. We’re also creating a factsheet to share which will outline the data we collect, for which purposes and how it is processed. Today we have removed v5.45 and reverted to v5.44 as the main download for CCleaner while we work on a new version with several key improvements. You can grab version 5.44 from one of the links below: v5.44 Free edition: https://www.ccleaner.com/go/get_ccfree v5.44 Professional edition: https://www.ccleaner.com/go/get_ccpro v5.44 Business Edition: https://www.ccleaner.com/go/get_ccbe (32-bit installer) v5.44 Technician Edition: https://www.ccleaner.com/go/get_ccte (File hashes here: https://forum.piriform.com/topic/52095-ccleaner-v5446575/) Software Changes As stated before, we'll split cleaning alerts (which don't send any data) from UI trend data (which is anonymous and only there to measure the user experience) and provide a separate setting for each in the user preferences. Some of these features run as a separate process from the UI: we'll restore visibility of this in the notifications area, and you'll be able to close it down from that icon menu as before. We understand the importance of this to you all. This work is our number 1 priority and we are taking the time to get it right in the next release. There are numerous changes required, so that does mean it will take weeks, not days. While we work on this, we have removed version 5.45 and reinstated version 5.44.
  4. We don't know why it is not available but we have asked for it to be reinstated.
  5. CCupdate.exe not only scan for security updates.

    Hi TheOwner, Please see this thread:
  6. CCleaner 5.45 riddled with bugs

    Hi everybody, Thank you all for your feedback. We are working on a fix for the Recycle Bin crash. We'll look into the phantom process issue. Please see this thread for the latest information on the analytics topic:
  7. Hi everyone, Thanks for your feedback. Please see this thread for the latest information on this topic:
  8. Privacy

    Hi everyone, Thanks for your feedback. Please see this thread for the latest information on this topic:
  9. Useless new Privacy 'menu'?

    It's a bug and it will be fixed in the next DF release. The GDPR period was not a fun time for anyone in any software company.
  10. Useless new Privacy 'menu'?

    This could not be further than the truth if it were uttered by El Presidente himself.
  11. CCleaner v5.45.6611

    File Verification Please find below the MD5 and SHA-256 file hashes for verification purposes. CCleaner Installers ccsetup545.exe - CCleaner Free Installer MD5: 33136874f7d0c67967dbce12714392d1 SHA256: 805b136fcedbf5451e6d86c89cb90c0198d0e68ff42daee8e95511aea744f543 ccsetup545_pro.exe - CCleaner Pro Installer MD5: 1e13ba95cba43eae7d9f89d993f559cc SHA256: b5ced03c0531e9bf9f7c17e361d98aa782d5005dfa211340c424291aafea6120 ccsetup545pro.exe - CCleaner Pro Trial Installer MD5: 7cbb9c1dde79813b3ebd702e321d3087 SHA256: eb959069bc06d99ef932b5f2542eb4be11bb9f2a9cc5b5fadfe64f7c59441ad8 ccsetup545.zip - CCleaner Portable (zipped) MD5: 26e74a1003393a62ab830332ce27f129 SHA256: d301b8b1f1902ea64e9b3a6404afd7a1e2a88adb3f86b5ad54e5a9cd81aad3ea ccsetup545_slim.exe - CCleaner Free Slim Installer MD5: f642a4ba679efc741ca2252d30877343 SHA256: 71ab866cfdf8bb605a25f61221d493f8e0c21215713041fb19a29d2c2ddde6f5 ccsetup545_te.exe - CCleaner Technician Edition Installer MD5: 27a0a0947cff74b0c601744f371e7353 SHA256: e170f476e3a210397846fd02d1e771b4290b2ba251bc5dec615862b07d06d340 ccsetup545_be.exe - CCleaner Business Edition Installer MD5: 242b08a5252b9e4579f1ed078f6fe295 SHA256: 92c30b0c6ddb27bfdb85f6f8e48e3b29e08f1173dd26ab26cdfe53ba3c1cae43 ccsetup545_be_trial.exe - CCleaner Business Edition Trial Installer MD5: a851093cb699c62c4f2a7843524339d5 SHA256: 02b457ba209a6012a3e4e1bb437fb70f7543c7e765acdda6c9152079bc0add01 ccsetup545_x64_be.msi - CCleaner Business Edition 64-bit MSI Installer MD5: d6c288751f857a539bf208cef7bfa872 SHA256: 388aeda8a667c5d4dc77d240daa5bdc856000c051b85735bd9604d1fe48bc0ed ccsetup545_x86_be.msi - CCleaner Business Edition 32-bit MSI Installer MD5: 90b3252c5d00248bfb511758a8da7be5 SHA256: 54771fc4f02a94c05d4b4f663af5c02b6ae6b6d92a089207212918ad073312c4 CCleaner Application Executables CCleaner.exe - CCleaner 32-bit binaries MD5: a16739be4ef551df0be8164bcf977bf2 SHA256: b2d1186f94dd03e1e85cd213e83a8379ee933a204ff72306abaa581b923e6660 CCleaner64.exe - CCleaner 64-bit binaries MD5: f30e7478f7964f02cca471409e339a72 SHA256: 228ee9790c2fa6a2720877bfd19bd71379af199f487dc19875b72b7b2676134a CCUpdate.exe - CCleaner Emergency Updater MD5: 47113704001c02b0489cd9f3b11a8355 SHA256: 530e91237b0aec84262904fd697d05b12ce6fb95a78c57293ee94a7f28981b17
  12. update c cleaner 5.44

    Welcome to the forums! This is an English speaking forum. If you use a translator such as google.translate.com we should be able to understand and will be more than happy to help with your query! Welkom bij de forums! Dit is een Engels sprekend forum. Als u een vertaler zoals google.translate.com gebruikt, moeten we dit kunnen begrijpen en zullen we u graag helpen met uw vraag!
  13. Hi everyone, Malwarebytes has been removing the CCleaner.exe executable during the automatic update process (a feature of the Pro/Business/Tech edition only), and that is used for some functions of CCleaner. This was producing the behaviour described. In this case, there is another cause which is an update to Windows 10 (build 1803) that is breaking this functionality. We are working on this issue currently and anticipate a fix for the v5.46 release (release after the next one). @Arbie you can return to the pure Free edition by uninstalling Pro and installing Free from www.ccleaner.com/download. If you never purchased a Pro license, your product will not have activated Pro features anyway, it will basically be the Free edition of the software.
  14. CCleaner v5.44.6575

    v5.44.6577 Minor update 6577 changes a shopping cart URL in the Pro and Pro Trial editions only. File Verification for v5.44.6577 Please find below the MD5 and SHA-256 file hashes for verification purposes. CCleaner Installers ccsetup544_pro.exe - CCleaner Pro Installer MD5: 0d56fc231cb80462ef0290837953c82e SHA256: 05cf039451423ee1cc2a4571f65657d230f6ada17b5ac01750ac2e8d94baf18e ccsetup544pro.exe - CCleaner Pro Trial Installer MD5: 0016855bb7bb110ed520565451015871 SHA256: bfbc3007747caf507636806b055a5db82b0d05e01a0a0d63da2a1439b02f1581 CCleaner Application Executables CCleaner.exe - CCleaner 32-bit binaries MD5: 171b075462a3a3e6c52a54fa5d4ae344 SHA256: 0fd922a6e752bd7fef9707c4990df6d4013cb3fab0e4b5d866be2605249c03ff CCleaner64.exe - CCleaner 64-bit binaries MD5: c776ce456738ae83bf5694ed7f74201a SHA256: 46363ab40ec5345aebd4ebb9962f627536f9bf16b5b81320a672d9f80b59d9d8 CCUpdate.exe - CCleaner Emergency Updater MD5: 5a9e451000e2d6271739f0b73829b5e1 SHA256: a32d7789030295cc36ed1103d60b00059221802020df3ed9e95e948b07cbd472
  15. Error while updating to V5.44.6575

    v5.44.6577 6577 is a minor fix for a shopping cart URL in the Pro & Pro Trial editions only (one for the 'Subscription Expired'). It didn't merit a big announcement or prompting people to update as it affects a very small portion of the userbase. I will however take on your feedback about transparency and include the MD5 for 6577 in a separate post of the Announcement thread in the forum for clarity, with this mini changelog. Update Failures This change is in no way related to the original post in this thread regarding failed updates. There is a known issue with MWB Ransomware Protection feature that breaks the update process of both CCleaner and other applications such as Skype, Visual Studio Community Edition and so on. MWB have released a fix for this to their Beta programme. Furthermore, Norton had been originally blocking the file on release, in spite of us releasing the installer files to VirusTotal ahead of time. This could be because their heuristics rely in part on MWB, or perhaps there was some other false positive triggering it. Either way, by the time I sent the False Positive report through it had already been fixed.