Jump to content
CCleaner Community Forums

SirDracula

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About SirDracula

  • Rank
    Newbie
  1. Sorry, but the thread was started 5 months ago, so the problem has been around at least that long. The devs should say something, either that things are not going to change for whatever reason or that it's being prioritized. Silence is the worst they can do.
  2. Doesn't look like this is going to be fixed any time soon. Pretty annoying.
  3. Well, I delete them with Spybot and Adaware and then a few days later, same thing happens: run CCleaner, deletes most of them, but then again Spybot and Adaware still find a couple more. Next time it happens I'll try and track it down, where these cookies are, etc.
  4. Of course I have the cookie cleanup option checked. The 48 hrs. option applies to the Windows Temp folders and it's unchecked. As I said, it doesn't delete *all* cookies, some are still left behind.
  5. If I run CCleaner followed right away by Spybot and Lavasoft Adaware, without any other applications running, or browser sessions, etc. Spybot & Adaware still find cookies. For example I just did it and Spybot still found 25 cookies. Is CCleaner not removing all cookies by default? The list under "Cookies to Keep" is empty. This has been going on forever, it's not something new in the recent versions. thank you
  6. After the upgrade to 1.35.424, the hotfix uninstall directories, e.g. C:\WINDOWS\$NtUninstallKB920213$ are left behind. Others are complaining of all sorts of files left behind with this version too. Seems that there are some bugs that need to be worked out in this version. Meanwhile I'd recommend people stick with the previous version unless they have a very good reason for the new version (e.g. affected by bugs which were fixed in this version).
  7. I see the same behavior after the upgrade to 1.35.424 In addition, the hotfix directories under C:\WINDOWS don't get cleaned up either (e.g. C:\WINDOWS\$NtUninstallKB920213$, etc.) Looks like there are some bugs in this version that need to be worked out. I'm reverting back to the previous version ...
×
×
  • Create New...