Jump to content
CCleaner Community Forums


  • Content Count

  • Joined

  • Last visited

Everything posted by nukecad

  1. You seem to be labouring under a few mishaprehensions. I am not a Piriform employee, I am a user and volunteer - as are all the moderators here. It is not 'my programme', I do not have access to the programme code. If you choose to do a Wipe Free Space on 3 drives everytime you run CCleaner then that is entirely up to you, but it is not normal practice and is unecessary. Again: There is a CPU leakage bug in v5.69 that has been acknowledged and is being fixed. It is only affecting a minority (like yourself) who are using CCleaner in certain ways, most users aren't even aware of it. You have been advised that if you temporarily stop using Wipe Free Space on all 3 drives in CCleaner then you will not see the issue. Again it is entirely up to you whether to take that advice or not, but if you don't then until the next update you will keep having the issue. Once the bug is fixed in the next update you will no longer see the issue, and you can go back to wiping all 3 drives if you want to.
  2. After Duplicate Finder has found files then the 'Delete selected' button is greyed out until you actually select a file or files to be deleted. Is that what you are meaning? If not then could you attach a screenshot of what it is that you are seeing.
  3. You need to contact support to resolve licencing issues; it's not something that we can do on the open forum. (For security/privacy we can't see licence information here). You should email them at: support@ccleaner.com If possible send your request from the same email address that you used when registering CCleaner. (If that's not possible then noting that registered email address in your request, if you can, will make it easier for them to find your account). You should get an automatic acknowledgement by return email that your request has been received and is in a queue for action, if you can't see one then check your email spam folder.
  4. You have been answered twice here already, I'm sorry if you cannot understand that answer - here it is again. Yes, there is currently a bug in CCleaner v5.69 that is causing a 'CPU leak' and slowdow/freeze in certain circumstances. Whether it happens to you or not depends on how you are using CCleaner. It is happening to you personally because you are doing a Wipe Free Space on 3 drives, it is not normal to do that every time you clean. Yes, it will be fixed in the next CCleaner update. To stop your freeze it until the update/fix is available: Stop doing the unneccessary Wipe Free Space that you are doing on 3 drives with every clean - Open CCleaner, Clean normally (without the Wipe Free Space), Close CCleaner - then you will not see the freeze.
  5. Yes, it's a bug in v5.69 and as said above it will be fixed in the next CCleaner update. It's a problem with 'leaking' device context handles, as you say that you are not a newbie to software user then you will probably know that 'leak' means that the longer the programme is open the more of the CPU it will want to use. Closing the programme means it is no longer trying to hog the CPU. This is why with normal use most users are not even aware that there is an issue, they open CCleaner, clean, and close CCleaner - the leak does not have time to affect anything noticably. Only those who leave CCleaner open for longer times notice it, because the programme is open for longer it has time to hog the CPU. In your particular case you are regularly wiping free space on 3 drives and that is not normal usage, (Wipe Free Space is not meant to be used like that), and that will mean that you have CCleaner open for longer than it would be in normal usage. So it then becomes a race between can CCleaner finish wiping your 3 dives before the leak causes your CPU to top out, from what you describe then it is finishing the wipes but then because of the leak it has no more CPU resources to do anything else. In that circumstance force closing CCleaner (by task manage or a restart) frees up the CPU again. I suggest that if you realy insist on continuing to wipe all 3 of your drives with each run of CCleaner, which is your choice to make, then you stop wiping them until the next CCleaner update fixes the context handle leak. For now untick Wipe Free Space and just do the cleaning without the wiping of free space. (Alternatively wipe one at once, closing and reopening CCleaner between each one). Once the leak is fixed in the next update then you can go back to wiping free space every time if you want to. (But it's not necessary). PS. While SSDs can stand many more rewrites than they used to do in the early days they still have a limit on how many times they can be written to, it's just a much bigger limit than the early SSDs had.
  6. This has been posted twice, I have answered here : https://community.ccleaner.com/topic/59091-ccleaner-hangs-while-cleaning-disks/?tab=comments#comment-322683
  7. I believe that what you describe as 'hangs' is simply CCleaner taking a long time to wipe your free space. The settings that you have made will mean that it will take a very long time to wipe your free space, especially as you are doing it for all 3 of your drives. You have 'Wipe Free Space' selected in Custom Clean and the other settings apply it for all 3 of your drives. 'Wipe Free Space' is not meant for use on a regular basis and should hardly ever need to be used. You should have it unticked for normal cleaning. It is a tool to use when you are selling or passing on your computer or hard drive. It removes the remnants of deleted files so that they cannot be later recovered with a recovery tool. It will not 'clean up' your computer for normal use, or make it run any faster. Wipe Free Space is also not needed on an SSD and using it regularly, as you seem to be, can shorten the life of an SSD. So untick your drive if/when you do use Wipe Free Space. You then have 'Secure File Deletion' set for 7 passes, Wipe Alternate Data streams, & Wipe Cluster Tips. You do not need to use secure file deletion on an SSD. (And it can also shorten the life of an SSD if you do use it). With a modern HDD one pass is sufficent for secure file deletion, more passes are not needed on modern computers. With your disc setup I would suggest that you don't use secure file deletion, if you do then one pass only. Finally - I believe that by "your program loads the operating system very strongly" you are meaning that CCleaner is using a lot of the CPU? This is a known issue in certain circumstances, the cause and fix is now known, and it will be fixed in the next CCleaner update. In the meantime be sure to close CCleaner after using it, - it is only if you leave CCleaner open (or minimised to the taskbar) after use that the high CPU usage build up. It will be happening to you because you will have CCleaner open for a long time while attempting to wipe the free space on all 3 drives.
  8. Partly tounge-in-cheek, but: Remember that it is the browser that changed things, not CCleaner which now has to catch up with what the browser programmers changed (as will all other 3rd party cleaners). So shouldn't you really be shouting at mozilla for changing things in the first place?
  9. Requests to support are handled on a 'first come first served' basis, so new requests get queued and dealt with in order. Which may mean waiting awile for a response if they are busy. We are told that sending multiple emails/support forms can actually slow down the response. TBH though I don't see why they can't send an acknowledgement that your request has been received and will be actioned, I'll suggest it to the staff.
  10. @Bethy54 Hi again, Things have been happening, and after some testing the cause of the rising CPU usage and computer slowdown issue has been pinned down, how to fix it is known, and it will be fixed in the next CCleaner update. (Apparently it was a problem with "leaking device context handles"). Hopefully that update will be soon, but I have no influence over when updates are released. Your posts, and having your machine checked over at Malwarebytes, has helped pin down just what the cause was. Thanks for doing that. From the testing that I did myself it does only happen when CCleaner is either left open on the dektop, or open and minimised. (Because of the nature of 'device context handles' Task Manager doesn't show it using up the CPU when it is minimised). Closing CCleaner stops it happening and frees up the CPU again. If CCleaner is not open (or not open and minimised) then it can't happen. (Because if CCleaner is closed it can't be using device context handles). What you did with AdvancedSetup over at Malwarebytes was simply to make sure that your machine did not have any malware/virus/other nasties, which is always a good thing to know and never a waste of time. So thanks again for doing that, it helped.
  11. For those who don't have a ccleaner.ini, or don't want to edit it manually, you can apply the exclusion/workaround like this: After using Firefox close it, open ccleaner and go to Custom Clean. Click on Analyze Double click on 'Firefox - Internet Cache' (You may need to expand the window to see the full pathnames, but they may be the only two files there). Right click on '...\storage-sync-v2.sqlite-wal' Click on 'Add to Exclude list' Right click on '...\storage-sync-v2.sqlite-shm' Click on 'Add to Exclude list' Job done. Note also that Exclusions only apply to Custom Clean, Health Check ignores Exclusions. PS. If you don't have your Firefox synced with a Firefox account then you don't need this workaround.
  12. Speed of defragmenting depends on quite a few things, including the total size of the drive, the free space available for the defragmenter to work with, and just what type of 'Defragment' you are doing. As said above there are different types of 'Drefragment' see the link below for more information. The larger drives available for home use these days means that of course they are going to take longer to do a full disc defrag (consolidation), the solution is to do a file defrag instead. With larger drives you are unlikely to be running out of free space, so what you want from a defrag is different to consolidating files to free up space. See this for more information on the different types of 'Defragment' that Defraggler can do, and how to specify each or a combination: https://community.ccleaner.com/topic/58213-program-increases-fragmentation/?tab=comments#comment-319520
  13. ESET is currently doing that. You should note that the detection says 'Potentially unsafe application' which does not mean that what it is flagging is unsafe. AV's use that wording when there is something in the file that you may not want, although normally they say 'Potentially unwanted application'. (ESET likes to be dramatic). At the moment a few AV's have taken issue with the fact that the Standard CCleaner installer contains a 'bundled' offer for other software. Many free-to-use programmes (and some paid ones) include offers like that, it doesn't make them unsafe - If you don't want the offered software then simply don't accept the offer. Some AV's have also suddenly decided to take exception to CCleaner itself because it contains a Registry Cleaner - which can cause damage if used unnecessarily or incorrectly. (Some AV's are getting a bit "Granny knows best" overprotective). You can either tell ESET to ignore the warning, or try using the 'Slim' installer (which is the same but doesn't contain offers) from here: https://www.piriform.com/ccleaner/builds PS. The CCleaner installers work on both 32-bit and 64-bit, one installer does both - another indication that ESET may be being overzealous?
  14. If it's not been automatically updated then it does look like you will need to contact support to chase this up; we don't have access to individual licences on the forum The standard contact form is found here: https://support.piriform.com/hc/en-us/requests/new Or you can email them: support@ccleaner.com
  15. Accepted, Have you had time to look at the testing/debugging issues that I raised yesterday?
  16. I resent that somewhat. I didn't 'find a way to break it' - it was broken at the server end. I can't replicate it because I haven't tried to, - no point trying because it was broken at the server end.
  17. I hope that's going to be something useful like which AV/version/definition is being used? Which Windows 10 version (and maybe build) would also be an improvement over just 'Windows 10 64-bit'.
  18. Yes it's all a bit odd. PS. I've just been fixing up a laptop for a friend and after reinstalling Windows set the user account name to 'User' so they could change it to what they want later. So for now that one does have "C:\Users\User\....." as a valid pathname.
  19. Just for info- You can achieve that with Snipping Tool, (at least with Win 8 or 10 - not sure about Win 7), I do it all the time. That's what the 'Delay' button in Snipping Tool is for. Simply set a delay for the snip (3 seconds is usually enough), click 'New', and drop down the context menu during the delay. Then after 3 secs the tool will freeze the screen with the menu dropped while you take the clip, eg:
  20. Good spot on the filename @lmacri. That also seems an odd location to be downloading .exe files to. (But I guess some browsers may put '.part' files there?) Just what 'WQchxgI+.exe' is I don't know, and can't find anything on google. So why ESET thinks that file is CCleaner is also an odd one? An in-progress CCleaner installer download would be called 'ccsetup569.exe.part'. File Explorer shows it like this while it is downloading to your Downloads folder (this is a download from Firefox): Once the download is completed the '.part' file disappears and 'ccsetup.exe' will show the full filesize. (26,320 KB for ccsetup569.exe). PS. I'd still be careful at the moment with ESET and CCleaner or other already installed Piriform apps, as seen from my link above ESET may remove them unless you have made them exceptions.
  21. I wasn't suggesting a scan in Defender - I was meaning a clean of Defender using CCleaner.
  22. I'd tell ESET to 'Ignore' it for now, and be careful with ESET settings: Untick 'Copy to Quarantine' and tick both 'Exclude from detections'. Another user reports that ESET removed all his Piriform apps: https://community.ccleaner.com/topic/59009-eset-cleared-ccleaner-out-of-my-pc/?tab=comments#comment-322477
  23. This was originally posted in a thread about Windows Defender - I've split it, and the relevant replies out into it's own ESET thread.
  24. I'm not sure if running Custom Clean with Windows Defender selected would remove them? (OR - Applications tab, right click on Windows Defender and select clean). I do know that if you do clean that then Defender thinks that it has never scanned your machine. Mine resets back to last scan in Sept 2018 if I do that.
  • Create New...