Jump to content
CCleaner Community Forums


  • Content Count

  • Joined

  • Last visited

Everything posted by iiiHuman

  1. This is already being discussed here: http://forum.piriform.com/index.php?showtopic=44150
  2. Oh, CCleaner still works from what I have seen. At least, for most people. There are just certain bugs with Windows 10. And, this is an important bug that needs to be addressed. Sure, they could have been testing with the Technical Preview that was available for Windows 10 and I'm guessing they actually did. Of course, the Technical Preview is different than the final version of Windows 10 that was eventually shipped. Even then, there's no guarantee bugs like this would have been found right away regardless how similar the Technical Preview was with the final release that shipped the first day. And, it hasn't really been all that long since the final release of Windows 10 started hitting machines. I would suspect they are working on fixing it. Although, it would be nice to hear from an actual Piriform employee stating that they are actually working on this specific bug. Even better, a rough estimate of when it may finally be fixed would also be good if they're willing to state that too.
  3. I totally agree with both of these people here. This is the first time I have seen this bug. I didn't have this problem under Windows 7. Same software installed other than the operating system change. Regardless of what a user may have to be expected to do in certain cases, CCleaner should be consistant. And, since no other software had changed, this is an obvious bug in CCleaner. And, even regardless of that, since CCleaner does clean the registery and you have to be careful with the registry, CCleaner should be especially aware of registry keys that may be needed and then not even give you the option to remove them (or force you to have to know yourself and also force you to exclude them). Also, keep in mind that not only would the user have to know then (extremly unlikely not to mention impossible in every instance), there is no guarantee that a needed key would automatically come back. You can't assume that something like an anti-virus program (or any program for that matter) will bring back a key that is needed. Just saying "you have to exclude it" is more of a band-aid at most. At the very least, it is still working under the assumption that it cannot be safely removed. Just because a key automatically comes back does not automatically mean that it must be needed. That is why I asked for specific references regarding these particular keys. For all we know, it is part of the bug with CCleaner that it keeps coming back such as it not being cleaned out completely and Windows therefore compensating for it and "repairing" it even though it could have been safely removed. Of course, again, if it couldn't be safely removed then CCleaner shouldn't be indicating it can be removed in the first place (which it did not do in Windows 7). I also disagree with the statement that you get absolutely no performance boost by cleaning the registry. Cleaning the registry is not just to fix things. In fact, I believe Piriform even mentions somewhere about boosting your performance by cleaning the registry. Otherwise, why even have it? Regardless, I have personally noticed a perceptible increase in performance on multiple computers by cleaning up the registry. Not only related to the boot process but also in general. And, this can be for many factors such as specific hardware and/or just how cluttered the registry can get over time etc. Sure, not everyone will notice a perceptible change in performance in some cases by cleaning the registry but it does help.
  4. I have been running into this exact issue too! This started after I upgraded to Windows 10 Professional (64-Bit). CCleaner is the only program that I trust to clear out the registry so I hope that Pirifom fixes this issue for Windows 10. If these entries are needed, I am glad that Windows 10 automatically replaces those entries. But, at the same time, CCleaner shouldn't be indicating that they can be removed in the first place then. They come up as ActiveX/COM entries. I believe most ActiveX items can be safely removed. But, the COM items are a bit more of a concern. Especially, since the file names say they are related to the Connected Storage Service. Are we 100% sure that these two particular entries are not supposed to be removed? How do we know for sure? Does anyone have any specific references citing these particular items? Here's a link to an image of the issue: http://i.imgur.com/Ns8U1Fa.png NOTE: There is also an outdated post pinned at the top of these forums from back in 2007 titled "Registry Issues Keep Re-appearing in CCleaner" that mentions using the old "Dial-A-Fix" program. But, again, it's outdated. For one thing, Dial-A-Fix doesn't work with anything after Windows XP. Also, if you are running Windows XP, the Dial-A-Fix program also has a "critical unpatched bug that will delete your 'C:\Documents' folder." And, again, I didn't have the problem in Windows 7. This particular issue started happening in Windows 10.
  • Create New...