Jump to content

Donald-w

Members
  • Posts

    1
  • Joined

  • Last visited

Reputation

0 Neutral
  1. I am having a similar problem. ID bar says: CCleaner Free v5.22.5724 (64-bit) Windows 10 Pro 64-bit Intel Core i& CPU870 A 2.93GHz, 8.0GB RAM, AMD Radeon HD 5570 Generally when I use Run Cleaner it runs with a couple of minutes. It has now been running for hours and has stopped at 32%. It does show changing files under System Temporary files*, so it is not totally frozen, but progress is excruciatingly slow. I checked for a later version, but unfortunately it says I have the latest. It is possible I have a large number of temporary files that have crept in or something, but I would think some more evident progress would occur. Also unfortunately there is not option to stop CCleaner and allow it to process what it has done so far. I guess this is not usually an issue, but it would be a nice feature when the program is taking this long. I hate to stop it after hours without any benefit. I have never had this happen before. The closest to any complaint I have had recently is that after running CCleaner registry scan and fix is that my printer definitions get lost (HP LaserJet P1006). I think that is more of an issue with Windows 10 though. I guess if that is my largest issue I am lucky. ;-) When that happens I run small HP driver I downloaded, an eventually the printer will start cranking out the print job. Like I said, I really do not know why that happens, but just mentioning it in case it relates to any CCleaner issue. If it really is just a large number of temp files slowing CCleaner down, should I manually delete them before running CCleaner? Seems to defeat the purpose, but I would like to make some progress. Thanks for any attention and/or info. -- * C:\Users\Don\AppData\Local\Temp\Mimo\binheader\***** P.S. Although progress indications could have more exact, I think ultimately it was just a lot of temporary files that had gotten created that needed to be deleted. CCleaner did actually finally finish and worked. I ran it again, to check, and it was much quicker. Thanks.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.