Jump to content
CCleaner Community Forums

mxz55

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mxz55

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It could be interesting for others to know exactly what did the trick. Do you mean a chkdsk with "disk repair", or some sort of HDD health regeneration software? Anyways, if the latter was neccesary to get free space wipe to start doing something meaningful, then you can rest assured that your HDD is at the end of its lifespan, deteriorating, and that this "repair" has only temporarily extended it. This then also explains why you always were able to do free space wipes on acceptable speeds (you said that you noticed things changed) on the same huge sized HDD. So in that case I would
  2. Updating would make it go away huh? Well in that case, I wonder what this user means; So that person who was also experiencing this bug, said that he rolled back to the old version, hoping that it would go away. That probably means he was previously using a more recent version. Experiencing the same bug.. So let's wait for @johnniedoo to clarify (although i doubt he's still active here) or hear if someone else is having this problem on newer versions as well.
  3. Yes, i can reproduce this for months, also now on Windows 10 1903 and the latest CCleaner release; you can never see the clean results, because CCleaner will disappear at (or before) reaching 100%, so you cannot know if the scan you ordered deleted (all) the files it's supposed to. yeah, and it's also sad that people are always trying to make up excuses/justifications for incorrect behavior of software, like in this older post: Clearly; - most if not all cleaners except for CCleaner are able to function correctly in safe mode. - as someone else said, people want to do
  4. I would recommend the syntax chkdsk /F /V /R /X /B /spotfix to anyone that wants to run it for fixing errors/mainentance. It's a Windows feature, to check for disk errors and automatically attempt to repair them. So it's safe. Anyways, on traditional hard disks (even more so those without a high read/write speed in MB/s, or with a lot of data or free space), "wipe free space" can only be expected to take extremely long. If you think it was previously way faster, then think about if the free space or used space was around the same, if it was, then yeah your disk's healt
  5. The environment is CCleaner with default settings, and Winapp2.ini from https://github.com/MoscaDotTo/Winapp2 placed into CCleaner's installation directory root. Current behavior: per the CCleaner default settings, the starting screen is Easy Clean, due to Winapp2 presence this will cause the CCleaner thread to freeze on launch, or exhibit another technical issue resulting from Easy Clean being unable to handle the presence of this file. Symptom: CCleaner will not appear to be launching for mostly over a minute. After clicking the CCleaner application icon, it will only show CCleaner
  6. That's not what I mean.. I am talking about the fact new CCleaner versions encounter technical issues just from the presence of a Winapp2.ini file. Even though I added a note about this being unrelated to trimming, you seem to not have understood my point either. The thing is that there are now 2 delays: the trimming thing (big amount of entries), and a long delay of CCleaner even appearing on newer versions due to the presence of Winapp2.ini, when the launch screen is Easy Clean. During this time, CCleaner won't be visible entirely, but only in Task manager as a process. The
  7. Did anyone notice that after the recent CCleaner updates (in which they added "Easy Clean" feature), on default configuration CCleaner can take over a minute to launch when Winapp2.ini is present in the install folder? NOTE: I mean CCleaner not appearing at all (with a huge delay), not the usual slow loading of application entries until CCleaner becomes responsive. Now, it would be both the delay in launching, and on top of that the usual delay if you didn't trim the ini. The reason being that it appears the "Easy Clean" is incompatible with Winapp2, so it causes a delay because the
  8. About: Black Friday popup ads covering the "Run Cleaner" button on fullscreen app mode I dislike the behaviour of Piriform company, they started becoming more commercial and while they already made a bunch of money from CCleaner, they want to focus on monetizing the tool even more and now resorted to pretty intrusive ads, harming their reputation. I am starting to get less and less sympathy for CCleaner developers, for some reason this move gives me a sense of their arrogance. The aggressive pop-up advertisements were engineered to cover the "Clean now" button entirely, on start
  9. CCleaner is loved by developers for the obvious reason of advanced users taking care of their system. I suggest adding an option to clean some cache locations that fill up lots of disk space for the average developer, you could list some common dev software such as "Microsoft Visual Studio" and/or "Debugging Tools for Windows" under the Applications cleaning submenu. When someone is using Debugging tools for Windows, especially software like WinDbg, the disk tends to get filled up with symbol files (pdb, dll for crashdumped apps that fit the host machine it crashed on and which you're ana
  10. I suggest CCleaner to support cleaning of the Windows shader cache. It is located at C:\Users\[username]\AppData\Local\D3DSCache\ and Windows Disk Cleanup has supported it for ages, so then why not also CCleaner? I am successfully using it as 'include' custom cleanup rule for a long time.
×
×
  • Create New...