Shodan

Very much appreciated ! Just hoping 1.4 secure delete will erase file names as well as content. That one improvement will make the wait worthwhile. ;-)

A new bug was introduced in the latest version: I have the following line in my winapp2.ini file: FileKey23=%Windir%|*.txt The previous version indeed deleted all text files in my Windows folder. The new version does not. Seems to ignore this entry. Also, a correction and apology for my forum entry yesterday where I stated the latest version indeed runs slower than the previous version. This was an error on my part as I neglected to restore my previous registry settings (instructing CCleaner to do a single overwrite instead of the 'default'.) Indeed the latest version is at least as fast as the previous one, and probably slightly faster. My apologies to the author.

Many of us have waited patiently for many weeks, anxiously anticipating the new version that boasts, among other improvements: - Rewritten secure deletion code, now over 2x faster. - Performance improvements deleting Internet Cache. Well, folks, I just finished testing 1.39.502 pretty thoroughly and guess what ? It not only seems to run SLOWER, but after all this time, it STILL does not ERASE THE FILE NAMES of the files it overwrites in secure mode ! ! Now I suppose I'll wait for another 6 weeks, or so, and see if MAYBE the next version might just FIX this issue. Destroying a file's name along with it's content is really not that difficult to code, and it would add immense value to this already wonderful application.

hmmmmm Sorry, TwistedMetal, but for once I beg to disagree. A skilled geek can always make his tracks VIRTUALLY nonrecoverable with a little knowledge and effort. Unless you are the CIA and plan to do a high tech, in depth surface scanning of my hard drive, I would defy you to undelete virtually any file that I choose to securely erase on my hard drive. And I do mean ANY file - 'protected' or not. As for those files that Windows 'protects', such as index.dat files, etc. - well, there is a simple solution for that too - it's called 'use a good old DOS based eraser at boot up.' Works like a charm and I assure you that no 'undelete utility' that I have ever tested was able to recover any of them... CIA, maybe, but 99.9999% of the rest of the people in the world with access to my PC - simply 'No way, Jose'... :-)

Precisely. It allows you to delete which folders YOU choose by using the REMOVESELF command - not a mass deletion of all empty folders. As mentioned earlier in this thread, you better know what you are doing before mass deleting a bunch of empty folders...

One thing that has not been mentioned yet in this thread - CCleaner already gives you the ability to delete any folder you choose by correctly adding it to the Winapp2.ini file. This is the best of all worlds. You will never delete any (or necessary) folders that you choose not to, but at the same time you may delete the folders of your choosing. Now, if you delete empty folders that were indeed necessary, well, shame on you. So what's the problem ? I think we can all agree that you would surely not want to delete ALL empty folders. Can't belive anyone would be stupid enough to do this... ;-)

Mr. G - your reply is appreciated more than you know ! ! THANK YOU ! And PLEASE keep up the great work ! !

'gbj' makes some good points. Those of us who really care about CCleaner and it's future, come here and report what we believe are legitimate bugs, then we sit in the dark - sometimes for a month or more with zero feedback - waiting to see if the next release will fix what we reported. If this forum is here purely for newbies to ask moderators for help, then please tell us that. Otherwise, please make it at least a bit of a 'two way street.' When bugs are reported, I think we would all like to know whether or not they are legit and whether they will be fixed at some point in time.. My .02...

Ok Mystery solved, and indeed I must fall on my sword. I ASSUMED that running CCleaner automatically scanned for issues when I did an 'Analyze' in the opening windows. I see now that I was sadly mistaken and that indeed I must run the 'Scan for Issues' separately. When I do this, it works like a charm. My humble apolgies for this oversight. THANKS for the pointer ! ! ! Again, very much appreciated.

Your efforts to run this test on your Win98 machine are VERY MUCH APPRECIATED ! ! ! Thanks for going this extra mile. I am running 'Portable CCleaner', so I shall do additional testing to see whether or not it's a 'portable' issue or maybe something else. Thanks again ! ! !

I assure you this is not working on Win98. Do you have a Windows 98 machine to test this on ? I have volunteered numerous times to beta test CCleaner because I don't think it is getting adequate testing on 'pre-XP' machines. I moved an EXE file to a temporary folder, created a shortcut, moved the shortcut to my start menu and then deleted the EXE. Ran CCleaner several times and it did not pick up on the invalid shortcut. Ran another utility - RegistryFix - and it identified the invalid shortcut immediately. Once again, I am more than willing to beta test new versions of CCleaner, but no one has replied when I have volunteered... It will be most interesting if you can get invalid shortcuts identified and deleted under Win98.

Please allow me to amend my previous reply. CCleaner indeed has options under Issues/File Intergrity for both start menu and desktop shortcuts. However, I have yet to see this function actually detect an invalid shortcut. Just now, I created a shortcut on my start menu and then deleted the EXE File. CCleaner did not detect the shortcut as being invalid. Really don't know if this has been reported as a bug, as I use a separate utility for this purpose..

Hmmmm Not to put words in this user's querry, but I THINK the user may have been asking 'Is CCleaner capapble of DETECTING AND cleaning invalid desktop/startmenu shortcuts?' Of course CCleaner will delete any shortcuts you elect to place in the winapp2.ini file, but detecting invalid shortcuts is an entirely different matter. If CCleaner is capable of doing this, it is surely very well hidden...

I totally concur, Trev. I have written of the same or similar issues here more than once. What is so frustrating is that we cannot seem to get at least a 'Mr. G is working on this issue and it should be fixed in an upcoming release', or something along these lines. We, the loyal users, have no way to know if a fix for this issue is even being considerred. If other programs can securely erase both content and filenames, then surely this fantastic tool could be made to do the same. As far as I'm concerned, erasing file names is the only thing lacking in this jewel...

This topic has been posted here now for over four days with no response from Mr. G or a moderator. I assume Mr. G is too busy to reply to all bug posts, but I would also assume the moderators would at least find out whether or not the bug post is legitimate and whether or not Mr. G intends to try to fix it. If not, those of us with issues would stop looking here for answers to them each day. Will CCleaner every erase file names, as well as content ? It seems a number of us are concerned about this issue and would really like to know whether or not to look forward to a fix. Thanks...

I have seen numerous posts in this forum, many of which complain about the same basic issue - that the latest version simply is not cleaning what previous versions did. I also read that 'Mr. G.' IS aware of the issue. However, it's been several weeks now and I'm sure everyone would like to know what is being done to resolve the problem, and perhaps an estimate of when we might expect to see a new release that fixes this issue. Please understand that I am NOT complaining about a free application, and a great one at that. Just want to make management aware that some word on progress on this issue would be deeply appreciated. Thank you.