Jump to content
CCleaner Community Forums


Experienced Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Archlinux

  • Rank
  1. In CCleaner, I have the following: So I thought "Great! Exactly, what I was looking for." Yet, when I create a file, remove it, and run CCleaner, the Recycle Bin gets emptied also. As nobody has seemed to have mentioned this, it's probably a Windows 10 bug(?). I'm on Build 9926.
  2. Which app are we speaking of? You could probably redownload it (or ask the manufacturer to provide you with a copy after giving your details), but you could also try Piriform's own Recuva. It doesn't recover the item name to the uninstaller menu, but it can recover un-overwritten individual files.
  3. So anybody tried the new version? The change log doesn't really tell whether this is 'fixed' or not.
  4. 1.19.* will be released in a matter of days. We'll just have to see whether the devs have the time or interest to fix this and the other issues mentioned in this topic (that btw. should have been put into a new topic).
  5. Not as easy to fix as it seems. Took both devs and users by surprise .
  6. It doesn't clearly come up, what exactly is your problem. The volume shadow copy thingy is morely a windows bug. It sences the file moves and "backups" the files which quickly fills up the HDD until they are purged. You can read about it here: http://docs.piriform.com/defraggler/techni...e-shadow-copies Also did you try "Fast Defrag" and/or deselecting the "Move Large files at the end of the drive" (or whatever it was named as).
  7. Well, it really has been confirmed already, don't you think .
  8. Ok, so Defraggler is not efficient with small files. I don't think posting a debug output is going to help if this is an implementation feature/problem - not a bug. I can't even post any debug logs as my win 7 died for the 6th time now and I have no intentions of reinstalling the piece of crap (ever) again. But for those complaining about this thing - I suggest you either use quick defrag, 'file-only defrag' or go back to the Windows integrated Defragmenter (which is not a solution in any way). ps. You should know that the threats of not using any Piriform applications anymore is just so glaring that you should think twice before saying that. You honestly think that saying Defraggler is bad and threatening the authors is gonna help one bit of implementing a decent small file handling feature to Defraggler? I'd really like to see any of these moaners to do it themselves - oh right, you need to have some programming skills... well get a refund - oh right, this is FREE software... oh well...
  9. I myself never had that option enabled. E: You seem not to know the difference between file allocation and the actual file size: http://forums.aliensoup.com/showpost.php?p...amp;postcount=2
  10. I tried defragging 3 times in a row and every single time Defraggler takes like an hour to complete (I didn't create or delete any files between the defrags - in other words I just had the Defrag on). My C: partition is 241 GB and I have no pagefile.sys, hiberfil.sys or system restore files. Edit: As I checked the defrag process, it does indeed seem that Defraggler spends very much time with the small files that I have on my C:. I dunno if it's somewhat the same time as spent when moving around individual 'medium' sized files but that is indeed the problem. /vote for Reiserism.
  11. As the topic title says: now you are talking! It was really worth it jumping over with a new CCleaner in order to add the 64-bit support to Defraggler! I'm really proud of you guys. Keep-it-up!
  • Create New...