Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by mxz55

  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 stop relying on your HDD, evacuate important files, and get a new one.
  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 mainentance tasks (like using a cleaner) especially when there is a problem, so it's very likely people that have a problem causing them to go to safe mode will use a cleaner as part of their mainentance tasks. The usability in this scenario is significant, so it's not an excuse to say "why use a cleaner in safe mode". Also because of this correlation (people intending to use CCleaner in safe mode for specific reasons), it means the user experience of the software is impacted. It's a technical CCleaner issue, you cannot put it on the user. Maybe CCleaner relies on a driver that cannot work properly in Safe mode, or something like that or mentioned (about web end) earlier, but if anything is going on, then it's a result of CCleaner doing awkward things (that can fail in safemode) or relying on unconvential things.. yeah, because most competiting cleaners can work properly.
  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 health might be deteriorating (and with that the reading/writing speeds). Also make sure to check in CCleaner options, if you didn't accidentally select more hard disks/drive letters to clean in Wipe free space mode, than you previously used to.
  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.exe in the task manager. It will not show the interface until it is "done" bugging. After that phase, it will start the original delay of processing the countless of Winapp2.ini entries (which is understandable and acceptable) once you click Custom Clean interface, which is only now possible because CCleaner has finally displayed itself. Previous behavior (before the "Easy Clean" feature update): CCleaner will start, and if the same Winapp2.ini is present, start getting a delay in usability on the Clean (now Custom Clean) tab, as expected due to the numerous Winapp2 entries. So as you can see, you will get a double problem with Winapp2.ini's as a result of the latest CCleaner updates. It became 500% worse and more impactful on the user experience of CCleaner. I really think that is avoidable. It is easy to set Custom Clean as launch screen so the issue is avoided, but average users (or first time using Winapp2 or any custom ini) can be misled into thinking the INI broke their CCleaner completely, because it appears not to start at all (except for in task manager as explained) for over a minute. This means they are more likely to remove the ini and never attempt using it again, because they believe it breaks CCleaner from starting properly. This is a shame, and with just a small 'fix' in CCleaner this can be completely avoided, just by making it like the Easy Clean interface wont load the component that tries to load the ini, or fixing the reason it freezes the thread or delays the interface from showing.
  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 latter is a technical issue. Due to this technical issue, the default config would cause CCleaner not to open entirely for over a minute, as it's then configured to launch in Easy Clean mode. After which it gets the regular (understandable) delay of loading the entries on top of it (spinning cursor over the applications list) I think that facing users with a technical issue by default is less than ideal Starting to get the point now? ; p Basically, until you put it in settings to load in Custom Clean on launch, you will have a double waiting time. This is an application freeze, because Ccleaner tries to load Winapp2.ini in a mode that doesn't support it. It's a program behaviour change since the updates, a bug.. and it affects ini users.
  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 main CCleaner program is still trying to load it (and gives it a long time-out delay). Basically, the time out means the main program eventually gives up on trying to load it, but after a really long amount of time. Workaround: go to CCleaner settings, and set "CCleaner home screen" to "Custom Clean" (this is under the language option) So yes it's easy to solve for an user that knows the reason of this problem, the delay will go immediately, but I think it's less than ideal for any new user of CCleaner. They will think Winapp2.ini broke CCleaner, like the process exists in task manager for more than a minute without having CCleaner show itself. I know CCleaner principally doesn't support add-ons like this, but perhap @APMichael or @Winapp2.ini can kindly request Piriform developers to find a solution, so that addons like this won't deteriorate the user experience by default. Especially as this is an issue brought on by CCleaner getting changed. If Custom Clean is incompatible with Winapp2.ini (and the core progra tries to load it there if its the start screen) then it should be only 1 line of program code to stop the ini from being loaded in that case, until Custom Clean is opened.
  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 startup of the program. Atleast is the case now with "Black friday sale" ad on CCleaner 5.49.. so closing the ad before running the cleaner is neccesary. They hope to annoy loyal users who want to get rid of the ad by buying the paid version, but I think all it does is scare them away from CCleaner or retreat to older versions with less commercial focus. Not covering the "Run cleaner" button with ads in fullscreen opening mode, therefore not requiring the user to dismiss the ad manually or wait before being able to clean, will already make this ad much less aggressive. I am doubting whether I should firewall block Ccleaner executable so it cannot fetch the ad, or moving away from CCleaner entirely.
  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 analyzing for, or otherwise pdb symbols for all components & dependencies of an app you're debugging) in these locations: The new metro-styled WinDbg store app: C:\ProgramData\dbg\ > all its subfolders contain caches old-fashioned WinDbg/some other common debuggers and development suites possibly: C:\symbols There may be other folders tied to Visual Studio or other common development environments, that contains cache and log files,I am just suggesting yet another "Application" to clean in CCleaner and when this gets accepted as idea then I believe Piriform investigates caches created by said software. Also others could post the locations they know in here. I personally experienced how symbol files (on the above location) could fill up several GB's in disk space.
  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...

Important Information

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